[DRAFT] Atom Registry — Official Web3 Universal Namespace Platform for Cosmos Hub

Change log

  • 2026-03-28 Created initial post

Summary

Atom Registry is a fully deployed, self-funded Web3 domain naming platform live on Cosmos Hub mainnet today. This signaling proposal asks the community to formally recognize it as the official multi-TLD Web3 namespace and domain naming layer for Cosmos Hub.

No community pool funds are requested. Eight CosmWasm contracts are already running on cosmoshub-4. This proposal costs the Hub nothing except an endorsement.

In exchange: full open-source publication, 2-of-3 multisig community governance, 50% of platform earnings to a Cosmos LP for one year, and unconditional transfer of 16 TLDs to major ecosystem teams — including .cosmos and .ibc to the Interchain Foundation and .dao to the Cosmos Hub community pool as a permanent revenue-generating asset.


Details

The Problem

Cosmos Hub has no official naming layer. ENS on Ethereum. SNS on Solana. Unstoppable Domains on Polygon. Every major L1 has one. Cosmos Hub does not. Users send to 45-character addresses. Projects have unverifiable identities. Validators compete on marketing copy. This is a solved problem — it is already solved.

Live Namespace Snapshot

122 TLDs minted across 10 distinct owners. 33 currently open for public name registration. The namespace marketplace already exists and is already operating. This is not a proposal for something hypothetical.

Open TLDs (registrable now): .any .atom .bitcoin .blockchain .btc .chain .custody .dev .do .eureka .global .grok .index .lab .link .lunc .mint .mori .name .onchain .oracle .org .price .reserve .route .skip .treasury .ultra .val .vip .web .xyz .zk

Contracts on cosmoshub-4

Contract Address
Registry cosmos16nff0lmuegn2zr6ca3dp8jnqltpq2c9ayhmqn3avjq0wne95h2xqkhn9qe
TLD Manager cosmos1xa9s4c2g26shyv3me50xqp0asxkfeqfnx0zhgy8ygvlglq9srxkq6djfhm
Resolver cosmos1swmjnderkae2hpegvt75dn34kya388vydxg5k5mzd0dl6wme2teq2xxpkv
Site Registry cosmos1xg6jh7nechv6kxrw35m08qdpaysnu97xjz5alql75p2k5xrcdvjs8rx7jt
Registrar cosmos16nff0lmuegn2zr6ca3dp8jnqltpq2c9ayhmqn3avjq0wne95h2xqkhn9qe
Marketplace cosmos1w4rknyllzt7mu6tsl6m7qm0sss66stwemvc4p4utdsyrjdf9q44ss0697x
Metadata cosmos12sseygvx4ykhp0df70ndg82l7p9a7ld7l0n0pptwj7c2h726cc9sahh4hz
dSSL Manager cosmos1swmjnderkae2hpegvt75dn34kya388vydxg5k5mzd0dl6wme2teq2xxpkv

Why Cosmos Hub

Not just .atom — any TLD. Anyone can own any top-level domain permanently. The owner sets the price, the policy, and earns 100% of registration fees under their namespace forever. No ICANN. No registrar. No expiry.

Every IBC-connected chain can query the naming layer with a single REST call. No separate deployment. No bridging. Query the Hub. Get the name. Done.

A lightweight Keplr update integrating name resolution instantly makes Web3 browsing available to millions of existing users simultaneously. Not a gradual adoption curve. A switch.

Ecosystem Benefits

  1. Human-readable identity for every wallet

  2. Cross-chain address resolution — one name, every chain

  3. Permanent censorship-resistant on-chain web presence

  4. Verifiable trust via dSSL — cosmos.toml manifests and attestations

  5. Validator identity and transparency

  6. DAO and governance legibility

  7. IBC routing legibility — long-term foundation

  8. Fediverse and decentralized social identity

  9. Truly on-chain NFTs and real world asset tokenization

  10. Developer platform and ecosystem growth

  11. Economic flywheel for ATOM

  12. Native monetization layer for wallet infrastructure

  13. ATOM commerce layer — any seller can accept ATOM payments in 10 minutes with zero fees

Unconditional TLD Gifts

Not conditional on this proposal passing. Claim by DMing @atomregistry on X from your official account with your Cosmos Hub wallet address. Transfer within 24 hours.

.osmosis → Osmosis Labs | .stargaze → Stargaze Foundation | .stars → Stargaze Foundation | .keplr → Keplr / Chainapsis | .leap → Leap Wallet | .ibc → Interchain Foundation | .cosmos → Interchain Foundation | .dao → Cosmos Hub Community Pool (permanent revenue stream — first proposal to give the pool a revenue-generating asset rather than request a spend) | .stride → Stride Labs | .injective → Injective Labs | .neutron → Neutron | .celestia → Celestia Labs | .akash → Akash Network | .noble → Noble | .dydx → dYdX Foundation | .juno → Juno Network / DAODAO

ATOM Sales Widget — Live at ATOM Sales Widget Builder | Atom Registry

