Skip to content

Core concepts

An organisation owns shared workflows, runs, controlled accounts, address-book entries, billing, and audit history. Your role and seat determine what you can do.

A personal wallet belongs to one txcast user and proves which address that user can use for signing or proposing. It is not automatically an organisation execution account.

An organisation execution account is a Safe or EOA that workflow steps are allowed to execute from. It is separate from both personal wallets and address-book entries.

The address book stores known addresses. A contract capability adds a saved ABI on a particular chain, allowing txcast to validate function calls and encode arguments. An address can be useful without being an execution account.

A workflow is a reusable transaction template. It can contain:

  • transaction steps and ordered transaction batches;
  • required or computed variables;
  • explicit dependency edges;
  • onchain conditions; and
  • audited manual checkpoints.

The editor maintains a draft. Save changes publishes an immutable revision.

A run is an executable instance of one workflow revision. A staged run can change variables. Publishing freezes its rendered transactions and begins coordination.

An attempt records work on one transaction step, such as a Safe proposal, an ordered wallet execution, a Safe rejection, or a verified completion performed outside txcast.

txcast coordinates and records intent, but chain state, transaction receipts, wallet signatures, and Safe state remain authoritative. A green workflow definition is not a guarantee that balances, owners, thresholds, or contract state will remain unchanged before execution.