alice.nova whether someone wants to send you assets on Stellar, Bitcoin, Ethereum or another supported network. Your name can publish a separate receiving address for each network your namespace enables.
The sender chooses the network. Their app looks up that network’s record, shows the destination and asks them to approve the transfer. The name stays familiar while the underlying addresses remain distinct.
How it works
Imagine Alice uses Ethereum for one project and Base for another. She can save an Ethereum address and a Base address under the same name. An app resolvingalice.nova for Base reads the Base record. It does not assume the Ethereum address is also valid for Base, even though both networks use 0x addresses.
These records live in Soran’s Resolver contracts on Stellar. They identify destinations on other networks; Soran does not move funds between those networks, swap assets or bridge a payment. The sending wallet still needs to support the chosen network and asset.
The additional network records use mainnet receiving addresses, including when the Soran naming contracts are on Stellar testnet. The naming network and the destination network are separate choices.
Supported networks
The current address formats cover these 14 networks:
Stellar uses its own payment instructions, including optional memos and complete muxed addresses. Those instructions remain separate from other-network records.
For XRP Ledger, a full mainnet X-address preserves a required destination tag. XRPL EVM is a separate network with its own
0x record.