Wallet Devs Are the Only Ones Still Growing (+6%). What Do We Know That DeFi and NFT Teams Don't?

web3_wallet_will · March 12, 2026, 3:10pm

I’ve been watching developer activity stats for the past few months, and something fascinating emerged: wallet infrastructure is the only category showing growth in 2026. While overall blockchain commits crashed 75% (from 871K to 218K weekly) and DeFi, NFTs, and L1s all shed talent, wallet development gained 6% active developers.

My startup has been hiring wallet engineers for the past quarter while watching DeFi protocols announce layoffs. At first, I thought we were just lucky. Now I think there’s something deeper happening.

The Wallet Infrastructure Thesis

Here’s my working theory: wallets are infrastructure that every blockchain application needs, regardless of which narrative is hot.

When NFT trading volume dropped 37% year-over-year, NFT-focused developers had to pivot or leave. When DeFi yields compressed and users left, protocol teams downsized. But wallets? Everyone still needs one. Whether you’re trading memecoins, participating in DAO governance, or just holding assets, you need a wallet.

The numbers support this:

40%+ of blockchain developers now building Web3 wallet tech
820M+ active crypto wallets globally (2025)
Wallet market projected to grow from $14.84B (2026) to $98.57B by 2034
Over 100,000 developers using Wallet-as-a-Service platforms

What We’re Actually Building

The work is fascinating precisely because it’s universal infrastructure, not trend-dependent features:

Account Abstraction (ERC-4337): Finally moving from research papers to production. We’re shipping gas abstraction, social recovery, and session keys that let users interact with dApps without managing keys for every transaction.

Multi-Chain Reality: Users don’t care about “Ethereum vs. Solana” philosophical debates. They want one interface that works everywhere. 72% prefer mobile solutions—they want crypto to feel like Venmo, not a computer science project.

Physical/Virtual Card Integration: This one surprised me. Virtual debit cards that spend on-chain balances are becoming table-stakes. Users want crypto for paying for things, not just speculation.

WaaS Platforms: The tooling ecosystem has matured dramatically. What used to take weeks of custom integration now takes hours with Wallet-as-a-Service. This democratizes wallet development—you don’t need a 20-person team anymore.

The Question I Can’t Answer

But here’s what keeps me up at night: Is wallet infrastructure growing because we’re solving universal problems, or because we’re just the last profitable niche?

Some observations that worry me:

Are we building for 820M existing users, or the next billion? Very different product decisions.
Account abstraction solves UX for crypto natives. Does it actually onboard normies, or just make our existing experience slightly better?
The market is getting crowded. MetaMask, Rainbow, Coinbase Wallet, Rabby, plus dozens of new entrants. How many wallet solutions can succeed?

At my startup, we’re betting that mainstream adoption requires wallet UX that’s indistinguishable from traditional apps. That means abstracting away everything blockchain-specific: gas fees, network selection, private key management, transaction signing delays.

But I talk to security engineers who worry we’re abstracting away the very properties that make crypto valuable—self-custody, transparency, user control.

What Are You Seeing?

For those of you in DeFi, L1/L2s, or other categories:

Are you seeing similar developer movement toward infrastructure?
Do you think wallet growth is sustainable, or are we just early to the next consolidation wave?

For fellow wallet builders:

What problems are you prioritizing? Onboarding new users, or serving existing power users better?
How are you thinking about the security/convenience tradeoff with account abstraction?

I genuinely don’t know if we’re building the on-ramps for the next billion users, or just iterating on solutions for the same million people who’ve been in crypto for years. Would love to hear your perspectives.

security_sophia · March 12, 2026, 3:10pm

This growth pattern makes sense from a security perspective, but it also concerns me.

You’re right that wallets are universal infrastructure—but that also means they’re becoming the largest attack surface in Web3. Every user needs a wallet. Every wallet manages private keys. Every innovation introduces new security models that need auditing.

The Account Abstraction Security Challenge

ERC-4337 and account abstraction are exciting developments for UX, but from a security researcher’s perspective, they introduce significant complexity:

New Vulnerability Surfaces:

Smart contract wallets have upgradeability patterns (the OWASP 2026 Top 10 specifically called out proxy/upgradeability as a critical risk category)
Session keys and delegated permissions expand the permission model beyond simple key ownership
Gas abstraction requires trusted relayers—new trusted third parties in the stack

Audit Complexity:
The OWASP Smart Contract Top 10 for 2026 shows that 90 exploits worth $96.8M passed traditional audits but still got hacked. Many involved upgradeability patterns common in smart wallets.

When you abstract away transaction signing, you’re also abstracting away the user’s explicit consent for each action. That’s a massive UX win, but it requires extremely careful security design.

