Safe Transaction Builder
Every admin change prepared for your multisig to review and sign.
What it does
The most dangerous actions on a platform are administrative: changing a compliance rule, adding a trusted issuer, upgrading a contract, moving a treasury balance. This module is designed so none of them is a single person clicking a button. A change is prepared as a transaction, described in terms a reviewer can actually assess, and queued for a multisig to examine and sign — so the people approving it can see what it does before it does it. In development.
How it works
The Safe Transaction Builder sits between an intention and an execution. Timelock & Execution can then delay a signed change, and the Audit Trail records who approved it.
Select a step to replay it. Hover to pause.
Step 1 of 3: Prepare. An administrative change is built as a transaction rather than executed on the spot.
Key capabilities
Changes prepared, not executed
A consequential action is staged for review instead of taking effect immediately.
Human-readable description
A signer sees what the transaction does, not only the bytes it contains.
Multisig review and signing
More than one person is required for the actions that matter most.
A record of who approved
Every approved change carries the signers behind it.