Agent payment safety checks for Base

What your agent needs to know about Base

Finality

Base docs describe three stages. The sequencer includes a transaction in an L2 block in about 200ms and reorgs are nearly unheard of (docs say less than 0.00000002% of mainnet transactions reorged). A batch containing it reaches Ethereum in about 2 minutes. That batch is protected like an Ethereum finalized block after about 20 minutes (2 epochs, 64 L1 blocks). Decide per amount: an agent may accept 200ms inclusion for small payments as a risk it chooses, and should wait for the 20 minute point on large amounts. Only withdrawals to Ethereum have a waiting period: 5 days for a single-proof dispute game, or 1 day when a TEE proof and a ZK proof back the same proposal. Third-party bridges can pay out sooner from their own liquidity. Flashblocks were retired on Base Mainnet on 5 Nov 2026, so there are no preconfirmed receipts; wait for a receipt in a canonical block.^[1],[5]

Fees

A Base fee has an L2 execution part (gas used times base fee plus priority fee) and an L1 data fee, plus any operator fee. Docs say the L1 fee is typically higher than the L2 fee, and it follows Ethereum base fee and blob base fee. The OP Stack docs say you cannot currently set a maximum for the L1 data fee. The L2 base fee has a minimum of 0.005 gwei (Jovian upgrade). At that minimum, docs say a 200,000 gas transaction costs about $0.002 in L2 execution fee at a $2,000 ETH price, excluding priority fee and L1 fee. A transaction that is included but reverts still pays fees. The gas token is ETH.^[2],[6]

Stablecoins

Circle lists native USDC on Base at the address below. Circle describes bridged USDC as created by third parties, not issued by Circle, not redeemable the way native USDC is, and not compatible with CCTP. Third-party sources name the bridged token on Base USDbC; Circle's pages do not use that name, so check the contract address, not the symbol. USDC contracts have an issuer blacklist: the Circle stablecoin-evm Blacklistable contract has blacklist, unBlacklist and isBlacklisted functions controlled by a blacklister role, so a frozen address cannot move its USDC. No official Tether USDT address for Base was found on Tether's supported-protocols page, so none is given.^[3],[4],[7]

How agent payments go wrong on Base

1. 1. Bridged USDC paid instead of native

   A token that looks like USDC (same name, similar symbol such as USDbC) can be a bridged version that Circle does not issue or redeem. An agent that matches on symbol can accept or pay the wrong token. Compare the contract address with Circle's list before accepting or sending.^[3],[4]

2. 2. Treating 200ms inclusion as settled for large sums

   Inclusion in an L2 block is not the same as the batch being final on Ethereum, which docs put at about 20 minutes. Reorgs are very rare, but a large payment should wait for the batch finality point or use the finalized block tag. Set a value threshold in the agent.^[1]

3. 3. L1 data fee surprise

   The L1 data fee moves with Ethereum gas and blob prices and cannot be capped on the OP Stack. A fee budget based only on L2 gas can be off. Estimate the total fee (L2 plus L1) right before signing and refuse if it exceeds the budget.^[2],[6]

4. 4. Sequencer outage

   OP Stack docs say that if the sequencer is down, a user can send a transaction through the OptimismPortal on L1 and it is included within the sequencer window, 12 hours by default but chain specific. An agent should not assume payments land during an outage and should time out and alert rather than resend blindly.^[8]

5. 5. Waiting on a pending or preconfirmed state that no longer exists

   Base ended Flashblocks on Mainnet on 5 Nov 2026. The pending tag now resolves to the latest canonical block and there are no preconfirmed receipts. Agents built on flashblock subscriptions or pending reads must poll eth_getTransactionReceipt instead.^[5]

6. 6. Frozen USDC address

   Circle's USDC contract can blacklist an address, which blocks transfers involving it. A payee address that is frozen will make the transfer revert. Call isBlacklisted on the USDC contract for the payee before sending.^[7]

Pre-flight checklist for a Base agent

• Match the token by contract address against Circle's native USDC list, never by symbol alone.
• Estimate total fee (L2 plus L1 data fee) just before signing and compare it with the budget.
• Wait for a receipt in a canonical block, and for large amounts wait for the batch to be final (about 20 minutes per Base docs).
• Call isBlacklisted on the USDC contract for the payee address before sending.
• Set a timeout and alert path in case the sequencer is down; do not resend the same payment without checking the nonce.
• Use the finalized block tag when reading balances that gate a release of goods.

Explorers to confirm a payment

• Basescan

Sources

1. [1] Base transaction finality, Base docs
2. [2] Base network fees, Base docs
3. [3] USDC contract addresses, Circle
4. [4] Bridged USDC Standard, Circle
5. [5] Flashblocks for apps (retirement notice), Base docs
6. [6] OP Stack transaction fees, Optimism docs
7. [7] Blacklistable.sol, Circle (GitHub)
8. [8] OP Stack rollup outages, Optimism docs

Checked against these sources on 9 November 2026. Networks change: confirm against the live docs before you rely on a number. This page is a checklist from public documentation. It is not a security audit, legal, compliance or investment advice.