Choose a Gas Strategy
Choose the account authorization model first; it determines which gas modes are available.
| Need | Configuration |
|---|---|
| Scoped customer-owned Safe automation | Roles profile with managed Lift sponsorship. |
| Existing legacy wallet should pay | Wallet-paid self/self-funded route with native funds. |
| Legacy wallet should try sponsorship when underfunded | Enable gas fallback, with sufficient mainnet dBank credit when applicable. |
New Roles automation
Complete the owner-approved target/selector scope and verify the profile. Flow manages the associated Lift integration and per-profile policy; a separate public Lift key is unnecessary. Start on an enabled testnet and confirm one intended call before scheduling recurring work.
The current Roles contract stack is Sepolia-only. Funding and routing support for a different chain do not make that profile type available there.
Existing wallet-paid automation
Fund the legacy profile's native balance on its chain. The effective route may be a direct EIP-7702 transaction or a self-funded ERC-4337 operation. Either spends the profile wallet's funds, including test tokens on testnets.
Fallback applies to insufficient-balance errors and retries once through sponsorship. It does not fix a contract permission error or make a reverted call valid.
Mainnet planning
Where the deployment and plan enable mainnet, keep dBank funded for sponsored operations and monitor actual receipt costs. A revert can consume gas, and a delayed receipt may settle later. Scope approvals and gas approval are separate checks.
Inspect execution payer and hashes when troubleshooting. Use gas modes, dBank, and Flow with Lift for the details.