Create an account
A smart account, deployed from this browser and owned by a key generated in it. No wallet, no sign-in, and nothing of yours on a Limen server — the fee is paid by a testnet account friendbot funds a few seconds before it is spent.
The owner key is disposable and cannot be exported. Clearing this browser’s site data destroys it, and with it the account it owns. That is stated here rather than discovered later.
Generate the two keys
An owner key and an agent key, both created in this browser. The owner installs boundaries; the agent is what the boundary is installed against.
Reading what this browser holds…
Fund them from friendbot
Both accounts pay their own fees. The agent holding its own funded account is what keeps any owner signature away from the agent's transactions later.
Friendbot is called from this page, not through a Limen route. No Limen server is in this write path at all, which also means no Limen rate limit applies to it — friendbot and the public RPC apply their own.
Deploy the smart account
createCustomContract, with the account wasm already uploaded to testnet and the owner key as its only signer.
The account contract is OpenZeppelin’s multisig smart account example, built from v0.7.2 and already on testnet. Limen writes no Rust and generates none. What is not audited is the code that decides what to install.
- account wasm hash
- 1815dda1b96ea6d23865be8a16ffcbe0b8336d15fc0d3d5ada776c06cb17afde
- ed25519 verifier