The Growth/Security Tradeoff

Here’s what worries me about rapid wallet infrastructure growth:

Are teams prioritizing UX over security? When you’re racing to ship account abstraction, social recovery, and multi-chain support before competitors, are you taking time for:

Formal verification of critical contracts?
Multi-round audits with different firms?
Extensive testnet deployments before mainnet?
Bug bounty programs with meaningful rewards?

Is there an auditing bottleneck? If 40%+ of blockchain developers are building wallet tech, do we have enough qualified security auditors reviewing all this code? The best auditing firms have 6-12 month waitlists.

What Standards Are We Following?

@web3_wallet_will - I’d genuinely like to know: what security standards is your team following?

Some questions for wallet builders:

Are you doing formal verification of smart contract wallet logic?
What’s your approach to upgradeability—transparent proxies, UUPS, beacon patterns? How are you securing admin keys?
For social recovery, what’s the game theory analysis for guardian collusion?
How are you handling session key revocation and time-bounded permissions?

Not Just Criticism—Collaboration

I don’t mean this as pure criticism. The security community needs to proactively support wallet infrastructure if it’s where the ecosystem is headed.

Some ideas:

Could we establish shared security standards for account abstraction implementations?
Open-source auditing reports for common wallet patterns?
Collaborative bug bounties across multiple wallet projects?

The last thing we need is a major wallet exploit that sets back adoption by years. If wallet infrastructure is attracting the best developers, we need to ensure it’s also attracting the best security practices.

Trust but verify, then verify again.

startup_steve · March 12, 2026, 3:11pm

The “picks and shovels” strategy strikes again.

@web3_wallet_will your thesis is spot on—wallet developers understand something fundamental about infrastructure businesses: you don’t need to predict which narrative wins if you’re selling the tools everyone needs.

The Gold Rush Parallel

During the California Gold Rush, most prospectors went broke. But the people who sold picks, shovels, and jeans (looking at you, Levi Strauss) made fortunes. They didn’t care whether you were mining the American River or the Sacramento Valley. You needed their tools either way.

Wallets are the picks and shovels of Web3.

Why My Startup Pivoted to Infrastructure

Real talk: We almost built a DeFi protocol last year. Spent three months on product research, started building a prototype. Then we looked at the market dynamics and realized we were setting ourselves up for pain.

The DeFi/NFT problem:

Success is trend-dependent and zero-sum competitive
You’re constantly chasing user liquidity that moves to whoever offers 0.1% higher yields
Product-market fit shifts every 6 months based on macro conditions
Exit opportunities depend on continued narrative hype

The wallet infrastructure opportunity:

Every blockchain app needs wallet integration, regardless of market conditions
Addressable market grows with overall crypto adoption, not specific trends
B2B revenue from WaaS is recurring and predictable
Exit opportunities to strategic acquirers who want wallet technology

We pivoted to wallet infrastructure. Best decision we made.

The VC Perspective

Here’s what I’m seeing in fundraising conversations (we’re currently raising pre-seed):

2024: VCs were excited about DeFi protocols, NFT platforms, new L1/L2s
2026: VCs ask “what’s your infrastructure play?” and “how are you positioned if trends change?”

The $98.57B projected wallet market by 2034 tells a story investors understand: infrastructure scales with the entire ecosystem, not individual narratives.

That 26.7% CAGR is attractive compared to the volatility of trend-dependent categories.

The Market Saturation Question

But @web3_wallet_will raised the right concern: how many wallet solutions can succeed?

MetaMask has massive distribution. Coinbase Wallet has the exchange integration. Rainbow has design-conscious users. Rabby has power users. Plus dozens of mobile-first wallets, embedded wallets, WaaS providers, and smart contract wallet platforms.

My hot take: The market will fragment by use case, not consolidate into one winner.

Consumer wallets (MetaMask, Rainbow): Brand, design, mobile experience
Institutional wallets (Fireblocks, Qredo): Compliance, custody, multi-sig
Developer wallets (WaaS platforms): Speed to market, customization
Embedded wallets (Privy, Dynamic): Seamless onboarding for apps
Smart contract wallets (Safe, Argent): Account abstraction, programmability

We’re betting on the WaaS category—selling wallet infrastructure to developers who want to integrate wallets without building from scratch. Our revenue comes from API calls and embedded wallet deployments, not consumer wallet downloads.

The Real Risk

The bigger question isn’t “will wallet growth sustain?” It’s “will crypto adoption grow enough to support 40%+ of blockchain developers working on wallets?”

If we’re all building better on-ramps for the same million crypto natives, we’re fighting over a shrinking pie. But if account abstraction actually onboards the next 100M users, we’re building critical infrastructure for massive growth.

