NAM Utility & Namada’s Path to Success

Excellent Validator Circle :yellow_circle: today. Grateful for so much engagement–the passion is energizing, thank you.

We discussed elements of this forum post, and I committed to writing this forum post to address the nam-only vs any-token gas fee model within the broader context of Namada’s long-term success and sustainability.

NAM utility is not a side concern–it will define whether or not Namada survives and thrives.

What’s the future of Namada, and why hold NAM?

Over time, as Namada’s adoption grows, NAM will generate meaningful value, and staked NAM should be able to capture some of that value. Our priority today is enabling that adoption: make Namada fast, safe, and secure at a foundational level, and expand to support more assets, chains, apps, wallets, and experimental features (like programmability). If you haven’t, check out this roadmap Namada - Roadmap :fire:

We* see two potential sources of fee revenue in Namada:

  1. Gas fees (compute and storage)

  2. Shielded pool (MASP) fees

Gas fees today can be paid in any token. That’s intentional—we want to make it as easy as possible for new users, wallets, and communities to onboard. Preventing spam/DoS matters, but in terms of revenue we don’t want to capture value at the edges (ie. gas for compute and storage), we want to capture value at the core–shielding.

Value Proposition

Namada’s MASP is the value engine. Privacy is our differentiator, and shielding is our product. So the MASP is where we should focus our value growth and capture efforts.

Shielded rewards are a bootstrapping mechanism, not a permanent subsidy. To provide shielding, there needs to be a target size for each asset in the pool, so we use NAM rewards to help establish that. But once a target is reached for a given asset, the job of the rewards is done, and at that point its incentives wind down.

As the MASP becomes a trusted and widely used system, Namada will generate enough demand to charge for shielding. Railgun is already earning ~$400K/month from privacy fees

Our path to utility and value capture is clear, we just need to keep building and integrating. When the time is right (ie. when Namada is scaling rapidly), MASP deposits can involve a fee. This isn’t something we should activate yet, but this is the path:

  • A small percentage of each deposit goes to the protocol as revenue

  • Revenue is protocol managed: partly to buy NAM, and partly to pay NAM stakers

  • Fee policy will be governed by NAM stakers

Gas fees should remain small to avoid penalizing experimentation or usage. MASP fees would be a separate lever, introduced when the ecosystem is thriving.

Will Namada be a privacy service or platform?

It’s still early, but surfacing this longer-term strategic question.

If Namada is Privacy-as-a-Service, we’re a modular layer—apps, chains, and users plug in for shielding, and we monetize access. This seems to be most in line with “composable privacy” and the roadmap here: Namada - Roadmap

If Namada is Privacy-as-a-Platform, Namada becomes a place to build, with native apps, programmable primitives, and composable privacy. We can experiment with programmability–which will be a lot of fun–but we’ll only lean into it if we see clear traction.

The service vs platform distinction should shape how we think about long-term value capture, programmability, and ecosystem growth. But again, our focus right now must be on making Namada fast, safe, and widely integrated.

Marketing

Lastly, (yes!) marketing will matter more and more. Privacy doesn’t sell itself—people need to understand what’s possible and why it matters. Right now I think we should market our mission and vision by growing our intrinsically-aligned base of contributors–people energized by the mission, ready to weather unpredictable token prices. As Heliax makes Namada solid, we’ll need a coordinated effort to make Namada’s value proposition visible and grow demand.

I’ve opened a hot topic here. Let me know what I’ve missed or what you’d challenge, would love to hear your thoughts!

Fast chat → Discord
Lasting ideas → Forum (reply here!)

*writing on behalf of Knowable

8 Likes

update from the Discord hot topic

2 Likes

I’d like to close this topic in favour of continuing discussions here: Proposal for a volume-proportional fee sharing system

I see that I didn’t close this topic. Convenient, because I’d like to bring attention to framing Namada as a privacy service versus privacy platform.

Namada as a Service vs Platform

There are a few different kinds of privacy-focused projects, and this is how I distinguish them:

  1. Privacy currency - eg. Zcash’s ZEC or Monero’s XMR
  2. Privacy platform - eg. Aztec’s smart contract development platform
  3. Privacy service - eg. Railgun’s shielded pool

I don’t think we’re trying to make better money, so if it’s between service and platform, I think we should be the world’s best privacy service.

Why not both?

There are many smart contact platforms, services, and apps that will want to use an established shielded pool instead of starting/growing their own, including privacy platforms. Why focus resources growing your shielded pool if your platform can use many shielded pools? And why focus resources on growing app development when you can offer your shielded pool to many platforms?

Shielded Pool as a Service

The purpose of a shielded pool is to secure data around transactions. If I transfer 100 Token_A, I want the pool of Token_A to be at least 1000 and for there to be a number of other similar sized transfers also happening regularly.

If the service Namada provides is access to use its shielded pool, then access and usefulness is what we need to grow.

Railgun appears to be offering the same thing, but specifically within the EVM ecosystem. Currently they have $90.17m and operate across four mainnet chains and an ethereum testnet.

To be as useful as possible, we should serve more chains. Some ideas:

  • Ethereum
  • Solana
  • Tron
  • Base

We should support a wide selection of tokens. Depositors should be able to use their tokens, eg. lend or stake them, using the Namada validator set to control them. What else?

What other noteworthy shielded pools are there?

There are others not on the DefiLlama list, like is https://x.com/0x0exchange a thing? It would be great for someone to gather some intel on this.

1 Like

https://x.com/BanklessHQ/status/1948368619672351008

“Transferring Privately” appears to be the category of shielded pools.

Each of these tools offers private transfer options with tradeoffs.

➢ (at)Veildotcash
— Ideal for one-time moves. Deposit ETH or USDC into zkSNARK pools on Base, withdraw to a fresh wallet. A secret note unlocks funds. Choose public or Coinbase-verified pools depending on compliance needs. Wait before withdrawing to avoid timing analysis.

➢ Privacy Pools by 0xbow — Transfer ETH, USDC, USDS, and sUSDS privately between addresses. ASP ensures fund legitimacy. “Ragequit” feature lets users exit at any time.

➢ Railgun — The only tool allowing indefinite direct transfers between shielded addresses. Both parties must use Railgun.

tweet thread includes other noteworthy privacy preserving projects (including on-ramps)

i haven’t gone through this huge list yet: https://github.com/web3privacy/web3privacy
(Namada’s could use an update, @Rigorous )

and here https://explorer.web3privacy.info/
Namada’s profile: Namada - Web3-Privacy

2 Likes

Submitted updated information.

There is low hanging fruit to get a higher score on the web3privacy explorer, like adding a privacy policy, but we will likely never get a 100% score because of how the protocol is designed to have optional privacy and upgradability. I do not know what to declare for funding transparency. https://mirror.xyz/0x0f1F3DAf416B74DB3DE55Eb4D7513a80F4841073/s9flkE6tMaJ4f2tzWu-FmDy7Zx_TRPe3jdXr2iYmYH0