[DRAFT] Whitelist Atom Registry Deployment Address for Osmosis Interchain TLD, Registry, and ICS-721 Infrastructure

Proposal Discussion DApps / Tooling
1

[DRAFT] Whitelist Atom Registry Deployment Address for Osmosis Interchain TLD, Registry, and ICS-721 Infrastructure

Summary

This proposal requests Osmosis governance approval to whitelist the Atom Registry Osmosis deployment address for scoped CosmWasm contract uploads related to interchain registry infrastructure, Osmosis-compatible TLD namespaces, and ICS-721 NFT transfer support.

Requested Osmosis deployer address:

osmo1mn2ekfxs8zc40hdjt44edfaht0pdgqul5esquq

Associated Cosmos Hub controller/deployment address:

cosmos1mn2ekfxs8zc40hdjt44edfaht0pdgquluzrs2j

Atom Registry operates from:

Atom Registry is building Cosmos Hub-native registry infrastructure for names, TLDs, NFT-backed claims, and interchain routing. As part of this work, Atom Registry has reserved .osmo and .osmosis within the Atom Registry system and seeks to build Osmosis-compatible infrastructure around those namespaces.

This request does not ask for community pool funds. It does not ask Osmosis governance to custody assets. It does not request control over any existing Osmosis namespace system. It asks only for upload authorization for the listed deployer address so Atom Registry can deploy and maintain contracts needed for Osmosis-compatible interchain registry and NFT transfer infrastructure.

Background

Atom Registry is developing infrastructure for interchain names, TLD records, resolver logic, NFT-backed claims, and IBC-aware routing. The goal is to make registry records and namespace-linked assets usable across IBC-compatible chains.

Related work already deployed or tested on Cosmos Hub includes:

  • PUSDC Vault v3.1
  • PUSDC NFT v3.1
  • PUSDC Transporter
  • Hub-side ICS-721 bridge endpoint

PUSDC is a Cosmos Hub-native, USDC-backed NFT asset. Each active PUSDC NFT represents a redeemable claim against USDC held in a Cosmos Hub vault. Redemption remains on Cosmos Hub. Osmosis-side infrastructure would support routing and transfer, not reserve custody.

Why Osmosis?

Osmosis is a core liquidity and DeFi venue in the Cosmos ecosystem. Supporting Osmosis is important for:

  • interchain registry records
  • Osmosis-specific TLD namespaces
  • NFT-backed claim movement
  • future interchain resolver logic
  • DeFi-compatible name and asset routing
  • .osmo and .osmosis namespace infrastructure
  • PUSDC and other NFT-backed claim transport

Requested Permission

Authorize the following Osmosis address to upload CosmWasm contracts on Osmosis mainnet:

osmo1mn2ekfxs8zc40hdjt44edfaht0pdgqul5esquq

This address will be used for Atom Registry deployment work related to:

  • Osmosis-side ICS-721 endpoint deployment
  • PUSDC / NFT-backed claim transport infrastructure
  • Atom Registry interchain TLD registry contracts
  • .osmo and .osmosis namespace support
  • resolver contracts
  • registry verification contracts
  • route/transport contracts
  • IBC-aware registry adapters
  • future upgrades or companion contracts necessary to maintain these systems

Associated Cosmos Hub address:

cosmos1mn2ekfxs8zc40hdjt44edfaht0pdgquluzrs2j

Contracts Expected Under This Authorization

  1. ICS-721 endpoint contracts

Used to support interchain NFT movement between Cosmos Hub, Osmosis, and other compatible IBC chains.

  1. NFT-backed claim transporter contracts

Used to route NFT-backed claim assets across IBC while preserving Hub-side redemption logic.

  1. Atom Registry TLD registry contracts

Used to manage registry records, TLD ownership, renewal/configuration rules, and chain-aware namespace metadata.

  1. Resolver contracts

Used to resolve registered names or TLD records to addresses, websites, contract addresses, metadata, or IBC routing records.

  1. Osmosis namespace contracts

Used to support Atom Registry’s reserved .osmo and .osmosis namespaces and related metadata/resolution infrastructure.

  1. Verification and adapter contracts

Used to verify ownership, route registry records across chains, and connect Osmosis-side contracts to Cosmos Hub registry state.

Risk Controls

  • No Osmosis community pool funds are requested.
  • Upload authorization can be revoked by Osmosis governance.
  • Contract code IDs and hashes can be published after upload.
  • Critical contracts can use multisig/admin controls where appropriate.
  • Registry and routing contracts can include pause/disable mechanisms.
  • PUSDC reserve custody remains on Cosmos Hub.
  • Osmosis-side PUSDC infrastructure does not custody USDC reserves.
  • Initial deployment can be limited to low-risk routing and registry functionality before expanding.

Requested Outcome

If approved, Atom Registry will:

  1. Upload required contract code to Osmosis mainnet.
  2. Publish code IDs, contract addresses, and hashes.
  3. Instantiate the Osmosis-side ICS-721 endpoint and related registry infrastructure.
  4. Coordinate a dedicated IBC route between Cosmos Hub and Osmosis where required.
  5. Deploy .osmo and .osmosis namespace support.
  6. Publish testing results and route status.
  7. Maintain public documentation for deployed contracts.

Voting Options

YES
Approve whitelisting the Atom Registry deployment address for scoped CosmWasm uploads related to interchain TLD, registry, resolver, and ICS-721 infrastructure.

NO
Do not approve this whitelist request.

NO WITH VETO
Indicates this proposal is spam, malicious, or significantly harmful to Osmosis.

ABSTAIN
Decline to vote for or against.

2 Likes
2

Hey, the current ICS721 implementation is osmo10vzkd8pyme67z38epdr3gf027y03dxq7t8vau5fp3r28vxks7mwse02j8f
We shouldn’t need multiple deployments of this for bridging.

We also use ICNS for naming on Osmosis already - although this is open to competition since it is a fairly old project now and the usecase looks slightly different.

Have seen all your posts on the Cosmos Hub forums too over the recent months, generally support active ecosystem builders having this access.

1 Like
3

Thanks!

The ARK Bridge still requires a checksum whitelisting for custom smart contracts which is how PUSDC is built.

For Atom Registry, I’m not kicking dirt on another project when I say its multi tld model considerably different. Instead of trying to wow anyone with fast talk and a hard sell, just check out what I have going on.

I set up a site @ https://osmosis.gdn/ for a web3 resolver and the browser extension I built works just as well. When someone looks for https://grok.grok or https://atomregistry.osmosis, or a 100 other sites because it’s growing, what the resolver renders is a 100 percent onchain stored website built in html. I built standard DNS into it also so a domain owner can use an ip address and build a site in regular hosting as an add on domain.

I tried and failed at future proofing this because in spite of all of the mad case use I packed in, I’m learning that the Cosmos stack has options no other chainstack has.

PUSDC is just cool. Cosmos Hub didn’t have a legit stable asset and now it does in the form of a pegged usdc nft. I do believe that Osmosis can benefit massively from having it as a means of transporting pegged usdc. Ark can see the PUSDC but can’t transport it because of checksum.

ark
ark1360×673 98.7 KB

With all I have cookin’ in the stew pot, I’d love to be whitelisted on Osmosis, and admittedly, it’ll benefit me. I bring alot more to the table than I take, though so granted the opportunity to build on Osmosis, Osmosis wins, too.

Atom Registry

1 Like