Gas Modes and Sponsorship
Gas pays for on-chain submission; running task code and reading the chain are separate usage categories. Configure gas on the executable through the console or management API.
| Profile | Sponsored | Wallet-paid |
|---|---|---|
Roles (safe_roles) | Required; managed Lift. | Unavailable. |
Legacy (legacy) | Supported when configured for the chain. | self or self-funded, depending on routing. |
Non-custodial profiles force sponsored mode and disable gas fallback when selected.
Sponsored execution
Roles profiles use a managed Lift integration and policy. You do not need to create a public Lift API key for Flow. Profile authorization decides which calls are allowed; sponsorship pays for those authorized calls. See Flow with Lift.
Sponsored testnet executions do not debit dBank. On mainnet, sponsorship requires sufficient workspace dBank credit and configured chain support. The managed Lift integration has its own reservation/settlement path against the same workspace balance, avoiding a second Flow debit. The current Roles/Lift route is Sepolia-only; its presence does not enable mainnet Roles profiles.
For other supported sponsorship paths, Flow estimates cost before submission and records the actual receipt cost afterwards. A receipt failure can still consume gas. Sponsorship is not a guarantee that a task will execute successfully.
Wallet-paid legacy execution
self means the profile wallet pays. Where a configured bundler is available, Flow can route it as a self-funded ERC-4337 operation (self-funded); otherwise the legacy route sends a direct EIP-7702 transaction. Fund the profile's native balance on the correct chain.
The console groups these under Self-paid (profile wallet). API results may report the effective self-funded mode. Even on a testnet, wallet-paid gas consumes native test tokens.
Fallback
For a wallet-paid legacy executable, enabling fallback permits one sponsored retry after an insufficient-balance error. It does not retry every contract revert. Mainnet fallback must pass the dBank gate; testnet fallback uses configured testnet sponsorship. A Roles or Smart Sessions profile never needs this toggle because it always uses sponsorship.
Operational checks
Before activating automation, verify the profile is active, the chain and sponsorship route are enabled, the release's required permissions are covered, and any required gas balance or dBank credit is available. Check the recorded payer and transaction hash when investigating a failed or delayed execution.