A complete self-hostable ATOM payment system built, tested, and shipped by the Atom Registry team. Free to any seller. Visual widget builder, Keplr-native checkout, on-chain TX verification via Cosmos Hub LCD, duplicate TX blocking, digital download delivery, downstream webhook automation. Drop it on any PHP host and accept ATOM in 10 minutes. No fees. No middleman. Every sale is an ATOM transaction. Every seller who wants a storefront registers mystore.atom.

Security

Contracts developed using rigorous internal methodology — invariant-driven design, authorization validation on every entrypoint, overflow-checked arithmetic, reentrancy-safe state management, and adversarial path simulation throughout. No formal third-party audit performed. Codebase published to GitHub on proposal passage. If the community requires a formal audit as a condition of acceptance, it will be conducted at the community’s expense.

Commitments

  1. Full open-source publication to atomregistry (Atom Registry) · GitHub within 30 days

  2. 2-of-3 multisig governance — founder holds 1 permanent required key, community elects 2 keyholders through Hub governance. Community keys alone cannot reach threshold. Enforced by math.

  3. 50% of all platform earnings to a designated Cosmos LP on Osmosis for one year. After one year, LP principal returned to founder interest-free. Yield remains in pool permanently. Default after year one: 50% founder / 50% community pool.

  4. Founder retains permanent Builder and Technical Lead role by structural design — cannot be removed without founder’s own signature.

  5. Contract migration to reflect multisig governance within 90 days.

What This Is NOT

Not requesting community pool funds. Not a grant. Not exclusive — community retains the right to endorse alternatives via future governance. Not locked-in — recognition can be revoked through subsequent governance at any time.

About the Builder

Atom Registry was conceived and funded by a single builder — an entrepreneur and technology developer who has been building in the Cosmos ecosystem quietly and methodically without outside investment, without hype, and without asking for anything in return. This proposal is the first formal ask directed at the community and it is not a request for money. It is a request to recognize work that has already been done, infrastructure that is already running, and a commitment to the long-term health of the Cosmos ecosystem that is already being honored.

The platform has been built this way deliberately. When you accept outside investment there is pressure to overpromise and underdeliver. When you fund it yourself you can focus on building something that actually works. Atom Registry works. It is live. It is on Cosmos Hub. It is yours if you want it. This proposal will remain in Draft for a minimum of 2 weeks before formal submission onchain to address any communiy concerns.

Full Visual Proposal

Complete proposal with visualizations, ecosystem map, contract tooltips, and interactive elements: @ Search | Atom Registry and enter proposal.atom, or by browser extension.


Forum post link


IPFS link

to be added — take PDF snapshot of forum post and pin via Pinata before going on-chain

Governance votes

The following items summarize the voting options and what it means for this proposal:

YES — You agree that Atom Registry should be recognized as the official Web3 multi-TLD domain naming layer for Cosmos Hub, endorsed as a public good, and that the open-source, governance, and LP commitments described above should proceed.

NO — You do not endorse Atom Registry for this role at this time. The team will take specific concerns raised in forum discussion and return with a revised proposal.

NO WITH VETO — A ‘NoWithVeto’ vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub governance. If the number of ‘NoWithVeto’ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.

ABSTAIN — You wish to contribute to quorum but you formally decline to vote either for or against the proposal.

2 Likes

Pretty cool I must say, I really like the UI , very smooth and clean. Was about to register my name but like someone els said it doesn’t work atm with Ledger.

Is it something you plan to add ?

I know nothing about domain and hosting a website so I’m waiting on other to comment on that part.

For now, I would say this is an interesting proposal I want to support

1 Like

Hi There!

I’m working on Leap and Ledger both! My goal is to trigger a popup if Kepler isn’t detected for Leap and Ledger. I have a bridge built but to be fully transparent, it’s glitchy so I can’t put it into production.

I’m on it, though!

Thanks!

Amazing work and respect for the effort but I don’t think this proposal passes in its current form. For something seeking official cosmos hub recognition, the key trust and security pieces should be in place before the vote, not after it. Open source code, an independent audit and clearer governance guarantees should come first. Right now it feels like the community is being asked to endorse first and verify later and for infrastructure of this importance, that order matters :atom_symbol:

2 Likes

That’s a valid point. I would think that an equally valid point is that this is the easiest project ever to verify simply by registering a TLD, then subdomain, then launch an HTML website, and it all functions clearly as I claim, or I’ve just been blowing smoke. For that testing flow, I’ll be more than happy to fund a clean account of the communities choosing.

If I’ve actually built a legitimate decentralized web experience as I claim, that can be determined in just a few minutes. If I haven’t then the proposal is dead anyway. As far as open sourcing the project, if the proposal does go into formal submission, I’ll open it up for review. All the data is either onchain already or in a static HTML website so it’s not secret anyway.

I would agree that the governance should be clear and if there is something I’ve overlooked, or needs to be negotiated, I’m available for that conversation. The Draft covers an independent audit and since the existing contracts would in part need updated for migration, it would make sense to audit the updated contracts instead of the existing ones since there will be treasury and governance items to address.

I appreciate your feedback and hope I can earn your support.

Thanks!