soran.domainsALLOCATION POLICY

How namespaces are awarded

The rules the allocator follows, in plain language. The contract enforces the mechanics; this page explains the testnet deployment released on 05 Sep 2026.

01

What the allocator can and cannot do

The allocator assigns unclaimed namespaces. Its allocation methods cannot revoke, transfer or modify an awarded namespace. Shared contracts remain upgradeable through governance during testnet.

Names inside a namespace are governed by the namespace’s own policy — reclaim rights and ownership terms — separately from namespace allocation.

02

Making a claim

A claimant can request an unregistered, eligible namespace. A claim states its basis and attaches evidence, all of which becomes public the moment it is announced. Evidence can include:

aRegistered trademark — filing number and jurisdiction.
bDNS control — a TXT record on the matching domain. You can check it before announcing; if the claim is disputed, it's weighed against the live DNS record during the objection window.
cCommercial first use — public evidence of operating under the name.

The contract records the submitted basis; it does not decide trademark or DNS rights. Governance evaluates disputed claims.

03

The public window

Each public Allocator claim sits in the public queue for a fixed window — one day on this testnet deployment (see each claim's live countdown on the queue). Unopposed claims are executable by anyone once the window ends — no human approves them. An objection freezes the clock for that claim until the objection is resolved. Claimants may withdraw a pending claim; withdrawing a claim that is under objection concedes it and consumes a minimum claim-age budget. Announced time counts toward a cumulative 30-day claim-age limit; time under objection is paused. After an objection remains unresolved for 30 days, anyone can resume the remaining claim window on chain.

04

Objections

An eligible account other than the claimant or governance may object during the window by stating a competing basis. Objections are public and bonded — this testnet deployment requires a 1 XLM bond. The bond is returned when an objection is upheld or the claimant concedes. Dismissed or timed-out objections forfeit the bond: it is burned, or stays permanently locked if the token cannot burn. Grounds can include a competing mark, prior use, and confusable similarity to an existing namespace.

Governance either upholds the objection, rejecting the claim, or dismisses it, resuming the remaining window. The contract records that outcome on chain. It does not split namespace ownership by jurisdiction.

05

Execution and irreversibility

Execution assigns the namespace to the claimant’s account and permanently ends the allocator’s authority over it. There is no administrative reversal. A wrongly awarded namespace can only change hands the way any owned namespace can: by its owner’s signature.

06

Fees

Public namespace claims currently pay 5,000 testnet XLM upfront into the Allocator. Check the live on-chain quote before signing. Awarded claims pay the configured recipient. Rejected or provably stuck claims receive 100%; withdrawn or expired claims receive 80%, with 20% retained. Only valid bound reserved direct claims are exempt. A provably stuck claim is one whose namespace is already owned in the Registry; the full refund also applies when it was under objection. Failed payouts remain recoverable as on-chain credit. Network fees and objection bonds are separate. No yearly name maintenance fee is charged; hosted subscription billing is disabled in this testnet release.