safe
Safe multisig operations: propose and execute transactions, manage owners and threshold, attach guards, and install Zodiac modules.
⚗️ Experimental — available at next.evmcrispr.com.
load safeConfiguration variables
Section titled “Configuration variables”Config variables are set with set (fully qualified, including the module prefix) and are only readable by their own module and the user script.
| Variable | Type | Default | Description |
|---|---|---|---|
$safe:serviceUrl | string | — | Custom Safe transaction-service endpoint for the current chain. |
$safe:apiKey | string | — | API key sent to the Safe transaction service. |
Commands
Section titled “Commands”| Command | Description |
|---|---|
| safe:add-owner | Add an owner to the Safe, optionally updating the threshold (keeps the current one by default). |
| safe:change-threshold | Change the signature threshold of the Safe. |
| safe:confirm | Confirm a Safe transaction or Safe message queued on the Safe Transaction Service, as an owner or through an owner Safe. |
| safe:confirm-offline | Sign a Safe transaction or Safe message as an owner, or through an owner Safe, and bind the signed JSON to a variable without posting it to the Safe Transaction Service. |
| safe:confirm-onchain | Confirm a Safe transaction or Safe message on-chain with approveHash, as an owner or through an owner Safe you complete alone, instead of signing it off-chain. |
| safe:delegate | Add or remove an account that proposes Safe transactions on the Safe Transaction Service on behalf of the connected owner, without confirming them. |
| safe:delegate-exec | Call a contract function via DELEGATECALL from the Safe. The code runs in the storage context of the Safe — only use audited libraries you trust. |
| safe:disable-module | Disable a module on the Safe. |
| safe:enable-module | Enable a module on the Safe, allowing it to execute transactions without owner signatures (e.g. a Zodiac module). |
| safe:execute | Execute a Safe transaction on-chain from a command block, cancel (a rejection of the pending transaction), the safeTxHash of a confirmed queued transaction, or signed Safe transaction JSON. |
| safe:install-delay | Deploy a Zodiac Delay modifier (timelock) owned by the Safe and enable it as a module. |
| safe:install-roles | Deploy a Zodiac Roles modifier (fine-grained permissions) owned by the Safe and enable it as a module. |
| safe:install-scope-guard | Deploy a Zodiac ScopeGuard owned by the Safe and set it as the transaction guard of the Safe, limiting which targets and functions owners can call. |
| safe:new | Deploy a new Safe v1.5.0 with the given owners, at a deterministic address that is the same on every chain for the same owners, threshold and salt (created like Safe{Wallet} creates Safes: switched to the L2 singleton on every chain but Ethereum mainnet). |
| safe:propose | Queue a Safe transaction, rejection or Safe message on the Safe Transaction Service: a command block, cancel or a message, signed by the wallet as an owner (its confirmation) or a delegate, or signed JSON. |
| safe:propose-offline | Create an unsigned Safe transaction, rejection or Safe message without the Safe Transaction Service and bind its JSON to a variable, for owners to sign with safe:confirm-offline. |
| safe:remove-guard | Remove the transaction guard of the Safe, or with --module its module guard (Safe v1.5.0 or later). |
| safe:remove-owner | Remove an owner from the Safe, lowering the threshold if it would exceed the remaining owners. |
| safe:set-fallback-handler | Set the fallback handler contract of the Safe. |
| safe:set-guard | Set the transaction guard of the Safe, a contract that checks every owner transaction before and after execution (e.g. a Zodiac ScopeGuard), or with --module its module guard (Safe v1.5.0 or later), which checks every module transaction. |
| safe:swap-owner | Replace an owner of the Safe with a new address. |
| safe:upgrade | Upgrade the Safe to v1.5.0 with Safe's SafeMigration contract (a delegatecall from the Safe), keeping its L2 or plain flavour and any custom fallback handler. |
Helpers
Section titled “Helpers”| Helper | Returns | Description |
|---|---|---|
| @safe:address | address | Predict the single-owner Safe address for safe:new with a deployment salt nonce, without RPC access. The address is the same on every chain. |
| @safe:delegates | array | Accounts the Safe Transaction Service lets propose transactions of a Safe on behalf of its owners, without confirming them. |
| @safe:fallbackHandler | address | Fallback handler address of a Safe, which answers the calls the Safe itself does not implement (the zero address when none is set). |
| @safe:guard | address | Transaction guard address of a Safe, or with module:true its module guard (the zero address when none is set; module guards need Safe v1.5.0 or later, so it is always zero on older Safes). |
| @safe:isOwner | bool | Whether an address is an owner of a Safe. |
| @safe:merge | string | Merge signatures into a Safe transaction or Safe message without network access: matching signed JSON, EOA signatures, or explicit contract signatures. Current authorization is checked by verify and execute. |
| @safe:modules | array | Enabled module addresses of a Safe. |
| @safe:nonce | number | Current nonce of a Safe. |
| @safe:owners | array | Owner addresses of a Safe. |
| @safe:queue | array | safeTxHashes of the trusted transactions queued on the Safe Transaction Service that can still execute (not executed, at the on-chain nonce or later), in nonce order, or with nonce: |
| @safe:signature | bytes | Packed owner signatures of a Safe transaction or Safe message once enough owners have signed, e.g. the EIP-1271 signature a dapp asks for. |
| @safe:singleton | address | Singleton (implementation) address a Safe proxy delegates every call to, read from its storage slot 0. |
| @safe:threshold | number | Signature threshold of a Safe. |
| @safe:verify | string | Verification report of a Safe transaction or Safe message as JSON: integrity-checked hashes, decoded calls, findings, owner signature checks, on-chain approvals, readiness and competing transactions, with the verdict safe:confirm and safe:execute would reach. |