Developer Resources
Deployment Status
Implementation Status
| Capability | Repository status | Public limitation |
| Name rental | Maintenance | Verify the deployed contract IDs before integrating. |
| Marketplace | Maintenance | Resale settles through Intents, not a TLA marketplace contract. Intents settlement is mainnet-only. |
| Keyless account operation | Maintenance | Rented accounts have zero access keys and run hos-wallet. |
| Fast-auth sign-in | Coming soon | Fast-auth setup and account-control instructions will be added when it is available. |
| Recovery | Maintenance | The recovery flow waits 72 hours before it can finish. |
| Business TLAs | Handled case by case | The current frontend has no self-service business application. |
| Security review | Complete | The review covers the frozen source snapshot. Confirm the active deployment and its contract hashes independently. |
Service Limitations
See Technical Overview for the supported action boundary.
- Marketplace resale requires NEAR Intents. Intents settlement is mainnet-only.
- Recovery requires a complete on-chain policy, MPC recovery key, mail delivery, and watcher-service configuration. The console mail fallback does not deliver messages.
Internal partner agreements, stale service keys, scheduled calls, and private deployment blockers are intentionally excluded from public documentation.
Deployment Contract IDs
Contract account IDs depend on the deployment. Read them from the active environment configuration and verify them against the deployment record before use.