Evolution is a life constant—and I'm no exemption. Having evolved over the while, let me introduce myself again.
I'm Emmanuel, (OmegaSage is my alias). I am a marketing & growth strategist.
I help web3 projects grow users, revenue & adoption, especially in emerging markets, without burning their run way.
Here's what I'm building and what you can expect to find here 🧵
Wrapping up the year feeling truly grateful🙏
Huge thanks to @Arcium for such an incredible year.
As @Angeldweb3girl and I look back on our journey so far, we are thankful for every single person in the Arcium community who supported us, liked our posts and cheered us on. It really means more than we can say.
We are not at the finish line yet, but the journey itself has already been worth it.
Remember that with Arcium, your personal details can remain encrypted while still powering the tools you rely on everyday.
Stay <encrypted>☂️ See you all next year💜
Here’s how to properly structure an end-of-year personal retreat.
Plus, I curated a Personal Retreat sermon playlist to help you withdraw, reset, and hear God clearly. You’ll find it below in this thread.
Thread 🧵
Most Web3 founders don’t have a marketing problem.
They have a story problem.
They’ve built something powerful…
But when asked “What do you do?” the answer sounds complicated, scattered, or forgettable by those who hear it.
And when people don’t understand you, they don’t trust you.
When they don’t trust you, they don’t convert.
This is why storytelling isn’t optional in Web3 marketing.
The founders who win aren’t louder,they’re clearer.
Save this if you’re building and struggling to explain it simply.
Bagging Jobs as a newbie or expert in Web3 Marketing comes with more than just having the skills or qualifications.
♦️I covered some of the basics you need to have to bag a Job as a marketer in web3 in the quoted post below but that is not all..
I see that a lot of people actually need these type of simple step by step relatable tweets to be well prepared and put together for a web3 marketing gig and today , we will be talking about the next important steps after the basics.
❗️❗️This is a very important phase that influences your chances of getting a Job as a web3 marketer
BOOKMARK THIS AND REPOST FOR MORE REACH
Now let’s get into it 👇
Most web3 projects are obsessed with acquisition.
They spend $50k on KOL campaigns. They run airdrop after airdrop. They chase Twitter engagement metrics like their life depends on it.
And then 90% of their "users" disappear within a week.
Here's the growth strategy they're missing: retention before acquisition 🧵
More often than not, we see projects celebrating 100k Discord members or 50k Twitter followers while their actual product has maybe 500 active users.
That's not growth. That's vanity metrics with extra steps.
Real growth is when users come back. When they stick around. When they bring their friends cos they actually find value.
The problem with acquisition-first thinking:
When you pour money into getting users before you've figured out how to keep them, you're essentially filling a leaky bucket.
Every new user costs money. If they leave immediately, that money is gone. And worse? You have no idea WHY they left cos you never built systems to understand retention.
Here's what retention-first looks like:
Instead of spending $20k on a Twitter campaign to get 10k new Discord members, spend that time (and way less money) understanding your first 100 real users.
→ Why did they show up?
→ What keeps them coming back?
→ Where do they get stuck or confused?
→ What would make them tell others about you?
This is because once you understand retention, your acquisition compounds. Every new user you bring in actually sticks around and adds value instead of churning out.
Real example from the trenches:
I watched a DeFi project spend $30k on influencer partnerships. They got 15k new Telegram members in two weeks.
Ninety days later? Less than 200 were still active.
Meanwhile, another project spent $2k on targeted content and community events for their existing 500 users. Six months later, they had 8k active users cos the original 500 kept bringing friends who actually stayed.
That's the difference between growth and noise.
How to actually implement this:
Step 1: Pick your retention metric. For web3 projects, this might be:
→ Weekly active wallets
→ Discord messages per member
→ Transaction volume per user
→ Community event participation
Don't pick vanity metrics. Pick something that shows real engagement.
Step 2: Study your best users. The ones who show up consistently. Interview them. Understand what they love and what frustrates them. These people are showing you the path to retention.
Step 3: Fix the leaks before you scale. If users drop off after onboarding, fix onboarding. If they get confused about your product, improve your education. If your Discord is dead, figure out why before inviting more people into a ghost town.
Step 4: Only then do you scale acquisition. Once you've proven that new users stick around, NOW you can justify spending on growth campaigns. Cos now every dollar you spend actually compounds instead of evaporating.
Why this is hard for web3 projects:
Retention work is slow and unattractive. You can't screenshot a retention rate and post it for engagement. You can't flex about "we improved day-7 retention by 15%" the way you can flex "we hit 100k followers."
But here's the thing: projects that focus on retention early are the ones still around two years later. The ones that chased acquisition? Most of them burned their runway and faded into irrelevance.
The compounding effect:
When you nail retention first:
→ Your acquisition costs drop (happy users recruit for free)
→ Your community quality improves (engaged people attract similar people)
→ Your product gets better faster (cos you're learning from real users, not tourists)
→ Your runway lasts longer (you're not burning cash on users who leave)
That's sustainable growth. Not the pump-and-dump community building that's way too common in web3.
Bottom line:
If your users don't come back, it doesn't matter how many you acquire.
Fix retention first. Understand why people stay before you figure out how to get more people to show up.
The projects that win long-term are the ones that build for the users they have, not the users they wish they had.
Do well to focus on the right metrics. Growth isn't about how many people show up. It's about how many people stay.
I am OmegaSage, a growth strategist helping web3 projects scale sustainably in emerging markets. If you found this valuable, share it with a founder who's burning money on acquisition without understanding retention first.
Good morning CT
While you are waking up to the smell of hot coffee and the morning vibes that come with it….
Let my podcast be your go-to morning news on marketing in web3 🌚😄❤️
Just to add
1: If I ever ask you to spam me your pictures, or I spam you mine, then I rate you like madd
2: expect me to dramatic when you spam me. Try and be too when I spam you (not compulsorily tho, but bring some energy)
3: if I ask you to spam me, DON'T YOU EVER send as view once...let's not be unfortunate🙏🏽
Are you into Web3 Marketing and are yet to bag Jobs either as a newbie or an expert?
Most times, people find it difficult to get jobs…..
… not because they don’t have the required skills or qualifications
… but because they aren’t checking out the basic things you have to do to back Web3 Marketing Jobs.
♦️In this post, I will be covering how you can start getting yourself positioned for Web3 Marketing Jobs.
But first..
BOOKMARK THIS POST SO YOU COME BACK TO IT AND REPOST FOR REACH
Now let’s get to it… 👇
What's next in this series:
Over the coming days & weeks, I'll be diving deep into each of these innovations:
→ How IceDB actually works
→ MultiStream consensus mechanics
→ EVM compilation benefits
→ Compression techniques explained
Follow along if you want to understand what makes Somnia tick beyond the marketing headlines. Next up is a deep dive on IceDB🧊
If you think this was helpful, do well to share it with someone exploring L1s or building in the Somnia ecosystem.
I am OmegaSage, a growth strategist helping web3 projects scale in emerging markets. If you're interested in how blockchain tech translates to real-world adoption, you're in the right place, feel free to give a follow @OmegaSage0x and lets connect.
The Innovations Behind Somnia's 1M+ Transaction Per Second (TPS) and Sub-second finality (#SomniaTechSeries)
Everyone talks about Somnia hitting 1M+ TPS with sub-second finality, but most people don't actually understand HOW they pulled it off.
It's not magic. It's four core innovations working together that make this possible.
🖼️ @Somnia_Network
I'll be breaking these innovations down in what I'll call the #SomniaTechSeries, and, this thread is the first episode, in which I will be doing an overview of all these innovations.
In subsequent episodes, I'll pick one innovation at a time and do a deep dive on it, till we've touched all four.
Now lets get to it!
First, some context.
More often than not, blockchains hit a wall at scale. Ethereum does ~15 TPS. Solana peaks around 65k TPS in practice (with regular hiccups). Even the "fast" chains struggle when real users show up.
Somnia approached scalability differently by—Rebuilding the fundamentals from scratch.
Innovation #1: IceDB
This is Somnia's custom database for storing blockchain state.
Traditional blockchains use databases that weren't built for this workload. IceDB was designed specifically for blockchain operations, making reads and writes significantly faster and more predictable.
Think of it like this: most chains are using a pickup truck to race in Formula 1. Somnia built a race car from the ground up.
Why IceDB matters:
When you're processing 1M+ transactions per second, your database becomes the bottleneck fast. You need something that can handle massive parallel operations without choking and IceDB solves this as it is optimized for the exact workload blockchains face, not general-purpose computing.
Innovation #2: MultiStream Consensus
This is Somnia's consensus mechanism. It's a proof-of-stake, partially synchronous BFT protocol that processes transactions in parallel streams instead of one sequential queue.
Most chains process transactions one after another; Somnia processes multiple streams simultaneously.
Why MultiStream matters:
Sequential processing is a fundamental speed limit. You can only go so fast when everything has to wait in line.
MultiStream breaks that barrier by handling multiple transaction streams at once, all while maintaining security and finality guarantees.
This is how Somnia hits sub-second finality (around 400ms) consistently.
Innovation #3: Accelerated Sequential Execution
Somnia compiles EVM bytecode for faster execution.
Standard EVM execution interprets code at runtime, which is slow. Somnia pre-compiles it, making each transaction execute significantly faster.
It's like the difference between reading instructions out loud versus having them memorized and ready to go.
Why this matters:
Speed at the execution layer compounds with everything else. If each transaction executes faster, your entire throughput increases without sacrificing EVM compatibility.
Developers can deploy Ethereum contracts as-is, but they run faster on Somnia. Best of both worlds.
Innovation #4: Advanced Compression Techniques
When you're doing 1M+ TPS, node-to-node data traffic explodes, and that fast becomes another bottleneck.
Somnia uses advanced compression to handle this increased data flow without overwhelming the network or requiring insane bandwidth from validators.
Why compression matters:
High throughput is useless if nodes can't keep up with the data. You'd end up with centralization (only massive data centers could run nodes) or network congestion.
Compression keeps things manageable. Validators can participate without enterprise-level infrastructure.
Here's what makes Somnia different:
Most "fast" blockchains optimize ONE thing and hope it scales. Somnia rebuilt FOUR fundamental layers:
→ Storage (IceDB)
→ Consensus (MultiStream)
→ Execution (Compiled EVM)
→ Data transfer (Compression)
Each innovation supports the others and that's how you get 1M+ TPS with sub-second finality that actually holds up under load.
Why this matters for real-world adoption:
• Gaming needs instant feedback (400ms finality delivers that).
• DeFi needs high throughput without failed transactions (1M+ TPS handles volume).
• Social apps need responsiveness (sub-second finality makes it feel native).
Somnia's tech stack makes these use cases actually viable on-chain for the first time.