TLA Spec Sheet
Authoritative lifecycle states, supported actions, architecture, fees, and deployment provenance for the TLA stack.
Product Definition
TLA means Top Level Account. House of Stake leases NEAR top-level namespace accounts as transferable NFTs. A TLA such as acme defines a namespace. A rented name such as alice.acme becomes a real NEAR account within that namespace.
The account is not a wrapper or a database record. It has its own NEAR address, balance, and transaction history, and runs the hos-wallet contract with zero access keys. Ownership is contract state; the owner operates the account from a wallet they already control.
The registry mints each name as a NEP-171 token and records its owner. Authority runs from tla-registry to hos-extension to hos-wallet. The extension accepts force_transfer only from the registry.
Source status. Contracts frozen for security review at a61b807, tagged valhalla-2026-08-3. Verified against 18 August 2026. This page describes the mainnet architecture.
TLA Lifecycle States
| State | Definition |
| Registered | Namespace record exists before activation. |
| Active | The TLA lease is current. |
| Grace | The TLA lease has ended but remains renewable by its current controller. |
| Reclaimable | Grace has ended and the TLA can return to the allocation process. |
| Suspended | Namespace activity is paused. |
Rented-Name Lifecycle States
| State | Definition |
| Active | The name lease is current and the account can be operated normally. |
| Grace | The name lease has ended but remains renewable by its current owner. |
| Reclaimable | Grace has ended and the name can return to its namespace. |
Expired is a display condition, not a lifecycle state. The canonical lease sequence is Active → Grace → Reclaimable.
Supported Actions
| Action | Supported |
| Transfer | Yes |
| FunctionCall | Yes |
| DeterministicStateInit | Yes |
| AddKey / DeleteKey | No |
| DeleteAccount | No |
| DeployContract | No |
| Native validator actions | No |
The three supported external actions come from the upstream wallet action vocabulary. The excluded actions do not exist in the accepted action set, so the restriction is structural rather than a policy that could later be relaxed.
Component Responsibilities
| Component | Responsibility |
| Registry | Namespaces, names, leases, pricing, and marketplace state |
| Registrar | Creates a leased sub-account under the TLA root |
| Wallet implementation deployer | Publishes the shared hos-wallet implementation |
| Wallet | Runs supported actions and stores the account control set with zero access keys |
| Extension | Authority for leased wallets, ownership rotation, and expiry sweeps |
| Recovery | Attestation, timelock, watcher quorum, and owner update |
| Indexer and services | Mirror chain state, run product workflows, and provide isolated recovery services |
Pricing and Fees
- Rent starts with a USD base band and converts to NEAR at quote time through the rate oracle.
- Base annual rent is $50 for 0–5 characters, $20 for 6–8, $10 for 9–10, and $5 for 11 or more.
- Legendary, Premium, Standard, and Public Goods / Community categories remain product policy; the current multipliers are 5x, 3x, and 1.5x for the first three categories.
- TLA allocation is $1,000, a business sub-account costs $0.50 at mint, and the account-creation deposit is 0.01 NEAR passed to the new account.
- Resale commission is zero. Exact NEAR amounts come from the current quote.
Marketplace and Recovery
Resale settles through NEAR Intents rather than an on-chain marketplace contract. A name enters Intents custody with nft_transfer_call, a signed two-sided swap settles atomically, and the buyer withdraws the name with nft_withdraw.
Recovery has three independent gates: attestation, timelock, and watcher quorum. The watcher threshold has a floor of two, so no deployment can permit a solo recovery.
Contract Identifiers
Contract account IDs are deployment-specific. Integrations should read them from the active environment configuration and verify them against the deployment record before operating against the deployment.