The agent's identity is just a Sui address, derived from a locally-stored Ed25519 keypair. lyra init generates a fresh agent wallet and writes a local encrypted keystore. There is no on-chain mint, no NFT, and no operator signature required to get started; the identity is just an address that holds SUI and signs the transactions the agent is allowed to send.
The agent wallet is the Sui address that pays gas and is the sender of every write the agent executes. Fund it with a little SUI and the agent can transact within the limits you set. The private key is stored locally in an encrypted keystore, never sent to the model and never required to live anywhere but the operator's machine.
The identity is deliberately boring. The interesting part is the boundary around it: the policy engine. What the agent can do with its wallet is decided entirely by deterministic configuration, not by the address itself.
| Control | Configured by | Effect |
|---|---|---|
| Hard caps | LYRA_POLICY_MAX_NATIVE_SUI, slippage caps | Block any action over the limit. |
| Allowlists | LYRA_POLICY_RECIPIENT_ALLOWLIST, LYRA_POLICY_TOKEN_ALLOWLIST | Restrict recipients and tokens. |
| Autonomy tier | LYRA_POLICY_AUTONOMY (auto / confirm / readonly) | How much the agent may do without a prompt. |
| Read-only | LYRA_POLICY_READONLY | Reject all writes outright. |
These live in code and environment, so the boundary is the same whether the request arrives from the terminal, Telegram, or the web console.
https://fullnode.mainnet.sui.io:443, explorer https://suiscan.xyz.https://fullnode.testnet.sui.io:443, explorer https://suiscan.xyz/testnet.Start on Sui testnet for exploratory work, then move to mainnet once your policy is set the way you want it.
Read Memory next.
Source: README.md.
Source: README.md