Skip to main content
Once you own a namespace, you can issue names yourself or let users claim them in your app. First activate the namespace’s Registrar and native Resolver, then choose how registration should work. The upfront namespace fee and any price you set for usernames are separate.

​
Activate the namespace

  1. Choose the Registrar policy, including reclaimability, transfers and the default name term.
  2. Review the prepared deployment and sign with the namespace owner’s wallet.
  3. Deploy and configure the native Resolver to store payment and profile records.
An admin or issuer console role does not replace the owner’s on-chain signature. If submission is interrupted, check its outcome before retrying. A reclaimable policy lets the owner reclaim names under its rules. A zero-term, non-reclaimable policy gives names no expiry, but code and routing remain unlocked until the permanence transition succeeds.

​
Automatic branded contract addresses

The console searches for a C?SORAN... address when preparing a new Registrar or native Resolver. Here ? is Stellar’s second address character: A, B, C or D. You can follow progress or cancel before signing. Search time varies, and you can restart a canceled or failed search. The contract exists only after its deployment transaction is confirmed. The preparation service searches public nonces without your signing key. Registry still verifies the owner and derives the namespace-specific contract address. Individual names are records within these contracts. Existing contract addresses do not change. Direct callers may choose ordinary addresses, so verify Registry routing rather than a SORAN prefix.

​
Issue names

For manual or reserved issuance, supply a canonical label and valid holder address. The initial payment target is the holder. The holder can then publish a different address and optional memo through the Resolver. For Public mode, follow automatic username claiming to integrate registration into your app. The console supports single issuance and CSV workflows with per-row outcomes. The Owner SDK supports batches of at most 23 names per transaction. Check confirmed outcomes and uncertain transaction hashes before retrying a row.

​
Fees

You can make public username claims free or set a flat native XLM price paid directly to your G treasury. Choose a treasury that does not require a deposit memo. The contracts add no mandatory annual ownership charge or separate holder renewal fee. Stellar transaction fees and storage rent still apply; use the current transaction estimate. When enabled on a deployment, managed billing can charge for hosted services. A namespace owner can also offer its own commercial service or timed names under its disclosed contract policy. These costs are distinct from the upfront top-level namespace claim fee.

​
Dormancy, TTL and restoration

A hosted cold label means the service considers a name dormant. It does not establish on-chain archival or end ownership. A keeper can extend relevant contract and record TTLs while they are available. Archived entries may need restoration before payment resolution succeeds. The hosted API does not substitute a database destination for a failed on-chain read. Cached profiles can show history, but payments need current instructions.

​
Who can change what

Console team roles do not combine these separate authorities.