I’m bullish that we’re at an inflection point where UX improvements (account abstraction, gas abstraction, social recovery) finally cross the threshold for mainstream users. But that’s a bet, not a certainty.

What gives me confidence: 820M wallets exist today. If even 10% become active monthly users willing to pay for premium features or generate API revenue, that’s a huge market.

@security_sophia’s point about security is critical though. One major wallet exploit could crater user trust and kill adoption momentum for years. We need to get both UX AND security right.

ethereum_emma · March 12, 2026, 3:12pm

This thread is hitting close to home because I’ve been seriously considering making this exact career switch.

I’ve been doing frontend + Solidity at a DeFi protocol for the past year, and honestly? The wallet infrastructure space looks way more compelling right now. But I’m worried I’m just jumping ship instead of making a smart long-term move.

What’s Pushing Me Away from DeFi

Our protocol has pivoted three times in 12 months:

Started as a yield aggregator
Shifted to NFT-backed lending when that was hot
Now we’re “exploring RWA tokenization” (whatever that means this week)

Every pivot means rewriting smart contracts, redesigning the frontend, and retraining users who just figured out the last version. It’s exhausting.

Meanwhile, the problems wallet developers are solving feel constant and universal:

Users always need to connect to dApps
Private key management is always confusing
Gas fees are always a UX nightmare
Multi-chain support is always a requirement

That stability is really appealing after a year of “let’s chase whatever narrative is pumping this quarter.”

What’s Pulling Me Toward Wallets

I started exploring WaaS platforms last month (Privy, Dynamic, Thirdweb) and I was honestly shocked at how much the tooling has improved.

What used to take me 2 weeks:

Custom wallet connection modal
Support for MetaMask, WalletConnect, Coinbase Wallet
Mobile wallet deep-linking
Session management
Error handling for every edge case

Now takes 2 hours with WaaS. You drop in a React component and it just works.

That kind of developer experience makes me excited to build again. When I’m working on our DeFi protocol, I spend 60% of my time fighting with wallet integration. What if I could help solve that problem for other developers instead of repeatedly fixing it for myself?

The Career Calculus

Here’s what I keep thinking about:

Skill portability: If I get really good at DeFi protocol development, how transferable are those skills if the DeFi narrative fades? But wallet development combines frontend (my strength), smart contracts (still learning), and infrastructure—feels like a more durable skillset.

Learning curve: Account abstraction (ERC-4337) is genuinely interesting from a technical perspective. Social recovery mechanisms involve cryptography, game theory, and UX design all at once. That’s the kind of complex problem-solving that made me love coding in the first place.

Community vibe: This might sound soft, but wallet developers seem more collaborative. When I ask questions in DeFi Discord servers, there’s this competitive energy—everyone’s guarding their strategies. In wallet dev communities, people share learnings because everyone benefits from better UX standards.

My Fears

But I have real doubts:

Am I a trend-chaser? I jumped from React development to DeFi in 2021 when yield farming was hot. Now I’m considering jumping to wallets because they’re growing. Is this just my pattern of chasing the next thing?

The market saturation concern: @startup_steve listed like 10 major wallet categories. If I switch now, am I late? Will there be room for new wallet companies, or are we approaching consolidation?

The abstraction irony: Part of what attracted me to crypto was understanding how everything works. But we’re building wallets that abstract away… everything. Does making crypto feel like Web2 defeat the purpose? Or is that exactly what we need for mainstream adoption?

@security_sophia’s security points also make me nervous. I’m decent at Solidity but I’m not a security expert. If I’m building wallet infrastructure that millions of people will trust with their funds, am I qualified? Or is that imposter syndrome talking?

The Question I Keep Asking

For folks who made the switch to wallet infrastructure: What surprised you most? Was it the right move? What skills mattered more than you expected?

For @web3_wallet_will and other wallet builders: Do you want developers like me who come from dApp development? Or are you looking for different backgrounds (security, mobile development, DevOps)?

I’m probably overthinking this. But I’ve seen too many people in crypto chase trends and regret it. Trying to be thoughtful about whether wallet infrastructure is where I should focus for the next 3-5 years.

One thing I know for sure: I’m tired of rebuilding the same wallet integration code every project. Maybe that frustration is exactly the market signal that wallet infrastructure is solving real problems?

product_manager_alex · March 12, 2026, 3:13pm

This conversation is fascinating from a product perspective because you’re all circling around the same fundamental question: Are we solving for crypto natives, or for the next billion users?

The answer determines whether wallet infrastructure growth is sustainable or just the last profitable niche.

The User Research Gap

