dBank Gas Credits

dBank is the workspace's prepaid USD credit balance used for sponsored mainnet gas. It is shared across projects. Task compute and RPC-related usage are separate from gas; see usage and metering.

When credits are used

Sponsored testnet gas does not debit dBank. Sponsored mainnet execution requires sufficient credit and enabled sponsorship support. A wallet-paid legacy run pays from its native balance; if configured fallback switches it to sponsored mode, the sponsorship funding rules apply.

The managed Lift integration is designed to reserve and settle paid sponsorship against the same workspace balance; the current Roles/Lift deployment path is Sepolia-only and uses testnet sponsorship. The linked Flow execution does not debit the operation a second time. Receipt costs and reconciliation can appear after the initial execution response.

Add credit

Open the workspace's billing page, use the dBank top-up action, and complete the payment flow shown for that deployment. Verify the resulting balance and ledger entry before enabling work that depends on it. Do not infer live mainnet availability from the presence of a top-up button.

Funding and failure behavior

Gas checks can refuse a run before broadcast when the estimate, pricing, or available credit cannot be established. Inspect the actual execution outcome: some pre-submit gas errors are recorded as failures, and repeated enforcement failures can pause the executable.

A transaction that reverts on-chain can still consume gas. A timed-out receipt may still resolve later. Review transaction hashes and final settlement rather than assuming that every non-successful execution is free.

A funded balance does not bypass profile permissions or workspace limits. After correcting a funding issue, inspect whether the executable was automatically paused and resume it if appropriate. Missed invocations are not an automatic replay queue.

See gas modes and Flow with Lift.