Developer Docs
Integration boundaries for wallets, applications, and contracts.
Product users do not need these mechanics to rent or operate an account.
Operating an Account
The owner sends a transaction from an account they already control and calls the leased account’s wallet. The wallet checks that the caller is an enabled extension, that the lease is active, and that the account is not frozen.
The wallet executes the requested action with the leased account as predecessor. Staking delegation, liquid staking, DeFi, and other contract interactions work through ordinary function calls. Native validator registration is excluded because it needs a key.
Actions Available to Integrators
| Action | Supported | Notes |
| Transfer | Yes | Transfers NEAR from the operated 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 are the actions available to integrators, not a complete list of every NEAR protocol action. AddKey, DeleteKey, DeleteAccount, and DeployContract do not exist in the action set the wallet accepts. The guarantee is structural, not a policy that could be relaxed later.
Integration Boundary
Leased accounts have no access keys. The owner controls the account through a wallet they already control, while recovery, payment, notification, and other product capabilities depend on their configured services.