Skip to main content
Use the Soran console to run your namespace. You can issue names, let users claim them in your app, enable additional address networks and subnames, and invite operators to help. If you hold a name and want to change its receiving details or profile, start with Managing your name. Holder records are managed through the public name page or Holder SDK.

​
Wallet sign-in

  1. Open the console and connect your wallet.
  2. Review and sign the short-lived, one-time sign-in challenge. It authenticates your account without submitting a network transaction.
  3. Select a namespace you own on chain or operate through a console invitation.
Switching namespaces changes your access scope. Signing out ends the server session. If you do not yet own a namespace, use Register namespace to begin the public allocation process. The current public deployment uses Stellar testnet. Check the app and network in your wallet before signing an on-chain action.

​
Common flows

Billing and Marketplace provide optional commercial features when enabled on a deployment. They are separate from the protocol’s naming and resolution functions. For a new namespace, begin with activation in Issuance, choose your registration approach, then enable any additional features you want to offer. Each on-chain change needs its authorized signer and a confirmed transaction.

​
Username registration

  1. Open Username registration with the current namespace owner’s wallet.
  2. Choose Owner-issued names or Self-service claims.
  3. For self-service claims, choose open registration, invited wallets or eligible users approved by your app. Set the username price, receiving G treasury and cumulative wallet limit.
  4. If your app approves eligibility, configure a separate approval account and its budgets.
  5. Reserve administrative labels, review the settings and enable claiming when your app integration is ready.
Reserved assignment lets you issue an administrative label while keeping it reserved. Self-service mode replaces ordinary owner issuance, even while claims are paused. Your signup or account page uses the Owner and Holder SDKs. Users can choose and authorize their names there without visiting the Soran console. The maximum network fee starts at 5 XLM per transaction, separate from the username price. It is a ceiling, not the amount charged. Review the estimate before increasing it. After an interrupted submission, use Check transaction before making another change.

​
Enable networks and subnames

Open Contract updates if your namespace needs newer contracts. Network addresses need a compatible Resolver; subnames need compatible Registrar and Resolver contracts. An updated app alone does not change those contracts. Then open Settings:
  • Network addresses chooses which additional networks holders may publish destinations for.
  • Subnames enables creation, stops new creation while preserving existing children, or suspends their use.
These choices apply to existing and future names. Installing an update does not enable the features automatically. Follow Enable networks and subnames for the exact policy effects. Holders can then add network addresses or create subnames on their public name pages. They can also publish profile records through the Holder SDK. Namespace administration does not grant permission to edit a holder’s Resolver records. In Sponsorship, you can cover supported network fees for username claims, namespace display-name elections and primary-name elections. Review the available coverage and set your funding limits before enabling a policy. Sponsoring a claim’s network fee does not pay the username price you configured. The user still authorizes the claim and any purchase price.

​
Operator roles

Console roles control access to the interface. Self-custody owner operations still require the owner’s signature; holder record changes and individual transfers require holder authority. A destination account authorizes its own reverse and Primary elections.

​
Custody modes

Self-custody: your wallet is the on-chain owner and signs prepared transactions. The server does not hold the signing authority for your namespace. Platform-operated: the deployment’s operating key owns and signs for the namespace. Permitted console actions use that signer. The mode depends on the on-chain owner key, not the namespace label.

​
Current ownership checks

The console checks the selected namespace’s current on-chain owner before allowing namespace administration. After a namespace transfer, the previous owner’s console team loses access. The new owner can refresh their wallet session, select the namespace and configure their own team or rotate webhook credentials. If current ownership cannot be read, management waits until that check succeeds. An indexer delay does not require you to transfer the namespace again. Public lookups and holder-authorized name operations have their own access rules. A transfer from All names moves an individual name. A whole namespace uses Registry’s separate proposal and acceptance process. After any interrupted write, check the original transaction before retrying. A successful simulation is an estimate and preflight check, not confirmation of a completed action.