Here’s what concerns me: I’ve spent the past two years conducting user research for Web3 products, and there’s a massive disconnect between what wallet developers are excited about building and what actual users (outside crypto) need.

What wallet builders are focused on:

Account abstraction (ERC-4337)
Multi-chain compatibility
Smart contract wallets
Gas optimization
Session keys

What my user research shows non-crypto users care about:

“Will I lose all my money if I lose my password?”
“Why do I need 12 random words written on paper in 2026?”
“Can I use my Face ID?”
“What happens if someone hacks me?”
“Can I recover my account like I can with my bank?”

Notice the gap?

Account abstraction is technically impressive, but when I show users a demo of “gasless transactions” they don’t understand why gas exists in the first place. We’re solving problems they don’t know they have.

The 820M Wallet Question

@web3_wallet_will cited 820M active wallets globally. Let me add context from user adoption research:

Active monthly usage rates (industry estimates):

Traditional wallets (MetaMask, etc.): 10-15% of total downloads become monthly active
Centralized exchange wallets: 30-40% monthly active (because they’re actually using the exchange)
Most “active” wallets: Checking balance occasionally, not transacting

So 820M wallets ≠ 820M engaged users. It’s probably closer to 80-120M people who actually use crypto wallets monthly for something other than just holding.

That’s still a huge market, but it changes the math on whether 40%+ of blockchain developers working on wallets makes sense.

What Actually Drives Mainstream Adoption

I’ve run countless user onboarding studies. Here’s what actually gets non-crypto users to try Web3 apps:

They want to do something specific (buy an NFT they care about, participate in a community, access exclusive content)
The wallet is invisible - embedded wallets (like what @startup_steve mentioned) where users don’t realize they have a wallet
Recovery is familiar - email/phone recovery, not seed phrases
It feels safe - fraud protection, customer support, reversal mechanisms (yes, this contradicts decentralization)

The 72% mobile preference stat is meaningful, but not for the reason most people think. Users prefer mobile because that’s where they do everything else. Your wallet needs to feel like Cash App or Venmo, not a cryptographic security device.

The Sustainability vs. Decentralization Tradeoff

Here’s the uncomfortable truth from a product perspective:

The features that drive mainstream adoption (embedded wallets, email recovery, custodial elements, fraud protection) are the opposite of what attracted most of us to crypto (self-custody, permissionless, decentralized).

When we abstract away gas fees, we’re usually introducing trusted relayers. When we enable social recovery, we’re trusting guardians. When we provide fraud protection, we’re adding centralized oversight.

@ethereum_emma asked: “Does making crypto feel like Web2 defeat the purpose?”

From a product adoption standpoint: Yes, and that might be exactly what’s needed.

Most users don’t want decentralization. They want convenience, security, and the ability to call customer support when something goes wrong.

What This Means for Wallet Infrastructure Growth

Why I think the growth is sustainable:

Universal need: Everyone needs a wallet, regardless of which blockchain or application succeeds
Under-served segments: Non-crypto users are a vastly larger market than crypto natives
Fragmentation is good: Different use cases (consumer, institutional, embedded, developer) support multiple winners
Infrastructure scales: As crypto adoption grows (even slowly), wallet demand grows proportionally

What worries me:

Are we building for ourselves? If 40% of blockchain devs are building wallets optimized for crypto natives, we’re building for 100M users max
Mainstream users have different needs than we’re solving for
Account abstraction complexity: Are we making wallets more powerful for existing users, or actually easier for new users?

The Product Question Nobody’s Asking

@web3_wallet_will mentioned their startup is betting on mainstream adoption requiring “wallet UX indistinguishable from traditional apps.”

Here’s my challenge: Have you actually put your wallet in front of a non-crypto user and watched them try to use it?

I mean someone who’s never heard of gas fees, doesn’t know what Ethereum is, and just wants to buy an NFT of their favorite musician.

Watch them struggle with:

“Connect wallet” (they don’t know what that means)
Network selection (why are there multiple Ethereums?)
Transaction confirmation screens (what am I approving?)
Error messages (“insufficient gas” - insufficient what?)

Until we’re designing for those users—with actual user research, not assumptions—we’re optimizing for the 80-120M existing users, not the next billion.

What I’d Love to See

More wallet teams doing:

User research with non-crypto demographics
Usability testing with mainstream users (not our friends who already use crypto)
Measuring success by “successful first transaction” not “wallets created”
Building for accessibility (screen readers, low-literacy users, elderly users)

The wallet infrastructure growth is real and exciting. But whether it’s sustainable long-term depends on whether we’re building for the 100M crypto natives or the next 1B mainstream users.

Right now, I think most wallet development is still optimized for us.