Organisation execution accounts

Execution accounts are organisation-owned choices for evm.transactions effects. They are separate from personal wallets and address-book targets.

Register an account

1. Open Execution accounts for the current organisation.
2. Choose Safe or EOA.
3. Enter the address and select its supported chains.
4. Give it a name that distinguishes purpose and environment.
5. Save the account.

Organisation owners and admins may perform the same CRUD operations through MCP or Agent REST with registry.write. Agent updates and deletions require the latest updatedAt value, and clients should reconcile by reading the exact address before retrying an indeterminate creation.

Future chains added to the same controlled-account record remain part of that account. Agent credentials with a selected grant reference the account ID; an all grant dynamically includes current and future accounts.

Choose between Safe and EOA

Use a Safe when multiple owners, threshold review, and coordinated execution are appropriate. Use an EOA only when a single connected wallet should submit transactions directly.

EOA batches are ordered but not atomic: the wallet signs and broadcasts each transaction separately. A later transaction may fail after earlier ones have succeeded.

Before using an account

• Verify the checksum address and chain.
• Confirm that intended operators have the relevant personal wallet or Safe authority.
• Use a recognisable name such as “Treasury Safe — Ethereum”.
• Test with a low-risk workflow before production use.

Review a Safe’s live configuration

Open a registered Safe to compare the account saved in txcast with its current onchain configuration. The account page shows:

• the Safe contract version;
• every current signer address; and
• the number of confirmations required out of the current signer count.

The snapshot is read directly from the selected network at one block. txcast caches it for up to 30 seconds and shows the block number and read time. Choose Refresh when you need a newer snapshot; manual refreshes are rate-limited to protect the configured RPC. A failed or stale read does not change the Safe or the controlled-account record.

Choose Open in Safe to inspect the same address in the official Safe web app. If an account is registered on more than one chain, select the chain whose configuration you want to review first.

Safe configuration is informational. Signer and threshold changes must still be proposed and executed through Safe; txcast never changes them from this page.

Removing a chain or account prevents new authoring and execution through it. It does not rewrite existing workflow revisions or reverse onchain activity.

Deleting an account also removes immutable selected credential-account references to that account. Credentials with all account access dynamically include newly created accounts; selected grants are never widened automatically.