Add minimum base fee documentation to network fees page #704
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| --- | ||
| title: Configuration Changelog | ||
| slug: /configuration-changelog | ||
| description: A log of configuration changes to the Base networks. | ||
| --- | ||
|
|
||
| This page tracks configuration changes to the Base networks, including updates to block building, network fees, and other network parameters. | ||
|
|
||
| ## Base Mainnet | ||
|
|
||
| | Date | Change | Documentation | | ||
| |------|--------|---------------| | ||
| | December 4, 2025 | Enabled Minimum Base Fee (200,000 wei) | [Minimum Base Fee](/base-chain/network-information/network-fees#minimum-base-fee) | | ||
| | September 17, 2025 | Enabled Per-Transaction Gas Maximum | [Per-Transaction Gas Maximum](/base-chain/network-information/block-building#per-transaction-gas-maximum) | | ||
| | September 11, 2025 | Ended testing Per-Transaction Gas Maximum | [Per-Transaction Gas Maximum](/base-chain/network-information/block-building#per-transaction-gas-maximum) | | ||
| | September 10, 2025 | Started testing Per-Transaction Gas Maximum | [Per-Transaction Gas Maximum](/base-chain/network-information/block-building#per-transaction-gas-maximum) | | ||
| | July 7, 2025 | Enabled Flashblocks | [Flashblocks](/base-chain/network-information/block-building#flashblocks) | | ||
| | May 15, 2025 | Ended testing Flashblocks | [Flashblocks](/base-chain/network-information/block-building#flashblocks) | | ||
| | May 15, 2025 | Started testing Flashblocks | [Flashblocks](/base-chain/network-information/block-building#flashblocks) | | ||
|
|
||
| ## Base Sepolia | ||
|
|
||
| | Date | Change | Documentation | | ||
| |------|--------|---------------| | ||
| | November 20, 2025 | Enabled Minimum Base Fee (200,000 wei) | [Minimum Base Fee](/base-chain/network-information/network-fees#minimum-base-fee) | | ||
| | September 3, 2025 | Enabled Per-Transaction Gas Maximum | [Per-Transaction Gas Maximum](/base-chain/network-information/block-building#per-transaction-gas-maximum) | | ||
| | February 25, 2025 | Enabled Flashblocks | [Flashblocks](/base-chain/network-information/block-building#flashblocks) | |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,110 @@ | ||
| --- | ||
| title: Troubleshooting Transactions | ||
| slug: /troubleshooting-transactions | ||
| description: Guide to diagnosing and resolving transaction issues on Base. | ||
| --- | ||
|
|
||
| ## Transaction Not Being Included | ||
|
|
||
| If your transaction is pending for longer than expected, check the following: | ||
|
|
||
| ### Max Fee Too Low | ||
|
|
||
| If your `maxFeePerGas` is lower than the current base fee, your transaction will remain pending until the base fee drops to your specified level. | ||
|
|
||
| **Solution**: The `maxFeePerGas` must cover both the base fee and your priority fee. Since the base fee can change with each block, set `maxFeePerGas` high enough to remain valid even if the base fee rises while your transaction is pending. A common approach is: | ||
|
|
||
| ``` | ||
| maxFeePerGas = baseFee * 2 + maxPriorityFeePerGas | ||
| ``` | ||
|
|
||
| This formula (used by [ethers.js](https://github.com/ethers-io/ethers.js/blob/98c49d091eb84a9146dfba8476f18e4c3e3d1d31/src.ts/providers/abstract-provider.ts#L945-L950)) provides headroom for the base fee to double before your transaction becomes unexecutable. You only pay the actual base fee at inclusion time, not the maximum. | ||
|
|
||
| <Note> | ||
| Base has a [minimum base fee](/base-chain/network-information/network-fees#minimum-base-fee). Transactions with `maxFeePerGas` below this value will never be included, since the base fee cannot drop below the minimum. | ||
| </Note> | ||
|
Comment on lines
+23
to
+25
There was a problem hiding this comment. These sections seem misformatted in the GH diff preview. Will these render correctly in the actual docs site? There was a problem hiding this comment. Edit: confirmed that this looks good on the staging docs site |
||
|
|
||
| ### Priority Fee Too Low | ||
|
|
||
| During periods of high demand, transactions compete for block space through priority fees. If your priority fee is too low relative to other transactions, yours may be delayed. | ||
|
|
||
| **Solution**: Most users simply wait for congestion to subside. For time-sensitive transactions, use `eth_maxPriorityFeePerGas` to get a priority fee estimate that can outbid enough recent transactions to be included. | ||
|
|
||
| <Note> | ||
| If [DA throttling](https://docs.optimism.io/chain-operators/guides/configuration/batcher#batcher-sequencer-throttling) is currently in effect, there's no RPC endpoint that calculates priority fee estimates with throttling in mind. During DA throttling, even transactions with high priority fees may be delayed as the sequencer limits L2 transactions to manage its L1 data availability throughput. | ||
| </Note> | ||
|
|
||
| ### Nonce Gap | ||
|
|
||
| If you have a pending transaction with nonce N, all transactions with nonce N+1 or higher will queue behind it, regardless of their fees. | ||
|
|
||
| **Solution**: Either wait for the pending transaction to be included, or replace it by submitting a new transaction with the same nonce and a higher fee (at least 10% higher `maxPriorityFeePerGas` and `maxFeePerGas`). | ||
|
|
||
| ### Nonce Too Low | ||
|
|
||
| If you submit a transaction with a nonce that has already been used, it will be rejected. | ||
|
|
||
| **Solution**: Query your current nonce using `eth_getTransactionCount` with the `pending` tag to get the next available nonce. | ||
|
|
||
| ## Transaction Rejected | ||
|
|
||
| ### Gas Limit Exceeds Maximum | ||
|
|
||
| Ethereum enforces a [transaction gas limit cap](https://eips.ethereum.org/EIPS/eip-7825) of **16,777,216 gas**. Base plans to match this limit in a future upgrade, but currently enforces a [per-transaction gas maximum](/base-chain/network-information/block-building#per-transaction-gas-maximum) of **25,000,000 gas**. Transactions specifying a higher gas limit are rejected by the mempool before inclusion. | ||
|
|
||
| **Error**: `exceeds maximum per-transaction gas limit` | ||
|
|
||
| **Solution**: Reduce the gas limit to 16,777,216 or below. If your transaction genuinely requires more gas, you'll need to break it into multiple transactions. | ||
|
|
||
| ## Transaction Included But Failed | ||
|
|
||
| If your transaction was included in a block but shows a failed status: | ||
|
|
||
| ### Out of Gas | ||
|
|
||
| The transaction ran out of gas during execution. | ||
|
|
||
| **Solution**: Increase the gas limit. Use `eth_estimateGas` to get a gas estimate, then add a buffer (e.g., 20%) to account for variability. | ||
|
|
||
| ### Reverted by Contract | ||
|
|
||
| The contract execution encountered a revert condition. | ||
|
|
||
| **Solution**: Check the transaction on [Basescan](https://basescan.org) to see the revert reason. Common causes include failed require statements, arithmetic errors, or invalid state transitions. | ||
|
There was a problem hiding this comment. Should we explicitly identify Basescan or use the more generic explorer.base.org, which can be rerouted in the case of a service disruption.
Contributor
Author
There was a problem hiding this comment. The docs mention Basescan all over the place, so I don't think that's an avoidable problem. Changing how we refer to the block explorer makes sense, but I think we'll be better off if it's a consistent change that we make everywhere. |
||
|
|
||
| ## Slow Confirmation | ||
|
|
||
| ### Understanding Confirmation Times | ||
|
|
||
| Base produces blocks every 2 seconds, but [Flashblocks](/base-chain/flashblocks/apps) provide preconfirmations every 200ms. | ||
|
|
||
| | Confirmation Level | Time | Description | | ||
| |-------------------|------|-------------| | ||
| | Flashblock preconfirmation | ~200ms | Transaction included in a preconfirmation | | ||
|
There was a problem hiding this comment. This shows the cadence of each periodic event. Should we show average confirmation time instead, which would be ~100ms for flashblocks, and ~1s for L2 blocks?
Contributor
Author
There was a problem hiding this comment. This part is cribbed from the Transaction Finality page. I think using average times would be confusing. Most people need the upper bounds, and the people who need the average times will be able to figure it out. |
||
| | L2 block inclusion | ~2s | Transaction included in a sealed L2 block | | ||
| | L1 batch inclusion | ~2m | Transaction posted to Ethereum | | ||
| | L1 finality | ~20m | Ethereum batch is finalized | | ||
|
|
||
| See [Transaction Finality](/base-chain/network-information/transaction-finality) for more details. | ||
|
|
||
| ### Using Flashblocks for Faster Confirmations | ||
|
|
||
| To get the fastest possible confirmation, use a Flashblocks-aware RPC endpoint: | ||
|
|
||
| | Network | Flashblocks RPC | | ||
| |---------|-----------------| | ||
| | Mainnet | `https://mainnet-preconf.base.org` | | ||
| | Sepolia | `https://sepolia-preconf.base.org` | | ||
|
|
||
| These endpoints return transaction receipts as soon as a transaction is included in a Flashblock, rather than waiting for the full L2 block. | ||
|
|
||
| ## Debugging Tools | ||
|
|
||
| - **[Basescan](https://basescan.org)**: View transaction status, logs, and revert reasons | ||
|
There was a problem hiding this comment. Same as above, although here we can maybe enumerate different explorers |
||
| - **[Tenderly](https://tenderly.co)**: Simulate and debug transactions | ||
| - **`eth_call`**: Test contract calls without submitting a transaction | ||
| - **`eth_estimateGas`**: Estimate gas usage before submitting | ||
|
|
||
| ## Getting Help | ||
|
|
||
| If you're still experiencing issues, reach out in the `#developer-chat` channel in the [Base Discord](https://base.org/discord). | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can probably base this on minimum doubling speed and a reasonable delay (including time to sign the tx), but this is subject to change alongside any modifications to EIP1559 parameters, including increasing elasticity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's technically the right way to think about it, but it feels like maybe too much information for the average reader. ethers.js multiplies by 2 and viem multiplies by 1.2. I don't think anyone is doing anything more sophisticated than that.