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.
⚗️ Experimental — available at next.evmcrispr.com.
Syntax
Section titled “Syntax”safe:delegate-exec <contractAddress> <signature> [...params]Arguments
Section titled “Arguments”| Name | Type | Description |
|---|---|---|
contractAddress | address | Target library/contract address |
signature | write-abi | Function signature (e.g. "signMessage(bytes)") |
[...params] | any | Arguments matching the signature types |
Examples
Section titled “Examples”Sign a message on behalf of the Safe by delegatecalling SignMessageLib:
load safe
set $mySafe 0x5afe3855358e112b5647b952709e6165e1c1eeeesafe:propose $mySafe ( safe:delegate-exec 0xd53cd0aB83D845Ac265BE939c57F53AD838012c9 signMessage(bytes) @bytes("hello"))A delegatecall runs arbitrary code in the storage context of the Safe — it can overwrite owners, modules, or the singleton pointer. Only use audited libraries you trust. Proposals containing a delegatecall are flagged in the Safe web UI, and the hosted Transaction Service only accepts them for whitelisted targets (such as SignMessageLib or MultiSend).