Ways to configure an account
There is more than one way to set up a Bloxchain smart account. Pick the route that matches who is doing the work and how often you will repeat it.
Where: Discover, inside an account, or your own tooling · You need: a wallet with a role that may sign the change
The five routes
Every route ends in the same place: a signed change that the account contract checks against its own policy. The chain does not care which one you used.
You are making a handful of changes and want to see what each one does
Your wallet, per batch
The wallet that decides is not on the machine that broadcasts
The approver, then a broadcaster
You are configuring many accounts, or the setup must be repeatable
Your script's key, or a wallet client
You want a draft prepared for you, and you will review it
The agent, then a person broadcasts
Presets
Discover lists first-party presets: Personal security, Treasury, Asset issuance. Choosing one deploys a governed account in a single transaction.
Today every preset deploys the same governed account, and it lands as a Vault: a finished, locked account with no spending capability yet (what that means). Capabilities are added afterwards through one of the routes below. A preset is a starting point, not a finished configuration.
Trade-off: fastest to a working account, but it does not wire roles or permissions for you.
See Discover presets.
The Platform UI
Inside an account, Policies holds Security, Actions, Gates and the allowlists, and On-chain access holds Signers and Roles. You change one thing at a time, the Platform batches the change, and you sign it.
Trade-off: the clearest route, because each screen tells you what is missing (Flow incomplete, gate gaps, empty allowlists). It is also the slowest if you have twenty accounts to set up.
See Policies and On-chain access.
Signed files
A signed change can be exported as a .bloxmeta.json file, carried to another device, imported and broadcast there. This covers an air-gapped signer, a hardware wallet on a separate laptop, and a team where the person who decides is not the person who pays gas.
Trade-off: no relay and no sign-in are needed, but the file is a bearer instrument and it expires.
See Signed files and Approve from another device.
The SDK
The Protocol's TypeScript SDK does everything the Platform does: register actions, create roles, assign permissions per step, grant gates, manage allowlists. A script can configure a new account the same way every time, and run in CI.
Trade-off: repeatable and reviewable in source control, but you own the key handling and the error paths.
Agent-assisted
An AI agent holding a narrowly permitted signer key can draft and sign a request or a configuration change. You import the file, read the decoded preview and broadcast it. The agent never holds the broadcaster key or the owner key, and the on-chain policy still constrains everything it signs.
Trade-off: useful for drafting and for repetitive work, and a person still decides. More AI tooling is in development.
Mixing routes
Most accounts use more than one. A common pattern is a preset to deploy, the Platform UI for Security and the first actions, then the SDK or an agent for the repetitive parts, with signed files whenever the approving wallet is somewhere else.
Related
Last updated
Was this helpful?