sorandomains What you get Register a namespace
Owning a namespace

Everything that comes with .yourbrand

A namespace is a contract pair you control, plus a set of features your holders can switch on. Each one below is live on Stellar testnet and documented in the Soran docs.

01 · Features for your holders

One name. A destination, an identity and a profile.

You enable the features; your holders publish their own records. Namespace ownership never grants permission to edit a holder's records.

Subnames

pay.alice.yourbrand

Holders add one child level beneath their name, each with its own receiving address. The parent holder stays in control; children follow the parent's lifetime. You set one policy for the whole namespace.

enabled creation-disabled suspended
alice.yourbrandGDHODRBD…IIE2 · memo 48213
↳ pay.alice.yourbrandGCOOXIOQ…F67JQ
↳ shop.alice.yourbrandM… muxed · id 4471
StellarGDHODRBD…IIE2 · memo 48213
Ethereum0x4bD1…9e2A
Bitcoinbc1qx7…m4ql
Solanadisabled by namespace
Network addresses

One name, every chain you allow.

You choose which networks holders may use. Each holder publishes one mainnet receiving address per enabled network. The sender picks the network; no swap or bridge is performed. Disabling a network hides its records without deleting them.

Profiles, display names and Primary

A wallet address that introduces itself.

Holders attach an avatar, description, website and social handles to their name, then elect it as the display name for their address, or as their Primary name across every namespace. Supporting wallets show the name and profile beside the address. Every record is holder-signed; the Resolver verifies authorship, not identity.

avatarhttps://alice.design/me.png
The URL of the holder's profile image. Supporting wallets show it beside the address.
a alice.yourbrandPRIMARY Designer · Lisbon · alice.design
received from alice.yourbrand+120 XLM
02 · Setting the rules

You write the policy. The contract applies it.

Lifecycle rules are fixed when you activate your Registrar. Registration rules can change later with another signed transaction.

Ownership policy · at activation What every name under you promises
reclaimablewhether you may reclaim usernames
transferablewhether holders may transfer to another wallet
default_termno expiry, or 1 day to 100 years
Wallets read this policy next to every payment. There is no ordinary setter after activation.
Registration · changeable Who can claim, and for how much
●Manual issuance, or Public claims inside your app
●Open, invitation list, or app-approved admission
●Free, or a flat XLM price paid straight to your treasury
●Per-wallet claim limits · reserved labels · pause at any time
Pausing never revokes issued names. Reserved labels can be assigned to whoever you choose.
Your contracts A Registrar and Resolver of your own Each namespace gets its own contract pair, with branded C?SORAN… addresses prepared by the console. You choose which governance-approved implementation to run and authorize every upgrade yourself; a newer SDK alone can't change your contracts.
03 · Platform

Built to be integrated, not just owned.

Universal Lookup Any wallet resolves your names Universal Lookup returns the payment destination and routing details. Read policy and profile records separately on chain. No Soran account or API key is needed.
Tooling Owner SDK · Holder SDK · HTTP API · MCP Issue from code in batches of 23, claim from your signup flow, or drive the console from an agent. Every write is signed by the right wallet.
Signed webhooks issued · reclaimed · transferred HMAC-signed deliveries to your backend, with up to six delivery attempts. Deduplicate by delivery ID. The event archive covers everything else.
Sponsored claims Pay the network fee for your users Fund a position and the relayer covers Stellar fees for successful claims and name elections. Settled only when the action succeeds.
04 · Guarantees

What nobody can do to your namespace.

0 Per-name or yearly Soran fee The contracts add no mandatory annual ownership charge and no holder renewal fee. You pay the namespace claim once; Stellar transaction and storage costs are separate.
1 Owner-authorized namespace transfers Allocation methods cannot reassign an awarded namespace. Transfers require your proposal and the recipient's acceptance. A console login confers no ownership; testnet governance upgrades remain a separate authority.
◇ Policy that wallets can read Reclaim rights, expiry and upgrade authority are on chain, separately from payment instructions. Holders see exactly what can happen to their name before they accept it.
Testnet note Shared contracts stay upgradeable through governance during testnet, and new permanence locks are rejected. A no-expiry, no-reclaim policy does not remove upgrade authority.
05 · Lifecycle

Three lifecycle operations, authorized on chain.

reclaimTake a name back
Only where your policy permits it. The name returns to your treasury; the holder's records stop appearing. Wallets name you explicitly as the issuer who can reclaim.
renewExtend a finite name
Add time to any time-bound name, up to 100 years out. Set up to 90 days of renewal grace so an expired name can't be reissued while its holder renews. Holders renew their own names without a fee from Soran.
transferHand over the namespace
You propose; the new owner accepts with their own wallet. Ownership moves on acceptance, your claim settings are disabled, and holders' records and renewal rights carry on untouched.
Register a namespace Read the docs ↗