HOME / PROTOCOL / ROADMAP

Where RHNS is going.

What is built, what is shipping next, and how yourname.rbh becomes yourname.rname.eth in every ENS-aware wallet. Updated as things actually ship.

✓

// PHASE 00

complete

Foundation

The full machine, built and tested end to end on a development chain: every layer below has real code behind it, exercised by automated tests and live registration runs.

✓Registry contract: ownership, expiry with 90-day grace, versioned records, reverse records

✓Registrar contract: commit-reveal registration, USD pricing paid in ETH via price feed, refunds, reserved names[18 automated tests]

✓Event indexer mirroring the chain into PostgreSQL

✓Public REST API: search, resolve, reverse, owner listings, transaction preparation, live stats

✓CCIP-read gateway answering ENS queries with onchain-verifiable signatures[byte-exact wallet query verified]

✓Web app: search, 3-step registration flow, name management, wallet connect via RainbowKit + WalletConnect

✓Honest content pass: every number on this site is real or labeled planned

// PHASE 01

up next

Public testnet

Everything moves from one developer machine to public infrastructure, with free test names so anyone can try the full flow before real money is involved.

→Deploy contracts to a public testnet (Arbitrum Sepolia, same stack as Robinhood Chain)

→Host the API, gateway, and indexer publicly at api.rhns.domains

→Real-wallet beta: registrations tested through MetaMask and WalletConnect by real users

→rhns.domains DNS, mailboxes, and the site deployed publicly

// PHASE 02

planned

Mainnet on Robinhood Chain

The real launch: .rbh names on Robinhood Chain (chain id 4663, RPC already verified live), with revenue flowing to a treasury the future DAO will control.

·Deploy registry and registrar to Robinhood Chain with verified source

·Production ETH/USD price feed (Chainlink if available on the chain, secured fallback otherwise)

·Treasury moved to a multisig; contract ownership hardened

·Reserved-names list finalized (brand protection, abuse prevention)

·Security audit of the registry and registrar before revenue scales

// PHASE 03

planned

The rname.eth bridge goes live

The headline feature: every name registered on Robinhood Chain becomes visible to the entire ENS world. The pipeline is already built and cryptographically verified in testing; what remains is switching it on with two Ethereum transactions.

✓How it works: wallets ask Ethereum for jonah.rname.eth, the resolver defers to the RHNS gateway via CCIP-read (ERC-3668), the gateway answers from the Robinhood Chain registry and signs, and the resolver verifies that signature onchain[built + signature-verified]

·Deploy the OffchainResolver contract to Ethereum mainnet

·Point rname.eth at it in the ENS registry (one transaction by the domain owner)

·From that moment: yourname.rbh resolves as yourname.rname.eth in MetaMask, Rainbow, Coinbase Wallet, Uniswap, Farcaster, Etherscan, and every ENS-aware product, with no per-name mainnet gas

·Round-trip monitoring: continuous checks that L1 answers match L2 state

// PHASE 04

planned

Full name management

The contracts already support more than the app exposes. This phase closes that gap and makes names tradable assets.

·Records editor in the app: avatar, website, social handles, contenthash[contract support already live]

·Transfer UI: send a name to any address from My names[contract support already live]

·ERC-721 wrapping so names trade on standard NFT marketplaces

·Subnames: issue names under yours for teams and communities

·Multi-coin address records beyond ETH

// PHASE 05

planned

Decentralization

RHNS ends up owned by its users. No token exists today, and anyone claiming to sell one before this phase ships is scamming you.

·Governance token and DAO: pricing, treasury, and roadmap decided by holders

·Vote and Delegate move from labeled previews to live onchain governance

·Grants program funded by protocol revenue

·Community forum and public working groups

·Paid bug bounty once the protocol secures meaningful value

// HOW .RBH AND RNAME.ETH STAY IN SYNC

One record, two names, zero drift

There is no syncing, because there is nothing to sync. A registration is a single record on Robinhood Chain; jonah.rbh and jonah.rname.eth are two ways of reading it. Change the owner, an address, or a text record once, and both names reflect it immediately, everywhere.

MetaMask asks: who is jonah.rname.eth?
Ethereum resolver: ask the RHNS gateway (ERC-3668 CCIP-read)
Gateway: reads the registry on Robinhood Chain, signs the answer
Ethereum resolver: verifies the signature onchain ✓
MetaMask shows: jonah.rname.eth → 0x7099…79C8

Want to shape what ships first?

Early feedback moves items up this page. Tell us what you need.

Get in touch →