Propose, sign, and execute a Safe step

Prepare a proposal

1. Open a ready Safe step.
2. Review the Safe address, chain, nonce, owners, and threshold.
3. Review every transaction in the prepared Safe payload.
4. Prepare the proposal and confirm the safeTxHash shown by txcast and your signing client.

txcast uses current Safe state and submits proposal data through the Safe Transaction Service (STS). STS helps coordinate proposals and signatures; the Safe contract remains the execution authority.

Submit signatures

Each owner signs the exact EIP-712 typed data outside txcast. txcast cryptographically verifies the signer and durably records the submission before calling STS. It never stores a private key.

Multiple owners can submit compatible signatures concurrently. A duplicate signer or stale attempt returns a conflict rather than overwriting another signature.

Execute after threshold

1. Request the Safe execution transaction from txcast.
2. Confirm the expected chain, Safe address, assembled calldata, and run link.
3. Sign and broadcast it through an external wallet.
4. Record the resulting transaction hash in txcast.
5. Wait for sync to verify the matching Safe ExecutionSuccess event and confirmation depth.

Caution

An outer transaction receipt with status = success is not enough. txcast requires the expected Safe event for the prepared Safe transaction hash.

Outside activity

A competing same-nonce proposal, onchain rejection, owner change, threshold change, or separately executed Safe transaction can invalidate or replace the attempt. Refresh and sync before signing. See rejections and conflicts.