Skip to content
txcasttxcasttxcast docs

Review, sign, and execute a Safe batch

A Safe evm.transactions list is one atomic batch. txcast supports Safe 1.3.0 and 1.4.1 and does not hold owner keys.

Preparation

Section titled “Preparation”

When the transaction effect reaches the front of its account lane, txcast reads latest Safe state and freezes:

  • chain and Safe address;
  • Safe version, nonce, owners, and threshold;
  • one direct call or an ordered MultiSendCallOnly batch;
  • typed data, Safe transaction hash, and evidence digests.

Preparation makes no Safe Transaction Service (STS) write and does not open a wallet.

Sign

Section titled “Sign”
  1. Verify the frozen call list, nonce, owners, threshold, and typed data.
  2. Connect an eligible owner wallet.
  3. Sign the exact Safe transaction hash.
  4. Submit the signature to txcast.

Signature bytes are write-only and attempt-scoped. txcast revalidates current Safe state and the signer before every STS mutation. The first accepted owner signature creates or reconciles the proposal; later signatures add confirmations. Ambiguous STS replies are reconciled by exact Safe transaction hash and signer.

Reaching threshold changes the attempt to Ready to execute. It does not broadcast anything.

Execute

Section titled “Execute”

An eligible Safe owner acquires the execution claim, reviews the final wallet request, and executes it. Record the resulting transaction hash immediately. txcast confirms the exact Safe execution receipt before succeeding the effect.

Reject

Section titled “Reject”

An eligible participant may reject a prepared proposal with a reason. Organisation admins can perform a clearly acknowledged, audited override. A rejection is a txcast coordination action; it does not reverse any provider or chain side effect that already escaped.

Conflicts and cancellation

Section titled “Conflicts and cancellation”

If Safe nonce, owners, threshold, or version changes, the stale attempt is invalidated. Refresh the run and prepare new work. Once an STS write or transaction broadcast may have occurred, the account remains fenced until txcast reconciles authoritative state, even if the run is cancelled.