Development of Transaction Automation via Safe{Wallet}
Safe{Wallet} (formerly Gnosis Safe) is the de facto standard for multisig wallets in Web3. Any serious DeFi protocol, DAO treasury, or corporate crypto wallet uses Safe. But manually collecting signatures from 3 out of 5 owners for every routine transaction is painful. Automation through Safe solves this: a Keeper executes transactions based on conditions or schedule without compromising multisig security.
Two Automation Mechanisms
Safe Modules
A Safe Module is a smart contract that a Safe wallet explicitly delegates the right to execute transactions without collecting owner signatures. A Module is enabled through enableModule(address module) — this requires normal multisig voting. But once enabled, the Module can call execTransactionFromModule directly.
This is powerful and dangerous. A compromised Module means full access to Safe's funds without any multisig protections. That's why proper Module architecture includes:
- Explicit whitelist of allowed actions (specific contracts, specific functions, maximum amounts)
- Timelock: transaction is announced, executed after N hours
- Ability to disable Module through multisig
Zodiac Module Framework from Gnosis — a set of ready-made modules: RolesModule (role-based system with detailed permissions), DelayModule (timelock), ExitModule (allows DAO participants to exit with proportional share). For custom automation, RolesModule is the right choice: define a "Keeper" role, give it the right to call specific functions on specific contracts with specific limits.
Safe Transaction Service + Relay
Alternative approach: a backend service forms a transaction, obtains the required number of signatures from owners (asynchronously via Safe Transaction Service API), and when the threshold is reached, a relay service submits the transaction on-chain.
This approach doesn't require a Module, is safer (multisig is fully preserved), but requires human-in-the-loop for signing. Suitable for semi-automatic processes: the system determines that a transaction is needed → notifies owners → they sign → execution is automatic.
Integration with Gelato and Chainlink Automation
For fully automatic transactions on schedule — integrate Safe Module with Keeper networks:
Gelato Safe Module — a ready-made Module from Gelato that allows setting up automatic transactions from Safe based on schedule or on-chain conditions. Gelato pays gas from its balance (1Balance), Safe doesn't spend ETH on gas directly.
Chainlink Automation + custom Module: Chainlink Keeper calls a Module function that checks the condition and initiates a transaction via execTransactionFromModule. More flexible, but requires Module development.
Development of Custom Automation Module
Basic Module structure:
contract AutomationModule is Module {
ISafe public safe;
function executeScheduled(bytes calldata data) external onlyKeeper {
require(block.timestamp >= nextExecution, "Too early");
require(safe.execTransactionFromModule(
target, value, data, Enum.Operation.Call
), "Module transaction failed");
nextExecution = block.timestamp + interval;
}
}
Important details: onlyKeeper — verification that an authorized Keeper is calling, not an arbitrary address. Enum.Operation.Call vs Enum.Operation.DelegateCall — for most cases Call is needed. DelegateCall executes code in the context of Safe — extremely dangerous for automation.
Typical Automation Use Cases
Automatic rebalance of DeFi positions. Safe holds liquidity in several protocols. Once a week, Keeper checks allocation and calls the rebalancing transaction via Module.
DAO-scheduled grant payments. DAO approved a grant of 10 ETH, paid out at 1 ETH per month. Module stores grant parameters, Keeper calls monthly.
Sweep from hot wallet to Safe. Hot wallet accumulates funds, Keeper transfers to Safe when threshold is reached.
Timeline
Setting up an existing Zodiac Module (RolesModule + Gelato) for typical automation — 1-2 working days. Developing a custom Automation Module with specific business logic — 3-5 days.
Cost is calculated after discussing Safe structure (number of owners, threshold, target transactions).