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.
You enable the features; your holders publish their own records. Namespace ownership never grants permission to edit a holder's records.
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.
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.
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.pngLifecycle rules are fixed when you activate your Registrar. Registration rules can change later with another signed transaction.
reclaimablewhether you may reclaim usernamestransferablewhether holders may transfer to another walletdefault_termno expiry, or 1 day to 100 yearsC?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.