DEFAULT_CONFIRMATION_BLOCK_TIME

Documentation for eth_defi.provider.receipt.DEFAULT_CONFIRMATION_BLOCK_TIME data.

DEFAULT_CONFIRMATION_BLOCK_TIME: float = 25.0

Default wall-clock confirmation time in seconds for wait_for_transaction_receipt_robust() on live (non-Anvil) chains.

Converted to a per-chain block count using eth_defi.chain.get_evm_block_time() and combined with confirmation_block_count as max(time_based_blocks, confirmation_block_count).

Why a time and not a count: a fixed block count means a wildly different real wait per chain — DEFAULT_CONFIRMATION_BLOCK_COUNT (2) is ~24 s on Ethereum mainnet but only ~0.5 s on Arbitrum. Half a second is not enough for all backend nodes behind a load-balanced RPC endpoint (lb.drpc.org and similar) to apply the new block, so an eth_call issued right after the wait could still read pre-transaction state. Observed on Arbitrum 2026-06-10: allowance() returned 0 immediately after a confirmed approve(), aborting a Lagoon vault first deposit.

25 seconds gives roughly: Ethereum mainnet 3 blocks, Base 13 blocks, Arbitrum 100 blocks.

Pass confirmation_block_time=0 to disable the time-based wait and use only confirmation_block_count. An explicit confirmation_block_count=0 (the documented pure receipt-visibility opt-out) also disables this default.