Technical Overview
This page explains the system and integration boundaries for wallets, applications, and contracts. Product users do not need these mechanics to rent or use an account.
System Architecture
NEAR Accounts opens new Top Level Accounts where people can rent real NEAR accounts. Each rented account runs the hos-wallet contract and has no access keys of its own. An ownership account controls it. For now, the ownership account comes from an existing NEAR wallet.
The registry mints each name as a NEP-171 token and records the owner. The rented account also records its owner, so both records must agree. Authority flows through tla-registry to hos-extension to hos-wallet. The extension accepts force_transfer only from the registry.
The owner sends a transaction from an account already under their control and calls the rented account's wallet. The wallet checks the caller, extension membership, lease state, and freeze state. It then runs the supported action with the rented account as predecessor. Nothing signs on behalf of the rented account.
Component Responsibilities
| Component | Responsibility |
| Frontend | Search, rental, marketplace, account management, recovery setup, and owner verification |
| The House of Stake backend | Orders, payments, product state, recovery orchestration, and operational records |
| TLA registry | NEP-171 names, leases, owners, pricing, treasury, and lifecycle |
| Registrar | Creates rented sub-accounts under the TLA root |
| Wallet implementation deployer | Publishes the shared hos-wallet implementation |
| Wallet | Holds the account’s control set and runs supported actions with zero access keys |
| Extension | Authority for rented wallets, ownership rotation, and expiry sweeps |
| Recovery | Signed confirmation, 72-hour wait, watcher approval, shared signing, and owner updates |
| Indexer and services | Mirror chain state, run product workflows, and keep recovery watcher services separate |
Operation Flow
- The owner sends a transaction from an account named in the rented wallet’s control set.
- The owner’s wallet calls
w_execute_extensionwith the exact supported actions. - The rented wallet checks extension membership, caller authority, lease state, and freeze state.
- The actions execute with the rented account as predecessor.
Actions Available to Integrators
| Action | Supported | Notes |
| Transfer | Yes | Transfers NEAR from the rented account. |
| FunctionCall | Yes | Calls a NEAR contract with explicit method, arguments, gas, and deposit. |
| DeterministicStateInit | Yes | Creates deterministic state using the wallet's initialization rules. |
These actions are the complete external action set accepted by the wallet. AddKey, DeleteKey, DeleteAccount, and DeployContract are not part of that set. The restriction is structural, not a policy setting.
Staking delegation, liquid staking, DeFi, and other contract interactions work through FunctionCall. Native validator registration is excluded because it requires an access key.
Integration Boundary
Rented accounts have no access keys. The owner controls a rented account through a wallet they already control. Recovery, payment, notifications, and other product features depend on the services that support them.
Ownership Transfer & Recovery
For a normal sale or transfer during an active lease, the current owner must approve. The lease authority (the system that manages the rental) cannot transfer the name by itself. When ownership changes, supported NEAR and fungible-token balances are sent to the outgoing owner's recorded payout account before the new owner takes control. NFTs and assets held through other contracts are not automatically swept. A separate recovery process can transfer the name to a new owner account after the recovery checks pass.
After Grace ends, the account becomes Reclaimable. The lease authority can take it back without a new signature from the owner. It can also destroy or release the lease token. This is a non-fungible token (NFT), a unique digital token that represents the rental. The lease rules decide which NEAR and supported regular tokens (fungible tokens that can be exchanged one-for-one) get sent. The system sends them to the address saved for payouts, not to House of Stake's treasury account.
When ownership changes, all recovery information connected to the transferred account is cleared; nothing from the previous owner carries over. Recovery also checks that the expected owner is still current before applying the update.
Turn on recovery before you lose access. For each request, enter the code sent to your saved email and complete one recovery method you set up. The recovery service signs a confirmation that those checks passed. The request waits 72 hours, then a group of independent reviewers—the watchers—must approve it.
Using the account or changing its owner before recovery finishes cancels the request. Recovery protects the ownership account and every rented account it controls. After a successful recovery of a regular NEAR account, the shared recovery key and rules stay on the ownership account until you remove them. See the Recovery Overview for setup requirements.