diff --git a/docs/AGENTS.md b/docs/AGENTS.md
index 1aa41788d..a696801d9 100644
--- a/docs/AGENTS.md
+++ b/docs/AGENTS.md
@@ -11,7 +11,7 @@ description: Look up Base documentation with a compact directory-grouped index b
- [Agents](./agents/llms.txt) — Give your AI assistant a wallet. Base MCP connects any AI to your Base Account. Check balances, send funds, swap tokens, sign messages, and pay with x402.
- [Apps](./apps/llms.txt) — A step-by-step guide to building a Next.js tally app on Base using wagmi and viem, with wallet connection, contract reads and writes, and batch transaction support.
- [Base Account](./base-account/llms.txt)
-- [Base Chain](./base-chain/llms.txt) — Bridge tokens and messages between Base and Solana Mainnet
+- [Base Chain](./base-chain/llms.txt) — Start here for Base Chain docs, including concepts, network reference, node operation, APIs, and protocol specifications.
- [Get Started](./get-started/llms.txt)
- [Ledgers](./ledgers/llms.txt) — An introduction to Base Ledgers, the enterprise way to run confidential payments that settle on Base.
- [Static](./static/llms.txt)
@@ -50,7 +50,7 @@ npx skills add base/base-skills
|apps/builder-codes:agent-developers,app-developers,builder-codes,wallet-developers
|apps/growth:rewards
|apps/guides:accept-b20-payments,migrate-to-standard-web-app
-|apps/quickstart:build-app
+|apps/quickstart:build-app,deploy-on-base
|apps/resources:design-resources,templates
|apps/technical-guides:base-notifications
|base-account/basenames:basename-transfer,basenames-faq
@@ -74,14 +74,15 @@ npx skills add base/base-skills
|base-account/reference/prolink-utilities:createProlinkUrl,decodeProlink,encodeProlink
|base-account/reference/spend-permission-utilities:fetchPermission,fetchPermissions,getPermissionStatus,prepareRevokeCallData,prepareSpendCallData,requestRevoke,requestSpendPermission
|base-account/reference/ui-elements:base-pay-button,brand-guidelines,sign-in-with-base-button
+|base-chain:overview
|base-chain/api-reference:rpc-overview
|base-chain/api-reference/debug-api:debug_traceBlockByHash,debug_traceBlockByNumber,debug_traceTransaction
|base-chain/api-reference/ethereum-json-rpc-api:eth_blockNumber,eth_call,eth_chainId,eth_estimateGas,eth_feeHistory,eth_gasPrice,eth_getBalance,eth_getBlockByHash,eth_getBlockByNumber,eth_getBlockReceipts,eth_getBlockTransactionCountByHash,eth_getBlockTransactionCountByNumber,eth_getCode,eth_getLogs,eth_getStorageAt,eth_getTransactionByBlockHashAndIndex,eth_getTransactionByBlockNumberAndIndex,eth_getTransactionByHash,eth_getTransactionCount,eth_getTransactionReceipt,eth_maxPriorityFeePerGas,eth_sendRawTransaction,eth_subscribe,eth_syncing,eth_unsubscribe,net_version,web3_clientVersion
|base-chain/api-reference/flashblocks-api:base_transactionStatus,eth_simulateV1,flashblocks-api-overview,newFlashblockTransactions,newFlashblocks,pendingLogs
-|base-chain/flashblocks:app-integration,architecture,faq,overview
-|base-chain/network-information:base-contracts,block-building,bridges,configuration-changelog,diffs-ethereum-base,network-faucets,network-fees,transaction-finality,troubleshooting-transactions
+|base-chain/flashblocks:faq
+|base-chain/network-information:base-contracts,base-solana-bridge,bridging-and-withdrawals,ecosystem-bridges,network-faucets,network-fees,throughput-and-limits,transaction-finality,transaction-ordering,troubleshooting-transactions
|base-chain/node-operators:node-providers,performance-tuning,run-a-base-node,snapshots,troubleshooting
-|base-chain/quickstart:base-solana-bridge,connecting-to-base,deploy-on-base,why-base
+|base-chain/quickstart:connecting-to-base
|base-chain/security:avoid-malicious-flags,bug-bounty,report-vulnerability,security-council
|base-chain/specs:overview
|base-chain/specs/protocol:batcher,overview
diff --git a/docs/apps/quickstart/build-app.mdx b/docs/apps/quickstart/build-app.mdx
index b2253affa..2c2070b96 100644
--- a/docs/apps/quickstart/build-app.mdx
+++ b/docs/apps/quickstart/build-app.mdx
@@ -537,6 +537,29 @@ Base is a fast, low-cost Ethereum L2 built to bring the next billion users oncha
+## Speed up confirmations with Flashblocks
+
+Base builds [Flashblocks](/base-chain/network-information/transaction-ordering#flashblocks) — 200ms incremental blocks that let your app reflect transaction confirmations roughly 10x faster than the standard 2-second block time. Flashblocks are always live; you opt in by pointing Wagmi at a Flashblocks-aware chain, with no other code changes. `useWaitForTransactionReceipt` then resolves against pre-confirmed state.
+
+Swap the standard chain for its `Preconf` variant in `config/wagmi.ts`:
+
+```typescript config/wagmi.ts highlight={2,5,8}
+import { http, createConfig } from 'wagmi'
+import { baseSepoliaPreconf } from 'wagmi/chains'
+
+export const config = createConfig({
+ chains: [baseSepoliaPreconf],
+ // ...connectors and storage unchanged
+ transports: {
+ [baseSepoliaPreconf.id]: http(),
+ },
+})
+```
+
+
+For production, the public endpoints are rate-limited — connect through a Flashblocks-enabled [node provider](/base-chain/node-operators/node-providers). For the underlying RPC behavior (the `pending` block tag and supported methods), see the [RPC Overview](/base-chain/api-reference/rpc-overview#flashblocks) and the [Flashblocks Reference](/base-chain/flashblocks/faq).
+
+
## Next steps
- **Go to mainnet** — add `base` to your `chains` array and transports in `config/wagmi.ts`, redeploy your contract to Base mainnet, and update `COUNTER_ADDRESS`.
diff --git a/docs/base-chain/quickstart/deploy-on-base.mdx b/docs/apps/quickstart/deploy-on-base.mdx
similarity index 98%
rename from docs/base-chain/quickstart/deploy-on-base.mdx
rename to docs/apps/quickstart/deploy-on-base.mdx
index f6e32f145..f12854d37 100644
--- a/docs/base-chain/quickstart/deploy-on-base.mdx
+++ b/docs/apps/quickstart/deploy-on-base.mdx
@@ -1,5 +1,6 @@
---
title: 'Deploy on Base'
+description: Deploy a smart contract to Base Sepolia with Foundry.
---
Welcome to the Base deployment quickstart guide! This comprehensive walkthrough will help you set up your environment and deploy smart contracts on Base. Whether you're a seasoned developer or just starting out, this guide has got you covered.
@@ -122,7 +123,7 @@ Note the format of the contract being deployed is `:
-**`eth_call "pending"` block context on Flashblocks nodes:** Block-context properties (`block.number`, `block.timestamp`, `block.basefee`) may reflect a block several behind tip due to how nodes cache historical Flashblocks. See the [FAQ](/base-chain/flashblocks/faq#why-does-eth_call-pending-report-a-block-context-several-blocks-behind-tip) for details.
+**`eth_call "pending"` block context on Flashblocks nodes:** Block-context properties (`block.number`, `block.timestamp`, `block.basefee`) may reflect a block several behind tip due to how nodes cache historical Flashblocks. See the [FAQ](/base-chain/flashblocks/faq#why-does-eth_call-pending-report-a-block-number-several-blocks-behind-tip) for details.
## Parameters
diff --git a/docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx b/docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx
index 40648d001..9382125ea 100644
--- a/docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx
+++ b/docs/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.mdx
@@ -50,7 +50,7 @@ Unique identifier for the block being built. Remains consistent across all Flash
-Flashblock index within the current block. Starts at 0 (system transactions only). User transactions begin at index 1. Typically reaches 9–10 per block, but [may exceed 10](/base-chain/flashblocks/faq#why-can-the-flashblock-index-exceed-10) during sequencer timing drift.
+Flashblock index within the current block. Starts at 0 (system transactions only). User transactions begin at index 1. Typically reaches 9–10 per block, but [may exceed 10](/base-chain/flashblocks/faq#can-the-flashblock-index-exceed-10-is-that-a-bug) during sequencer timing drift.
diff --git a/docs/base-chain/flashblocks/app-integration.mdx b/docs/base-chain/flashblocks/app-integration.mdx
deleted file mode 100644
index d7b417fe8..000000000
--- a/docs/base-chain/flashblocks/app-integration.mdx
+++ /dev/null
@@ -1,203 +0,0 @@
----
-title: App Integration
-sidebarTitle: App Integration
-description: Integrate Flashblocks into your app for 200ms transaction confirmations using RPC APIs and popular libraries like Ethers, Wagmi and Viem.
----
-
-Choose the integration method that fits your use case:
-
-| Use Case | Recommended Approach | Documentation |
-|----------|---------------------|---------------|
-| **Apps needing instant UX** | Flashblocks-aware RPC with `pending` tag | [API Reference](/base-chain/api-reference/flashblocks-api/flashblocks-api-overview) |
-| **Infrastructure providers** | Host Flashblocks-aware RPC nodes | [Enable Flashblocks](/base-chain/node-operators/run-a-base-node#enable-flashblocks) |
-| **Standard apps** | Continue using regular RPCs | [JSON-RPC API Reference](/base-chain/api-reference/rpc-overview) |
-
-
-Applications should avoid hard dependencies on the WebSocket stream. RPCs provide stable behavior and automatic failover to regular blocks if Flashblocks go down.
-
-
-## RPC Endpoints
-
-For HTTP and WebSocket endpoint URLs, see the [Flashblocks API Reference](/base-chain/api-reference/flashblocks-api/flashblocks-api-overview). Public endpoints are rate-limited. For production use, connect through a Flashblocks-enabled node provider such as Alchemy, QuickNode, or dRPC.
-
-## Performance Characteristics
-
-| Metric | Value |
-|--------|-------|
-| Flashblock build time (P50) | ~10ms |
-| Preconfirmation latency | ~200ms |
-| Full block time | 2 seconds |
-| Flashblocks per block | 10 |
-| Reorg rate | < 0.1% |
-
-## Gas & Transaction Sizing
-
-The gas budget is **cumulative**, not per-Flashblock. Each Flashblock unlocks an additional 1/10 of the total block gas:
-
-| Flashblock | Cumulative Gas Available |
-|------------|--------------------------|
-| 1 | 1/10 of block limit (~18.75M gas) |
-| 2 | 2/10 of block limit (~37.5M gas) |
-| 3 | 3/10 of block limit (~56.25M gas) |
-| ... | ... |
-| 10 | Full block limit (~187.5M gas) |
-
-
-**Unused gas carries forward.** If Flashblock 1 only uses 0.3/10 of gas, Flashblock 2 can use up to 1.7/10 (the cumulative 2/10 limit minus what's already been used).
-
-
-**Implications for large transactions:**
-- Transactions exceeding 1/10 of block gas (~18.75M) may not land in the first Flashblock — they wait until enough cumulative capacity exists.
-- There is a separate **max gas limit per transaction** on Base, distinct from Flashblock capacity.
-- If confirmation speed matters, keep individual transactions under ~18.75M gas to maximize the chance of inclusion in the earliest Flashblock.
-
-## Reliability & Fallback
-
-Base targets a **< 0.1% Flashblock reorg rate** — meaning a preconfirmation was streamed but not included in the final block. This is rare, but apps should account for it.
-
-
-**Implement fallback logic.** Treat preconfirmations as strong signals, not guarantees. For critical operations, confirm against finalized block data. Check live reorg metrics at [base.org/stats](https://base.org/stats).
-
-
-If Flashblocks become unavailable, the sequencer continues operating normally and confirmation falls back to standard 2-second blocks. Build your app to handle both cases gracefully.
-
-## Library Examples
-
-You will need to use a Flashblocks-aware RPC endpoint to use Flashblocks with the following libraries:
-
-### [Wagmi](https://wagmi.sh)
-
-To use Flashblocks with Wagmi, you will need to use the `basePreconf` chain in the Wagmi Config (see `config.ts`).
-
-
-
-```tsx Example.tsx
-import { useSendTransaction, useWaitForTransactionReceipt } from "wagmi";
-
-function SendTransaction() {
- const { data: hash, sendTransaction } = useSendTransaction();
- const { data: receipt } = useWaitForTransactionReceipt({ hash });
-
- return (
-
-
- {hash &&
Hash: {hash}
}
- {receipt &&
Included on block number: {receipt.blockNumber}
}
-
- )
-}
-```
-
-```tsx App.tsx
-import { QueryClient, QueryClientProvider } from '@tanstack/react-query'
-import { WagmiProvider, useAccount } from 'wagmi'
-import { config } from './config'
-import { Example } from './Example'
-
-const queryClient = new QueryClient()
-
-function App() {
- return (
-
-
-
-
-
- )
-}
-```
-
-```tsx config.ts
-import { createConfig, http } from "wagmi";
-import { baseSepoliaPreconf } from "wagmi/chains";
-import { baseAccount } from "wagmi/connectors";
-
-export const config = createConfig({
- chains: [baseSepoliaPreconf],
- connectors: [baseAccount()],
- transports: {
- [baseSepoliaPreconf.id]: http(),
- },
-});
-```
-
-
-
-### [Viem](https://viem.sh)
-
-```ts
-import { createWalletClient, http, parseEther, publicActions } from "viem";
-import { privateKeyToAccount } from "viem/accounts";
-import { baseSepoliaPreconf } from "viem/chains";
-
-// Create client with the Flashblocks-aware chain.
-const account = privateKeyToAccount(`0x${process.env.PRIVATE_KEY}`);
-const client = createWalletClient({
- account,
- chain: baseSepoliaPreconf,
- transport: http(),
-})
- .extend(publicActions);
-
-const submissionTime = new Date();
-console.log(`Submitting transaction at: ${submissionTime.toISOString()}`);
-
-// Send transaction.
-const hash = await client.sendTransaction({
- to: "0x...",
- value: parseEther('0.0001'),
-});
-console.log(`Transaction hash: ${hash}`);
-
-// Wait for transaction to be included.
-const receipt = await client.waitForTransactionReceipt({ hash });
-const confirmTime = new Date();
-
-console.log(`Transaction included at: ${confirmTime.toISOString()}`);
-console.log(`Time difference: ${confirmTime - submissionTime}ms`);
-```
-
-### [Ethers](https://github.com/ethers-io/ethers.js)
-
-```jsx
- const providerA = new ethers.JsonRpcProvider(
- "https://sepolia.base.org"
- );
-
- const wallet = new ethers.Wallet(process.env.PRIVATE_KEY, providerA);
-
- try {
- // Create a simple transaction (sending 0.001 ETH to a random address)
- const tx = {
- to: "",
- value: ethers.parseEther("0.0000001"),
- };
-
- // Submit transaction
- const submissionTime = new Date();
- const transaction = await wallet.sendTransaction(tx);
-
- console.log(`Submitting transaction at: ${submissionTime.toISOString()}`);
- console.log(`Transaction hash: ${transaction.hash}`);
-
- await transaction.wait(0); // Make sure to set the confirmation count to 0
-
- console.log("Transaction confirmed");
- const confirmationTime = new Date();
- console.log(`Transaction confirmed at: ${confirmationTime.toISOString()}`);
- console.log(`Time difference: ${confirmationTime - submissionTime}ms`);
- }
-```
-
-You should see the confirmation time significantly lower than the standard RPC endpoint.
-
-## Support
-
-For feedback, support or questions about Flashblocks, please don't hesitate to contact us in the `#developer-chat` channel in the [Base Discord](https://base.org/discord).
diff --git a/docs/base-chain/flashblocks/architecture.mdx b/docs/base-chain/flashblocks/architecture.mdx
deleted file mode 100644
index f1b24eda5..000000000
--- a/docs/base-chain/flashblocks/architecture.mdx
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Flashblocks Architecture
-sidebarTitle: Architecture
-description: Understand the sequencer architecture and infrastructure components that power Flashblocks on Base.
----
-
-## Before Flashblocks
-
-Base operates a high-availability sequencer system with five sequencer instances:
-
-| Component | Role |
-|-----------|------|
-| **base-consensus** | Consensus layer (CL) — replaced op-node after Azul |
-| **base-reth-node** | Execution layer (EL) — replaced op-geth after Azul |
-| **op-conductor** | High availability controller with Raft consensus for leader election |
-
-One sequencer instance acts as the **leader**, responsible for building blocks and propagating them via P2P. The remaining four act as **followers** that sync the chain. Leadership transfers if the current leader stops producing blocks.
-
-## With Flashblocks
-
-Flashblocks introduce several new infrastructure components:
-
-| Component | Purpose | What It Unlocks |
-|-----------|---------|-----------------|
-| **rollup-boost** | CL↔EL Engine API proxy | Enables sharing Flashblocks with the EL without modifying the CL. Provides a stable seam for future block-building evolutions (multi-builder, etc.) |
-| **base-builder** | Out-of-protocol builder at 200ms cadence | Produces the sub-second Flashblocks, decoupled from the EL. Enables pluggable builder mechanisms |
-| **websocket-proxy** | Flashblocks stream fan-out | Broadcast layer so many consumers can read the stream without overwhelming the builder |
-| **[base](https://github.com/base/base)** | RPC surface exposing preconfirmations | Converts streamed Flashblocks into familiar RPCs so apps and wallets can consume preconfirmation state |
-
-[rollup-boost](https://github.com/flashbots/rollup-boost) is built and maintained by Flashbots, while Base maintains [base-builder](https://github.com/base/base/tree/main/crates/builder), the websocket-proxy, and the [base](https://github.com/base/base) components.
-
----
-
-## Further Reading
-
-- [Flashblocks Overview](/base-chain/flashblocks/overview) — Key concepts and transaction lifecycle
-- [Enable Flashblocks](/base-chain/node-operators/run-a-base-node#enable-flashblocks) — Run your own Flashblocks-aware RPC node
-- [API Reference](/base-chain/api-reference/flashblocks-api/flashblocks-api-overview) — RPC methods, WebSocket subscriptions, and infrastructure stream schema
-- [Flashblocks Deep Dive](https://blog.base.dev/flashblocks-deep-dive) — Engineering blog post with implementation details
diff --git a/docs/base-chain/flashblocks/faq.mdx b/docs/base-chain/flashblocks/faq.mdx
index 750ec7ddb..bbff11673 100644
--- a/docs/base-chain/flashblocks/faq.mdx
+++ b/docs/base-chain/flashblocks/faq.mdx
@@ -1,13 +1,46 @@
---
-title: Flashblocks FAQ
-sidebarTitle: FAQ
-description: Frequently asked questions about Flashblocks, including block building, WebSocket data, RPC usage, and node setup.
+title: Flashblocks Reference
+sidebarTitle: Flashblocks Reference
+description: Reference for Flashblocks on Base — key concepts, architecture, and frequently asked questions about block building, WebSocket data, RPC usage, and node setup.
---
-For a comprehensive introduction to how Flashblocks work, see the [Flashblocks Overview](/base-chain/flashblocks/overview).
+For how Flashblocks affect block building and transaction ordering, see [Transaction Ordering](/base-chain/network-information/transaction-ordering#flashblocks).
+Flashblocks introduce **200ms** incremental block updates to Base, built in collaboration with [Flashbots](https://www.flashbots.net/). They stream sub-blocks within the standard 2-second block interval, giving applications near-instant sequencer preconfirmations.
+
+## Key concepts
+
+| Term | Definition |
+|------|------------|
+| **Flashblock** | A 200ms sub-block containing a portion of the full block's transactions |
+| **Preconfirmation** | An ultra-fast signal that a transaction will be included, before the full block is sealed |
+| **Full Block** | A series of 10 Flashblocks combined to form the complete 2-second block |
+
+## Architecture
+
+Base operates a high-availability sequencer system:
+
+| Component | Role |
+|-----------|------|
+| **base-consensus** | Consensus layer (CL) — replaced op-node after Azul |
+| **base-reth-node** | Execution layer (EL) — replaced op-geth after Azul |
+| **op-conductor** | High-availability controller with Raft consensus for leader election |
+
+One sequencer instance acts as the **leader**, building blocks and propagating them via P2P; the others act as **followers** that sync the chain. Leadership transfers if the current leader stops producing blocks.
+
+Flashblocks add several infrastructure components on top of this system:
+
+| Component | Purpose | What it unlocks |
+|-----------|---------|-----------------|
+| **rollup-boost** | CL↔EL Engine API proxy | Shares Flashblocks with the EL without modifying the CL, providing a stable seam for future block-building evolutions (multi-builder, etc.) |
+| **base-builder** | Out-of-protocol builder at 200ms cadence | Produces sub-second Flashblocks, decoupled from the EL, enabling pluggable builder mechanisms |
+| **websocket-proxy** | Flashblocks stream fan-out | Broadcast layer so many consumers can read the stream without overwhelming the builder |
+| **[base](https://github.com/base/base)** | RPC surface exposing preconfirmations | Converts streamed Flashblocks into familiar RPCs so apps and wallets can consume preconfirmation state |
+
+[rollup-boost](https://github.com/flashbots/rollup-boost) is built and maintained by Flashbots, while Base maintains [base-builder](https://github.com/base/base/tree/main/crates/builder), the websocket-proxy, and the [base](https://github.com/base/base) components.
+
## Block Building
@@ -18,7 +51,7 @@ For a comprehensive introduction to how Flashblocks work, see the [Flashblocks O
No significant differences—both order transactions by fee. The main difference is timing: Flashblocks occur every 200ms instead of every 2 seconds.
- See [Block Building](/base-chain/network-information/block-building#flashblocks) for details.
+ See [Transaction Ordering](/base-chain/network-information/transaction-ordering#flashblocks) for details.
@@ -26,16 +59,13 @@ For a comprehensive introduction to how Flashblocks work, see the [Flashblocks O
- Transactions with large gas limits (> ~18.75M gas, which is 1/10 of the ~187.5M block limit) may have longer inclusion times. This is because the builder allocates gas cumulatively—each Flashblock `j` can use up to `j/10` of the total block gas limit. Large transactions can be included once enough cumulative capacity exists.
+ Inclusion timing is driven primarily by priority fee, not transaction size. The builder allocates gas cumulatively—each Flashblock `j` can use up to `j/10` of the total block gas limit—so in principle a very large transaction has a harder time landing in the first Flashblock. In practice this rarely matters: Base's [per-transaction gas maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) (16,777,216 gas, ~16.7M) is below Flashblock 1's ~40M capacity, so any valid transaction fits in the first Flashblock by size alone. If a transaction is slow to include, the usual cause is a low priority fee relative to others competing in the same 200ms window.
- See [Gas & Transaction Sizing](/base-chain/flashblocks/app-integration#gas-&-transaction-sizing) for the full breakdown.
+ See [Throughput and Limits](/base-chain/network-information/throughput-and-limits) for gas limits and throughput-related network parameters.
- There's no way to guarantee which Flashblock a transaction lands in, similar to how you can't guarantee a specific block. To improve chances of quick inclusion:
-
- - Set a higher priority fee
- - Keep gas limits below ~18.75M (1/10 of block limit) to be eligible for Flashblock 1
+ There's no way to guarantee which Flashblock a transaction lands in, similar to how you can't guarantee a specific block. Gas size isn't the limiting factor—the [per-transaction gas maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) (~16.7M) is below Flashblock 1's ~40M capacity, so any valid transaction is eligible for the first Flashblock. To improve your chances of quick inclusion, set a higher priority fee.
@@ -76,7 +106,7 @@ For a comprehensive introduction to how Flashblocks work, see the [Flashblocks O
- **RPC API**: Standard JSON-RPC methods with the `pending` tag
- **WebSocket subscriptions**: Use `eth_subscribe` via your node provider's WebSocket endpoint
- See [App Integration](/base-chain/flashblocks/app-integration) for implementation details.
+ See the [RPC overview](/base-chain/api-reference/rpc-overview#flashblocks) for implementation details.
@@ -162,4 +192,12 @@ For a comprehensive introduction to how Flashblocks work, see the [Flashblocks O
Use the Reth binary from the [Base Reth repository](https://github.com/base/reth). See the [Enable Flashblocks guide](/base-chain/node-operators/run-a-base-node#enable-flashblocks) for complete setup instructions.
-
\ No newline at end of file
+
+
+---
+
+## Further reading
+
+- [Enable Flashblocks](/base-chain/node-operators/run-a-base-node#enable-flashblocks) — run your own Flashblocks-aware RPC node
+- [Flashblocks API Reference](/base-chain/api-reference/flashblocks-api/flashblocks-api-overview) — RPC methods, WebSocket subscriptions, and infrastructure stream schema
+- [Flashblocks Deep Dive](https://blog.base.dev/flashblocks-deep-dive) — engineering blog post with implementation details, built in collaboration with [Flashbots](https://www.flashbots.net/)
diff --git a/docs/base-chain/flashblocks/overview.mdx b/docs/base-chain/flashblocks/overview.mdx
deleted file mode 100644
index 21f2c7cc7..000000000
--- a/docs/base-chain/flashblocks/overview.mdx
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: Flashblocks Overview
-sidebarTitle: Overview
-description: Understand the sequencer architecture, block building algorithm, and integration options for Flashblocks on Base.
----
-
-## What are Flashblocks?
-
-Flashblocks introduce **200ms** incremental state updates to Base, significantly reducing perceived latency for users.
-
-Built in collaboration with [Flashbots](https://www.flashbots.net/), this mechanism streams sub-blocks within the standard 2-second block interval, providing near-instant sequencer preconfirmations, allowing applications to reflect state changes long before the full block is gossiped to the rest of the network.
-
-
-Flashblocks are always live on Base. All blocks are built by the Flashblocks builder. Apps can choose whether to consume preconfirmations or wait for standard 2-second block finality.
-
-
-### Key Concepts
-
-| Term | Definition |
-|------|------------|
-| **Flashblock** | A 200ms sub-block containing a portion of the full block's transactions |
-| **Preconfirmation** | An ultra-fast signal that a transaction will be included, before the full block is sealed |
-| **Full Block** | A series of 10 Flashblocks combined to form the complete 2-second block |
-
-Each block contains **10 Flashblocks** (indexes 1-10), each arriving every 200ms. Index 0 exists but only contains system transactions. See [Gas & Transaction Sizing](/base-chain/flashblocks/app-integration#gas-&-transaction-sizing) for how gas budgets work.
-
-
-## Architecture
-
-For details on the sequencer system and Flashblocks infrastructure components (rollup-boost, base-builder, websocket-proxy, and base), see the [Architecture](/base-chain/flashblocks/architecture) page.
-
-## Transaction Lifecycle
-
-When you send a transaction to Base, here's what happens:
-
-### 1. Submission
-```
-User → DNS (mainnet.base.org) → Load Balancer → Proxyd → Mempool
-```
-
-The transaction reaches the private mempool and is inserted into the txpool as pending.
-
-### 2. Distribution
-The mempool maintains P2P connections with execution layers (base-reth-node, base-builder), ensuring all pending transactions are synced for block building.
-
-### 3. Block Building
-During each 200ms block building loop, base-builder selects transactions based on:
-
-1. **Transaction fee** — transactions are ordered by fee (highest first)
-2. **Gas limit and remaining capacity** — each Flashblock `j` can use up to `j/10` of the total block gas limit
-
-
-**Dynamic Mempool:** The builder uses a dynamic mempool that continuously accepts new transactions while building. This minimizes inclusion latency but means a late-arriving high-fee transaction may appear after an already-committed lower-fee transaction within the same Flashblock. This is expected behavior, not a violation of fee priority—transactions are ordered by fee *at the time they're selected*.
-
-
-### 4. Block Building Algorithm
-
-The builder follows this process for each 2-second block:
-
-```
-FOR each flashblock j FROM 0 TO 10:
- 1. Wait until next 200ms window
- 2. Calculate available gas: (j / 10) × total_block_gas_limit
- 3. Sort pending transactions by fee (descending)
- 4. Select top transactions that fit within available gas
- 5. Execute transactions and update state
- 6. Stream flashblock to websocket-proxy
-```
-
-
-**Index 0** contains only system transactions and doesn't use any gas limit. **Indexes 1-10** are the actual Flashblocks that pull pending transactions from the txpool.
-
-
-### 5. Preconfirmation Delivery
-Once a transaction is included in a Flashblock, it's streamed to the websocket-proxy, which RPC nodes listen to. When you call a Flashblocks-aware RPC method (like `eth_getTransactionReceipt`), the node retrieves the preconfirmed data from its cache.
-
-
-For the complete infrastructure stream schema, see the [Flashblocks API Overview](/base-chain/api-reference/flashblocks-api/flashblocks-api-overview) reference: [Flashblock](/base-chain/api-reference/flashblocks-api/flashblocks-api-overview#flashblock-object), [Diff](/base-chain/api-reference/flashblocks-api/flashblocks-api-overview#diff-object), [Metadata](/base-chain/api-reference/flashblocks-api/flashblocks-api-overview#metadata-object), [Receipt](/base-chain/api-reference/flashblocks-api/flashblocks-api-overview#receipt-object).
-
-
-## Further Reading
-- [FAQ](/base-chain/flashblocks/faq) — Common questions about Flashblocks
-- [Block Building](/base-chain/network-information/block-building) — Detailed block ordering configuration
-- [Flashblocks Deep Dive](https://blog.base.dev/flashblocks-deep-dive) — Engineering blog post with implementation details
diff --git a/docs/base-chain/llms-full.txt b/docs/base-chain/llms-full.txt
index 5cff0bf21..ee157a89e 100644
--- a/docs/base-chain/llms-full.txt
+++ b/docs/base-chain/llms-full.txt
@@ -2,56 +2,49 @@
## Base Chain — Deep Guide for LLMs
-> Base is a fast, low‑cost Ethereum L2 built on the OP Stack. This guide orients an LLM to deployment, connectivity, network details, node operations, and security across the Base Chain docs.
+> Base is a fast, low‑cost Ethereum L2 built on the OP Stack. This guide orients an LLM to chain concepts, connectivity, network details, node operations, and security across the Base Chain docs.
### What you can do here
-- Deploy smart contracts quickly (testnet and mainnet)
- Connect apps to read/write on Base
-- Understand fees, contracts, and bridges
+- Understand ordering, finality, throughput, fees, contracts, and bridges
- Use the full Ethereum JSON-RPC API and Flashblocks pre-confirmation API
- Operate performant nodes
- Obtain testnet ETH from faucets
-- Discover Flashblocks resources
- Follow security disclosure guidance
## Navigation (with brief descriptions)
-### Quickstart
-- [Why Base](https://docs.base.org/base-chain/quickstart/why-base.md) — Platform value prop
-- [Deploy on Base](https://docs.base.org/base-chain/quickstart/deploy-on-base.md) — Deploy contracts (Foundry)
-- [Connecting to Base](https://docs.base.org/base-chain/quickstart/connecting-to-base.md) — App connectivity
-- [Base-Solana Bridge](https://docs.base.org/base-chain/quickstart/base-solana-bridge.md) — Bridge between Base and Solana
-
-### Network Information
-- [Base Contracts](https://docs.base.org/base-chain/network-information/base-contracts.md) — Canonical addresses
-- [Network Fees](https://docs.base.org/base-chain/network-information/network-fees.md) — Fee model
-- [Block Building](https://docs.base.org/base-chain/network-information/block-building.md) — Block production
-- [Diffs vs Ethereum](https://docs.base.org/base-chain/network-information/diffs-ethereum-base.md) — Differences from L1
-- [Bridges](https://docs.base.org/base-chain/network-information/bridges.md) — Bridges
-- [Transaction Finality](https://docs.base.org/base-chain/network-information/transaction-finality.md) — Finality model
-- [Troubleshooting Transactions](https://docs.base.org/base-chain/network-information/troubleshooting-transactions.md) — Diagnose common transaction issues
-- [Configuration Changelog](https://docs.base.org/base-chain/network-information/configuration-changelog.md) — Network config changes
-- [Network Faucets](https://docs.base.org/base-chain/network-information/network-faucets.md) — Testnet ETH for Base Sepolia
+### Introduction
+- [Chain Overview](https://docs.base.org/base-chain/overview.md) — Entry point for Base Chain docs
-### Flashblocks
-- [Overview](https://docs.base.org/base-chain/flashblocks/overview.md) — What Flashblocks is and how the two-tier RPC system works
-- [App Integration](https://docs.base.org/base-chain/flashblocks/app-integration.md) — Apps using Flashblocks
-- [Architecture](https://docs.base.org/base-chain/flashblocks/architecture.md) — How the sequencer emits Flashblocks and nodes consume them
-- [FAQ](https://docs.base.org/base-chain/flashblocks/faq.md) — Frequently asked questions about Flashblocks
-
-### API Reference
-- [Overview](https://docs.base.org/base-chain/api-reference/rpc-overview.md) — Networks, endpoints (Standard and Flashblocks), request/response format, error codes, block parameters, and full method index for all three API groups
-- [Ethereum JSON-RPC API](https://docs.base.org/base-chain/api-reference/ethereum-json-rpc-api/eth_blockNumber.md) — Core Ethereum protocol methods: account state, blocks, transactions, gas, logs, chain info, and WebSocket subscriptions (28 methods total)
-- [Flashblocks API](https://docs.base.org/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.md) — Flashblocks-specific HTTP methods (eth_simulateV1, base_transactionStatus), WebSocket subscriptions (newFlashblockTransactions, pendingLogs, newFlashblocks), and the raw infrastructure stream schema
-- [Debug API](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceTransaction.md) — EVM execution tracing: debug_traceTransaction, debug_traceBlockByHash, debug_traceBlockByNumber
+### Core Concepts
+- [Transaction Ordering](https://docs.base.org/base-chain/network-information/transaction-ordering.md) — How blocks are ordered on Base
+- [Transaction Finality](https://docs.base.org/base-chain/network-information/transaction-finality.md) — Detailed information about transaction finality on Base
+- [Throughput and Limits](https://docs.base.org/base-chain/network-information/throughput-and-limits.md) — Gas limits and throughput-related network parameters on Base
+- [Network Fees](https://docs.base.org/base-chain/network-information/network-fees.md) — L2 execution and L1 security fees on Base
+- [Bridging and Withdrawals](https://docs.base.org/base-chain/network-information/bridging-and-withdrawals.md) — Deposits, standard withdrawals, 7 day finalization, and faster withdrawal options
### Node Operators
- [Run a Base Node](https://docs.base.org/base-chain/node-operators/run-a-base-node.md) — Node setup
-- [Base Azul Upgrade](https://docs.base.org/base-chain/node-operators/base-v1-upgrade.md) — Migrate to base-reth-node and base-consensus for Azul
- [Performance Tuning](https://docs.base.org/base-chain/node-operators/performance-tuning.md) — Optimization
- [Snapshots](https://docs.base.org/base-chain/node-operators/snapshots.md) — Snapshot sync
- [Troubleshooting](https://docs.base.org/base-chain/node-operators/troubleshooting.md) — Common fixes
+
+### Network Reference
+- [Connecting to Base](https://docs.base.org/base-chain/quickstart/connecting-to-base.md) — App connectivity
- [Node Providers](https://docs.base.org/base-chain/node-operators/node-providers.md) — RPC node providers for Base
+- [Base Contracts](https://docs.base.org/base-chain/network-information/base-contracts.md) — Canonical addresses
+- [Base-Solana Bridge](https://docs.base.org/base-chain/network-information/base-solana-bridge.md) — Bridge between Base and Solana
+- [Ecosystem Bridges](https://docs.base.org/base-chain/network-information/ecosystem-bridges.md) — Available bridge providers and routes
+- [Network Faucets](https://docs.base.org/base-chain/network-information/network-faucets.md) — Testnet ETH for Base Sepolia
+- [Flashblocks FAQ](https://docs.base.org/base-chain/flashblocks/faq.md) — Frequently asked questions about Flashblocks, including block building, WebSocket data, RPC usage, and node setup
+- [Troubleshooting Transactions](https://docs.base.org/base-chain/network-information/troubleshooting-transactions.md) — Diagnose common transaction issues
+
+### API Reference
+- [Overview](https://docs.base.org/base-chain/api-reference/rpc-overview.md) — Networks, endpoints, preconfirmation app guidance, request/response format, error codes, block parameters, and full method index for all three API groups
+- [Ethereum JSON-RPC API](https://docs.base.org/base-chain/api-reference/ethereum-json-rpc-api/eth_blockNumber.md) — Core Ethereum protocol methods: account state, blocks, transactions, gas, logs, chain info, and WebSocket subscriptions (28 methods total)
+- [Flashblocks API](https://docs.base.org/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.md) — Flashblocks-specific HTTP methods (eth_simulateV1, base_transactionStatus), WebSocket subscriptions (newFlashblockTransactions, pendingLogs, newFlashblocks), and the raw infrastructure stream schema
+- [Debug API](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceTransaction.md) — EVM execution tracing: debug_traceTransaction, debug_traceBlockByHash, debug_traceBlockByNumber
### Builder Codes
- [Builder Codes](https://docs.base.org/apps/builder-codes/builder-codes.md) — Overview of the Builder Codes program
@@ -104,7 +97,7 @@
## Quickstart (excerpts)
-Source: `https://docs.base.org/base-chain/quickstart/deploy-on-base.md`
+Source: `https://docs.base.org/apps/quickstart/deploy-on-base.md`
Deploy with Foundry to Base Sepolia:
@@ -129,15 +122,15 @@ const client = createPublicClient({ chain: base, transport: http() })
## Key Concepts (excerpts)
-Source: `https://docs.base.org/base-chain/network-information/diffs-ethereum-base.md`
+Source: `https://docs.base.org/base-chain/overview.md`
- OP Stack rollup: Base batches L2 transactions and posts data to Ethereum L1, inheriting L1 security.
- Fees: Total includes L2 execution and L1 data costs. See fee breakdown and estimator.
- Source: `https://docs.base.org/base-chain/network-information/network-fees.md`
- Canonical contracts: Use published address lists for bridges, system contracts, and registry.
- Source: `https://docs.base.org/base-chain/network-information/base-contracts.md`
-- Bridges: Official and third‑party bridge options for moving assets to/from Base.
- - Source: `https://docs.base.org/base-chain/network-information/bridges.md`
+- Ecosystem bridges: Official and third‑party bridge options for moving assets to/from Base.
+ - Source: `https://docs.base.org/base-chain/network-information/ecosystem-bridges.md`
## Infrastructure (pruned)
@@ -173,17 +166,17 @@ curl -s -X POST "$BASE_RPC" -H 'content-type: application/json' \
```
-## Flashblocks (excerpts)
+## Preconfirmations (excerpts)
Sources:
-- `https://docs.base.org/base-chain/flashblocks/faq.md`
-- `https://docs.base.org/base-chain/flashblocks/app-integration.md`
+- `https://docs.base.org/base-chain/network-information/transaction-ordering.md`
+- `https://docs.base.org/base-chain/api-reference/rpc-overview.md`
- `https://docs.base.org/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.md`
- Overview: Flashblocks provide sub-200ms preconfirmed block state on Base, enabling lower-latency reads and faster transaction confirmation signals.
- Ecosystem: Review apps that make use of Flashblocks‑related infra and the node providers who support relevant capabilities.
- When to consider: High‑frequency reads/writes, market‑sensitive UX, or services where propagation and data freshness are critical.
-- Integration: Connect to `mainnet.base.org` (or `sepolia.base.org`); use `"pending"` block tag to query preconfirmed state. Follow provider documentation and the Flashblocks docs for setup and operational guidance.
+- Integration: Connect to `mainnet.base.org` (or `sepolia.base.org`); use the `"pending"` block tag or preconfirmation WebSocket subscriptions to query preconfirmed state. Follow provider documentation and the RPC overview for setup and operational guidance.
- Validation: Measure end‑to‑end latency and consistency across providers as part of your rollout plan.
Simple latency probe (conceptual):
diff --git a/docs/base-chain/llms.txt b/docs/base-chain/llms.txt
index f8bc3ff6a..33e7a8237 100644
--- a/docs/base-chain/llms.txt
+++ b/docs/base-chain/llms.txt
@@ -2,44 +2,39 @@
## Base Chain Documentation
-> Base is a fast, low-cost Ethereum L2 for building global onchain apps; start here to deploy, connect, and operate reliably.
+> Base is a fast, low-cost Ethereum L2 for building global onchain apps; start here to understand chain concepts, connect to networks, and operate reliably.
-## Quickstart
-- [Why Base](https://docs.base.org/base-chain/quickstart/why-base.md) — Why build on Base
-- [Deploy on Base](https://docs.base.org/base-chain/quickstart/deploy-on-base.md) — Set up Foundry, configure RPCs, and deploy your first contract
-- [Connecting to Base](https://docs.base.org/base-chain/quickstart/connecting-to-base.md) — Configure providers and clients to read/write on Base
-- [Base-Solana Bridge](https://docs.base.org/base-chain/quickstart/base-solana-bridge.md) — Bridge assets between Base and Solana
-
-## Network Information
-- [Network Fees](https://docs.base.org/base-chain/network-information/network-fees.md) — L2 execution and L1 data costs on Base
-- [Base Contracts](https://docs.base.org/base-chain/network-information/base-contracts.md) — Core contracts and addresses
-- [Block Building](https://docs.base.org/base-chain/network-information/block-building.md) — How blocks are ordered and built on Base
-- [Bridges](https://docs.base.org/base-chain/network-information/bridges.md) — Official and third-party bridge options
-- [Differences: Ethereum & Base](https://docs.base.org/base-chain/network-information/diffs-ethereum-base.md) — Behavioral differences between Base and Ethereum
-- [Transaction Finality](https://docs.base.org/base-chain/network-information/transaction-finality.md) — When transactions become irreversible on Base
-- [Troubleshooting Transactions](https://docs.base.org/base-chain/network-information/troubleshooting-transactions.md) — Diagnose and fix common transaction issues
-- [Configuration Changelog](https://docs.base.org/base-chain/network-information/configuration-changelog.md) — Log of network configuration changes
-- [Network Faucets](https://docs.base.org/base-chain/network-information/network-faucets.md) — Obtain testnet ETH for Base Sepolia
+## Introduction
+- [Chain Overview](https://docs.base.org/base-chain/overview.md) — Start here for Base Chain docs, including concepts, network reference, node operation, APIs, and protocol specifications.
-## Flashblocks
-- [Overview](https://docs.base.org/base-chain/flashblocks/overview.md) — What Flashblocks is and how it works
-- [App Integration](https://docs.base.org/base-chain/flashblocks/app-integration.md) — How apps integrate with Flashblocks
-- [Architecture](https://docs.base.org/base-chain/flashblocks/architecture.md) — Sequencer architecture and infrastructure components
-- [FAQ](https://docs.base.org/base-chain/flashblocks/faq.md) — Frequently asked questions about Flashblocks
-
-## API Reference
-- [Overview](https://docs.base.org/base-chain/api-reference/rpc-overview.md) — Networks, endpoints, request/response format, and full method index
-- [Ethereum JSON-RPC API](https://docs.base.org/base-chain/api-reference/ethereum-json-rpc-api/eth_blockNumber.md) — Core Ethereum protocol methods (eth_, net_, web3_)
-- [Flashblocks API](https://docs.base.org/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.md) — Flashblocks-specific methods, WebSocket subscriptions, and infrastructure stream schema
-- [Debug API](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceTransaction.md) — EVM execution tracing and block replay
+## Core Concepts
+- [Transaction Ordering](https://docs.base.org/base-chain/network-information/transaction-ordering.md) — How blocks are ordered on Base
+- [Transaction Finality](https://docs.base.org/base-chain/network-information/transaction-finality.md) — Detailed information about transaction finality on Base
+- [Throughput and Limits](https://docs.base.org/base-chain/network-information/throughput-and-limits.md) — Gas limits and throughput-related network parameters on Base
+- [Network Fees](https://docs.base.org/base-chain/network-information/network-fees.md) — L2 execution and L1 security fees on Base
+- [Bridging and Withdrawals](https://docs.base.org/base-chain/network-information/bridging-and-withdrawals.md) — How deposits, standard withdrawals, and faster withdrawal options work on Base
## Node Operators
- [Run a Base Node](https://docs.base.org/base-chain/node-operators/run-a-base-node.md) — Setup and operations guide
-- [Base Azul Upgrade](https://docs.base.org/base-chain/node-operators/base-v1-upgrade.md) — Migrate to base-reth-node and base-consensus for Azul
- [Performance Tuning](https://docs.base.org/base-chain/node-operators/performance-tuning.md) — Optimize node performance
- [Snapshots](https://docs.base.org/base-chain/node-operators/snapshots.md) — Snapshot sync to speed up initial node setup
- [Troubleshooting](https://docs.base.org/base-chain/node-operators/troubleshooting.md) — Diagnose and fix common node issues
+
+## Network Reference
+- [Connecting to Base](https://docs.base.org/base-chain/quickstart/connecting-to-base.md) — Configure providers and clients to read/write on Base
- [Node Providers](https://docs.base.org/base-chain/node-operators/node-providers.md) — RPC node providers for Base
+- [Base Contracts](https://docs.base.org/base-chain/network-information/base-contracts.md) — Core contracts and addresses
+- [Base-Solana Bridge](https://docs.base.org/base-chain/network-information/base-solana-bridge.md) — Bridge assets between Base and Solana
+- [Ecosystem Bridges](https://docs.base.org/base-chain/network-information/ecosystem-bridges.md) — Available bridge providers and routes for moving assets to and from Base
+- [Network Faucets](https://docs.base.org/base-chain/network-information/network-faucets.md) — Obtain testnet ETH for Base Sepolia
+- [Flashblocks FAQ](https://docs.base.org/base-chain/flashblocks/faq.md) — Frequently asked questions about Flashblocks, including block building, WebSocket data, RPC usage, and node setup
+- [Troubleshooting Transactions](https://docs.base.org/base-chain/network-information/troubleshooting-transactions.md) — Diagnose and fix common transaction issues
+
+## API Reference
+- [Overview](https://docs.base.org/base-chain/api-reference/rpc-overview.md) — Networks, endpoints, preconfirmation app guidance, request/response format, and full method index
+- [Ethereum JSON-RPC API](https://docs.base.org/base-chain/api-reference/ethereum-json-rpc-api/eth_blockNumber.md) — Core Ethereum protocol methods (eth_, net_, web3_)
+- [Flashblocks API](https://docs.base.org/base-chain/api-reference/flashblocks-api/flashblocks-api-overview.md) — Flashblocks-specific methods, WebSocket subscriptions, and infrastructure stream schema
+- [Debug API](https://docs.base.org/base-chain/api-reference/debug-api/debug_traceTransaction.md) — EVM execution tracing and block replay
## Protocol Specs
- [Overview](https://docs.base.org/base-chain/specs/index.md) — Full Base Chain protocol specification index
diff --git a/docs/base-chain/quickstart/base-solana-bridge.mdx b/docs/base-chain/network-information/base-solana-bridge.mdx
similarity index 100%
rename from docs/base-chain/quickstart/base-solana-bridge.mdx
rename to docs/base-chain/network-information/base-solana-bridge.mdx
diff --git a/docs/base-chain/network-information/block-building.mdx b/docs/base-chain/network-information/block-building.mdx
deleted file mode 100644
index fe83ea2ee..000000000
--- a/docs/base-chain/network-information/block-building.mdx
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Block Building
-slug: /block-building
-description: This page outlines how Base blocks are built.
----
-
-## Overview
-This section describes how blocks are ordered on the Base networks. The ordering is separate from the UX,
-for example the sequencer could be building Flashblocks every 200ms, without these Flashblocks being exposed publicly. In this scenario, block ordering
-would change but the user experience would remain consistent.
-
-The Base networks are currently configured in the following ways:
-
-| Network | Current Configuration | Upcoming Deployments |
-|--------------|-----------------------------|------------------------|
-| Base Mainnet | [Flashblocks](#flashblocks) + [Per-Transaction Gas Max](#per-transaction-gas-maximum) | |
-| Base Sepolia | [Flashblocks](#flashblocks) + [Per-Transaction Gas Max](#per-transaction-gas-maximum) | |
-
-See the [Configuration Changelog](/base-chain/network-information/configuration-changelog) for a history of changes to block building and other network parameters.
-
-## Configurations
-
-### Flashblocks
-
-Blocks are built using [base-builder](https://github.com/base/base/tree/main/crates/builder) with priority fee auctions occurring every **200ms**. This reduces effective block times from 2 seconds to 200 milliseconds through preconfirmations.
-
-
-For a comprehensive technical deep dive into Flashblocks architecture, see the [Flashblocks Overview](/base-chain/flashblocks/overview).
-
-
-*There are three key differences from vanilla ordering:*
-
-1. **Timing** — Flashblocks are built every 200ms, each ordering a portion of the block. Once built and broadcast, transaction ordering is locked. Later-arriving transactions with higher priority fees cannot be included in earlier Flashblocks.
-
-2. **Gas Allocation** — Each Flashblock has an incrementally increasing gas budget. Flashblock 1 can use 1/10 of the block gas limit, Flashblock 2 can use 2/10, and so on until Flashblock 10 has access to the full limit.
-
- | Flashblock | Available Gas |
- |------------|---------------|
- | 1 | ~14M gas (1/10) |
- | 2 | ~28M gas (2/10) |
- | 3 | ~42M gas (3/10) |
- | ... | ... |
- | 10 | ~140M gas (full) |
-
-
- Transactions exceeding 14M gas cannot fit in Flashblock 1 and must wait for later Flashblocks. Monitor inclusion latency if your app creates large transactions.
-
-
-3. **Dynamic Mempool** — The builder continuously accepts new transactions while building each Flashblock. This minimizes inclusion latency but means transactions are ordered by fee *at the time of selection*, not globally across all transactions that arrive during the 200ms window. A late-arriving high-fee transaction may appear after an already-committed lower-fee transaction.
-
-
- This is a deliberate tradeoff: faster inclusion at the cost of occasionally "breaking" expected priority gas auction (PGA) ordering within a Flashblock. See the [Flashblocks FAQ](/base-chain/flashblocks/faq) for more details.
-
-
-### Per-Transaction Gas Maximum
-
-As of the [Azul hardfork](/base-chain/specs/upgrades/azul/exec-engine#transaction-gas-limit-cap), Base enforces a protocol-level per-transaction gas maximum of **16,777,216 gas (2^24)** via [EIP-7825](https://eips.ethereum.org/EIPS/eip-7825). Transactions that specify a gas limit above this value are **rejected during block validation**. `eth_sendTransaction` or `eth_sendRawTransaction` will return a JSON-RPC error (for example: `exceeds maximum per-transaction gas limit`).
-
-
-Deposit transactions are exempt from this cap. They are limited by the maximum gas includable in an L1 block (20,000,000 gas).
-
-
-Bundler operators for smart contract wallets must configure their systems to limit the bundle size to fit within this cap.
-
-### Vanilla
-
-Blocks are built every 2s by `base-reth-node`. Transactions within those blocks are ordered by priority fee.
-
diff --git a/docs/base-chain/network-information/bridging-and-withdrawals.mdx b/docs/base-chain/network-information/bridging-and-withdrawals.mdx
new file mode 100644
index 000000000..d7d9cedbf
--- /dev/null
+++ b/docs/base-chain/network-information/bridging-and-withdrawals.mdx
@@ -0,0 +1,56 @@
+---
+title: Bridging and Withdrawals
+description: How deposits and withdrawals work on Base, including the standard withdrawal flow and faster bridge options.
+---
+
+Bridging moves assets or messages between Base and another chain. Deposits move assets into Base. Withdrawals move assets out of Base.
+
+Deposits and withdrawals have different timing because they rely on different parts of the rollup protocol. Deposits start on another chain and are executed on Base. Standard withdrawals start on Base, must be proven on Ethereum, and can be finalized only after the challenge period has passed.
+
+## Deposits to Base
+
+A deposit is initiated outside Base and becomes a transaction on Base. For Ethereum deposits, the L1 transaction emits data that Base nodes use to derive a corresponding L2 deposit transaction.
+
+Deposit transactions are included as part of the protocol. They do not use the same signature, nonce, or fee fields as ordinary L2 transactions because they are authorized by the L1 deposit event and pay for L2 gas on L1.
+
+For most users, the practical result is simple: after the source-chain transaction is confirmed and processed, the asset or message appears on Base. For the protocol details, see the [Deposits specification](/base-chain/specs/protocol/bridging/deposits).
+
+## Standard withdrawals
+
+A standard withdrawal is a cross-domain transaction initiated on Base and finalized on Ethereum. Standard withdrawals can transfer ETH, bridge supported ERC-20 tokens, or send a message from Base to an L1 contract.
+
+The standard withdrawal flow has three stages:
+
+1. **Initiate on Base:** the withdrawal transaction is sent on Base. This records the withdrawal message in the `L2ToL1MessagePasser` contract.
+2. **Prove on Ethereum:** after the relevant Base state has been posted to Ethereum, anyone can submit a proof to the `OptimismPortal` contract showing that the withdrawal message exists on Base.
+3. **Finalize on Ethereum:** after the 7 day challenge period has passed, anyone can finalize the withdrawal on Ethereum. Finalization releases the assets or relays the message to the target contract.
+
+The relayer that proves or finalizes a withdrawal does not need to be the same account that initiated it. This allows wallets, bridge UIs, or other services to help users complete withdrawals.
+
+
+Standard withdrawals to Ethereum must wait 7 days before they can be finalized. Regular Base transactions and deposits to Base do not have this 7 day wait.
+
+
+## Why standard withdrawals take 7 days
+
+Base uses fault proofs to secure withdrawals. When a withdrawal is proven on Ethereum, the proof relies on an output root that commits to Base state. The 7 day challenge period gives network participants time to dispute an invalid output root before withdrawals that depend on it can be finalized.
+
+If no valid challenge prevents finalization, the withdrawal can be finalized after the challenge period. If the output root becomes invalid, the Base chain does not reorg, but withdrawals proven against that output root cannot be finalized and must be proven again against a valid output root.
+
+See [Transaction Finality](/base-chain/network-information/transaction-finality#finality-for-withdrawal-transactions) for how withdrawal finality differs from ordinary Base transaction finality.
+
+## Faster withdrawal options
+
+Some bridge providers offer faster withdrawals than the standard bridge protocol. These services usually do not make the underlying standard withdrawal challenge period shorter. Instead, they use liquidity, relayers, market makers, or other mechanisms to give users funds on the destination chain before the standard withdrawal has fully finalized.
+
+This can improve user experience, but it adds provider-specific assumptions and fees. Before using a faster bridge, review the provider's terms, supported assets, fees, liquidity, and security model.
+
+For available bridge providers and routes, see [Ecosystem Bridges](/base-chain/network-information/ecosystem-bridges).
+
+## Standard bridge contracts
+
+The standard bridges support cross-domain ETH and ERC-20 transfers. They are built on top of the cross-domain messenger contracts and provide a standard interface for deposits and withdrawals.
+
+The `L2StandardBridge` is a predeploy contract at `0x4200000000000000000000000000000000000010`.
+
+For contract-level details, see the [Standard Bridges specification](/base-chain/specs/protocol/bridging/bridges) and the [Withdrawals specification](/base-chain/specs/protocol/bridging/withdrawals).
diff --git a/docs/base-chain/network-information/configuration-changelog.mdx b/docs/base-chain/network-information/configuration-changelog.mdx
index abde76c1b..13528d5db 100644
--- a/docs/base-chain/network-information/configuration-changelog.mdx
+++ b/docs/base-chain/network-information/configuration-changelog.mdx
@@ -10,28 +10,28 @@ This page tracks configuration changes to the Base networks, including updates t
| Date | Change | Documentation |
|------|--------|---------------|
-| May 28, 2026 | Azul: Reduced per-transaction gas maximum to 16,777,216 (2^24) via EIP-7825 | [Per-Transaction Gas Maximum](/base-chain/network-information/block-building#per-transaction-gas-maximum) |
+| May 28, 2026 | Azul: Reduced per-transaction gas maximum to 16,777,216 (2^24) via EIP-7825 | [Per-Transaction Gas Maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) |
| February 19, 2026 | Increased Minimum Base Fee to 5,000,000 wei | [Minimum Base Fee](/base-chain/network-information/network-fees#minimum-base-fee) |
| February 4, 2026 | Increased EIP-1559 Denominator to 125 | [EIP-1559 Fee Parameters](/base-chain/network-information/network-fees#eip-1559-fee-parameters) |
| February 2, 2026 | Increased Minimum Base Fee to 2,000,000 wei | [Minimum Base Fee](/base-chain/network-information/network-fees#minimum-base-fee) |
| January 22, 2026 | Increased Minimum Base Fee to 1,000,000 wei | [Minimum Base Fee](/base-chain/network-information/network-fees#minimum-base-fee) |
| December 18, 2025 | Increased Minimum Base Fee to 500,000 wei | [Minimum Base Fee](/base-chain/network-information/network-fees#minimum-base-fee) |
| 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) |
+| September 17, 2025 | Enabled Per-Transaction Gas Maximum | [Per-Transaction Gas Maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) |
+| September 11, 2025 | Ended testing Per-Transaction Gas Maximum | [Per-Transaction Gas Maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) |
+| September 10, 2025 | Started testing Per-Transaction Gas Maximum | [Per-Transaction Gas Maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) |
+| July 7, 2025 | Enabled Flashblocks | [Flashblocks](/base-chain/network-information/transaction-ordering#flashblocks) |
+| May 15, 2025 | Ended testing Flashblocks | [Flashblocks](/base-chain/network-information/transaction-ordering#flashblocks) |
+| May 15, 2025 | Started testing Flashblocks | [Flashblocks](/base-chain/network-information/transaction-ordering#flashblocks) |
## Base Sepolia
| Date | Change | Documentation |
|------|--------|---------------|
-| April 20, 2026 | Azul: Reduced per-transaction gas maximum to 16,777,216 (2^24) via EIP-7825 | [Per-Transaction Gas Maximum](/base-chain/network-information/block-building#per-transaction-gas-maximum) |
+| April 20, 2026 | Azul: Reduced per-transaction gas maximum to 16,777,216 (2^24) via EIP-7825 | [Per-Transaction Gas Maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) |
| February 19, 2026 | Increased Minimum Base Fee to 5,000,000 wei | [Minimum Base Fee](/base-chain/network-information/network-fees#minimum-base-fee) |
| February 10, 2026 | Increased EIP-1559 Denominator to 125 | [EIP-1559 Fee Parameters](/base-chain/network-information/network-fees#eip-1559-fee-parameters) |
| February 10, 2026 | Increased Minimum Base Fee to 2,000,000 wei | [Minimum Base Fee](/base-chain/network-information/network-fees#minimum-base-fee) |
| 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) |
+| September 3, 2025 | Enabled Per-Transaction Gas Maximum | [Per-Transaction Gas Maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) |
+| February 25, 2025 | Enabled Flashblocks | [Flashblocks](/base-chain/network-information/transaction-ordering#flashblocks) |
diff --git a/docs/base-chain/network-information/diffs-ethereum-base.mdx b/docs/base-chain/network-information/diffs-ethereum-base.mdx
deleted file mode 100644
index e78dbd55b..000000000
--- a/docs/base-chain/network-information/diffs-ethereum-base.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: "Differences between Ethereum and Base"
-sidebarTitle: 'Differences: Ethereum & Base'
----
-
-Base is built to be as compatible as possible to Ethereum, and there are very few differences when it comes to building on Base versus Ethereum.
-
-However, there are still some minor discrepancies between the behavior of Base and Ethereum that you should be aware of when building apps on top of Base.
-
-These minor differences include:
-
-- [Flashblocks](/base-chain/flashblocks/app-integration)
-- [Minimum base fee](/base-chain/network-information/network-fees#minimum-base-fee)
-- [Bridging](/base-chain/specs/protocol/bridging/bridges)
-- [Precompiles](/base-chain/specs/protocol/execution/evm/precompiles)
-- [Address aliasing](/base-chain/specs/protocol/bridging/deposits#address-aliasing)
-- [Transaction costs](/base-chain/network-information/network-fees)
-- [Chain Finality](/base-chain/network-information/transaction-finality)
\ No newline at end of file
diff --git a/docs/base-chain/network-information/bridges.mdx b/docs/base-chain/network-information/ecosystem-bridges.mdx
similarity index 60%
rename from docs/base-chain/network-information/bridges.mdx
rename to docs/base-chain/network-information/ecosystem-bridges.mdx
index 39f7fcdfe..c18188688 100644
--- a/docs/base-chain/network-information/bridges.mdx
+++ b/docs/base-chain/network-information/ecosystem-bridges.mdx
@@ -1,16 +1,11 @@
---
-title: Bridges
-description: Documentation for bridging assets to Base. This page covers how to bridge assets between Ethereum, Solana, Bitcoin, and Base.
-
+title: Ecosystem Bridges
+description: Available bridge providers and routes for moving assets to and from Base.
---
Base supports bridging assets from multiple chains including Ethereum, Solana, and Bitcoin. While the bridge on bridge.base.org has been deprecated, there are many bridges that support moving assets between Base and other chains.
-For questions, see our [FAQ](#faq).
-
----
-
-## Ethereum ↔ Base
+## Ethereum and Base
### Superbridge
@@ -53,7 +48,7 @@ If you have an ERC-20 token deployed on Ethereum and want to enable bridging to
---
-## Solana ↔ Base
+## Solana and Base
The Base-Solana bridge enables bidirectional token transfers and message passing between Base and Solana networks.
@@ -64,7 +59,7 @@ The Base-Solana bridge enables bidirectional token transfers and message passing
- Optional auto-relay for instant execution
-
+
Complete guide with code examples and contract addresses
@@ -81,12 +76,12 @@ The Base-Solana bridge enables bidirectional token transfers and message passing
| Solana Mainnet | Bridge Program | `HNCne2FkVaNghhjKXapxJzPaBvAKDG1Ge3gqhZyfVWLM` |
-For testnet addresses and full implementation details, see the [Base-Solana Bridge documentation](/base-chain/quickstart/base-solana-bridge#contract-addresses).
+For testnet addresses and full implementation details, see the [Base-Solana Bridge documentation](/base-chain/network-information/base-solana-bridge#contract-addresses).
---
-## Bitcoin → Base
+## Bitcoin -> Base
### Garden
@@ -104,33 +99,3 @@ Garden is a fast non-custodial Bitcoin bridge that enables you to bridge BTC and
Coinbase Technologies, Inc., provides links to these independent service providers for your
convenience but assumes no responsibility for their operations. Any interactions with these
providers are solely between you and the provider.
-
----
-
-## FAQ
-
-
-No, the bridge on bridge.base.org has been deprecated.
-
-
-
-Navigate to one of the Superchain Bridges to look up your transaction.
-
-
-
-Base is committed to decentralization and the Superchain vision. Leveraging the community to bootstrap the Superchain bridges is a step in that direction; increasing censorship resistance and decentralization.
-
-
-
-Superchain Bridges are operated by third parties, not by Coinbase Technologies, Inc. ("Coinbase"). Coinbase does not control, operate, or assume any responsibility for the performance of these external platforms. Before using any Superchain Bridge, you may be required to agree to their terms and conditions. We strongly recommend you review these terms carefully, as well as any privacy policies, to understand your rights and obligations. The integration or inclusion of the Superchain Bridges does not imply an endorsement or recommendation of any bridge by Coinbase.
-
-
-
-The Base-Solana bridge uses validators to verify cross-chain messages. When bridging from Solana to Base, tokens are locked on Solana and minted on Base. When bridging from Base to Solana, tokens are burned on Base and unlocked on Solana. See the [full documentation](/base-chain/quickstart/base-solana-bridge) for implementation details.
-
-
-
-The [Base Discord](https://base.org/discord) community is available around the clock for general questions,
-assistance and support! You can create a support ticket in the #general-support
-channel.
-
diff --git a/docs/base-chain/network-information/throughput-and-limits.mdx b/docs/base-chain/network-information/throughput-and-limits.mdx
new file mode 100644
index 000000000..e9a36a6dd
--- /dev/null
+++ b/docs/base-chain/network-information/throughput-and-limits.mdx
@@ -0,0 +1,68 @@
+---
+title: Throughput and Limits
+description: Gas limits and throughput-related network parameters on Base.
+---
+
+Base throughput is constrained by gas limits, data availability throughput, fee market parameters, and endpoint limits. There is no single transactions-per-second value that applies to every workload, because transactions consume different amounts of gas and data.
+
+Base has sustained multiple bursts of over 5,000 TPS, and throughput continues to increase as the chain scales. For more context, see [Introducing Base Azul](https://blog.base.dev/introducing-base-azul).
+
+## Current limits
+
+| Limit | Value |
+|-------|-------|
+| Full block gas budget | ~400M gas |
+| First Flashblock gas budget | ~40M gas |
+| Per-transaction gas maximum | 16,777,216 gas (2^24) |
+| Deposit transaction limit | Maximum gas includable in an L1 block (20,000,000 gas) |
+
+The full block gas budget is split across Flashblocks while the block is being built. Flashblock 1 can use 1/10 of the block gas limit, Flashblock 2 can use 2/10, and so on until Flashblock 10 has access to the full limit. See [Transaction Ordering](/base-chain/network-information/transaction-ordering#flashblocks) for how this affects transaction ordering.
+
+## Flashblock performance
+
+Flashblocks stream incremental block updates roughly every 200ms, giving apps sub-second preconfirmations within the standard 2-second block.
+
+| Metric | Value |
+|--------|-------|
+| Flashblock build time (P50) | ~10ms |
+| Preconfirmation latency | ~200ms |
+| Full block time | 2 seconds |
+| Flashblocks per block | 10 |
+| Reorg rate | < 0.1% |
+
+See the [Flashblocks Reference](/base-chain/flashblocks/faq) for reorg handling and other common questions.
+
+## Per-transaction gas maximum
+
+As of the [Azul hardfork](/base-chain/specs/upgrades/azul/exec-engine#transaction-gas-limit-cap), Base enforces a protocol-level per-transaction gas maximum of **16,777,216 gas (2^24)** via [EIP-7825](https://eips.ethereum.org/EIPS/eip-7825). Transactions that specify a gas limit above this value are **rejected during block validation**. `eth_sendTransaction` or `eth_sendRawTransaction` will return a JSON-RPC error (for example: `exceeds maximum per-transaction gas limit`).
+
+
+Deposit transactions are exempt from this cap. They are limited by the maximum gas includable in an L1 block (20,000,000 gas).
+
+
+Bundler operators for smart contract wallets must configure their systems to limit the bundle size to fit within this cap.
+
+## Fee parameters
+
+Fees affect practical throughput because they determine whether transactions can be included when demand approaches available capacity.
+
+| Parameter | Current value |
+|-----------|---------------|
+| Minimum base fee | 5,000,000 wei (0.005 gwei) |
+| EIP-1559 elasticity | 6 |
+| EIP-1559 denominator | 125 |
+| Maximum L2 base fee change per block | 4% |
+
+See [Network Fees](/base-chain/network-information/network-fees) for how Base transaction fees are structured, including the L2 execution fee and L1 security fee.
+
+## Data availability throughput
+
+Base transaction data is posted to Ethereum for data availability. If data availability throughput becomes constrained, the sequencer can limit L2 transaction throughput while the batcher catches up.
+
+During DA throttling, even transactions with high priority fees may be delayed. There is no RPC endpoint that calculates priority fee estimates with throttling in mind. See [Troubleshooting Transactions](/base-chain/network-information/troubleshooting-transactions#priority-fee-too-low) for the transaction-submission implications.
+
+## Endpoint limits
+
+Public endpoints are rate-limited and are not suitable for production traffic. Hosted RPC providers can also apply request-per-second limits, compute-unit limits, method restrictions, archive-data limits, or WebSocket subscription limits.
+
+Endpoint limits do not change Base protocol capacity, but they can become the practical bottleneck for apps, wallets, indexers, and monitoring systems. For production use, connect through a [node provider](/base-chain/node-operators/node-providers) or [run a Base node](/base-chain/node-operators/run-a-base-node).
diff --git a/docs/base-chain/network-information/transaction-ordering.mdx b/docs/base-chain/network-information/transaction-ordering.mdx
new file mode 100644
index 000000000..b012a4657
--- /dev/null
+++ b/docs/base-chain/network-information/transaction-ordering.mdx
@@ -0,0 +1,43 @@
+---
+title: Transaction Ordering
+description: Transactions are ordered based priority fee and arrival time, which determines which Flashblock they are included in.
+---
+
+## Overview
+This section describes how transactions are ordered on the Base networks. The ordering is separate from the UX,
+for example the sequencer could be building Flashblocks every 200ms, without these Flashblocks being exposed publicly. In this scenario, block ordering
+would change but the user experience would remain consistent.
+
+## Configurations
+
+### Flashblocks
+
+Blocks are built using [base-builder](https://github.com/base/base/tree/main/crates/builder) with priority fee auctions occurring every **200ms**. This reduces effective block times from 2 seconds to 200 milliseconds through preconfirmations.
+
+*There are three key differences from vanilla ordering:*
+
+1. **Timing** — Flashblocks are built every 200ms, each ordering a portion of the block. Once built and broadcast, transaction ordering is locked. Later-arriving transactions with higher priority fees cannot be included in earlier Flashblocks.
+
+2. **Gas Allocation** — Each Flashblock has an incrementally increasing gas budget. Flashblock 1 can use 1/10 of the block gas limit, Flashblock 2 can use 2/10, and so on until Flashblock 10 has access to the full limit.
+
+ | Flashblock | Available Gas |
+ |------------|---------------|
+ | 1 | ~40M gas (1/10) |
+ | 2 | ~80M gas (2/10) |
+ | 3 | ~120M gas (3/10) |
+ | ... | ... |
+ | 10 | ~400M gas (full) |
+
+
+ Because gas is allocated cumulatively, a transaction must fit within the budget available at the Flashblock it's selected for. Base's [per-transaction gas maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) (~16.7M) is below Flashblock 1's ~40M budget, so any valid transaction can be included starting from the first Flashblock.
+
+
+3. **Dynamic Mempool** — The builder continuously accepts new transactions while building each Flashblock. This minimizes inclusion latency but means transactions are ordered by fee *at the time of selection*, not globally across all transactions that arrive during the 200ms window. A late-arriving high-fee transaction may appear after an already-committed lower-fee transaction.
+
+
+ This is a deliberate tradeoff: faster inclusion at the cost of occasionally "breaking" expected priority gas auction (PGA) ordering within a Flashblock.
+
+
+### Vanilla
+
+Blocks are built every 2s by `base-reth-node`. Transactions within those blocks are ordered by priority fee.
diff --git a/docs/base-chain/network-information/troubleshooting-transactions.mdx b/docs/base-chain/network-information/troubleshooting-transactions.mdx
index b20699ede..135288ede 100644
--- a/docs/base-chain/network-information/troubleshooting-transactions.mdx
+++ b/docs/base-chain/network-information/troubleshooting-transactions.mdx
@@ -14,7 +14,7 @@ If your `maxFeePerGas` is lower than the current base fee, your transaction will
**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:
-```
+```text
maxFeePerGas = baseFee * 2 + maxPriorityFeePerGas
```
@@ -50,7 +50,7 @@ If you submit a transaction with a nonce that has already been used, it will be
### Gas Limit Exceeds Maximum
-Base enforces a [per-transaction gas maximum](/base-chain/network-information/block-building#per-transaction-gas-maximum) of **16,777,216 gas (2^24)**. Transactions specifying a higher gas limit are rejected during block validation.
+Base enforces a [per-transaction gas maximum](/base-chain/network-information/throughput-and-limits#per-transaction-gas-maximum) of **16,777,216 gas (2^24)**. Transactions specifying a higher gas limit are rejected during block validation.
**Error**: `exceeds maximum per-transaction gas limit`
@@ -76,7 +76,7 @@ The contract execution encountered a revert condition.
### Understanding Confirmation Times
-Base produces blocks every 2 seconds, but [Flashblocks](/base-chain/flashblocks/app-integration) provide preconfirmations every 200ms.
+Base produces blocks every 2 seconds, but [Flashblocks](/base-chain/network-information/transaction-ordering#flashblocks) provide preconfirmations every 200ms.
| Confirmation Level | Time | Description |
|-------------------|------|-------------|
diff --git a/docs/base-chain/node-operators/performance-tuning.mdx b/docs/base-chain/node-operators/performance-tuning.mdx
index 1cc6db77d..d3143f2ee 100644
--- a/docs/base-chain/node-operators/performance-tuning.mdx
+++ b/docs/base-chain/node-operators/performance-tuning.mdx
@@ -19,7 +19,7 @@ Running a performant Base node requires adequate hardware. We recommend the foll
(2 × [current chain size] + [snapshot size] + 20% buffer)
```
- This accounts for chain data growth and snapshot restoration space. Refer to [Base Stats](https://base.org/stats) for current chain size and [Base Chain Data](https://basechaindata.vercel.app) for snapshot size.
+This accounts for chain data growth and snapshot restoration space. Refer to [Base Stats](https://base.org/stats) for current chain size and Base Snapshots(https://snapshots.base.org) for snapshot size.
If utilizing Amazon Elastic Block Store (EBS), io2 Block Express volumes are recommended to ensure sufficient disk read speeds, preventing latency issues during initial sync. However, **locally attached NVMe SSDs are strongly recommended over networked storage for optimal performance.**
diff --git a/docs/base-chain/node-operators/run-a-base-node.mdx b/docs/base-chain/node-operators/run-a-base-node.mdx
index 89efac9d2..25fc948b1 100644
--- a/docs/base-chain/node-operators/run-a-base-node.mdx
+++ b/docs/base-chain/node-operators/run-a-base-node.mdx
@@ -131,7 +131,7 @@ RETH_FB_WEBSOCKET_URL="wss://mainnet.flashblocks.base.org/ws" docker compose up
**These WebSocket endpoints are for node infrastructure only.**
-Applications should not connect directly to `wss://mainnet.flashblocks.base.org/ws`. Instead, apps should query your RPC node for Flashblocks data. See the [App Integration guide](/base-chain/flashblocks/app-integration) for details.
+Applications should not connect directly to `wss://mainnet.flashblocks.base.org/ws`. Instead, apps should query your RPC node for Flashblocks data. See the [RPC overview](/base-chain/api-reference/rpc-overview#flashblocks) for details.
diff --git a/docs/base-chain/overview.mdx b/docs/base-chain/overview.mdx
new file mode 100644
index 000000000..635a3379a
--- /dev/null
+++ b/docs/base-chain/overview.mdx
@@ -0,0 +1,26 @@
+---
+title: Chain Overview
+description: Start here for Base Chain docs, including concepts, network reference, node operation, APIs, and protocol specifications.
+---
+
+Base Chain docs are organized around the core concepts, references, and operating guides teams need to build on and integrate with Base.
+
+## Start here
+
+
+
+ Understand transaction ordering, finality, throughput, fees, bridging, and Base-specific execution behavior.
+
+
+ Look up chain IDs, RPC endpoints, connection guidance, providers, contract addresses, faucets, configuration changes, and transaction troubleshooting.
+
+
+ Operate Base infrastructure, including Flashblocks-aware RPC nodes.
+
+
+ Use Base JSON-RPC, Flashblocks API methods, subscriptions, and debug APIs.
+
+
+ Read the Base Chain protocol specification, upgrades, and protocol reference.
+
+
diff --git a/docs/base-chain/quickstart/why-base.mdx b/docs/base-chain/quickstart/why-base.mdx
deleted file mode 100644
index ffa86161d..000000000
--- a/docs/base-chain/quickstart/why-base.mdx
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: 'Why Base?'
----
-
-## TL;DR
-
-- **Cheap, fast, and open platform:** Base is a globally available platform that provides 1-second and <1-cent transactions to anyone in the world.
-- **Access to high-quality tooling:** Builders have access to tools to build incredible onchain experiences for AI, social, media, and entertainment.
-- **A place to earn:** Base has delivered grants to more than 1,000 builders, with plans to continue supporting more.
-- **Reach more users:** Base is committed to helping developers grow their user base by distributing their apps through official Base channels.
-
-
-## A platform for building innovative apps
-
-Base is a global onchain economy of people, builders, and businesses creating the next generation of the open internet. It enables builders to:
-
-- Focus on solving real user problems
-- Scale apps globally by default
-- Onboard users with a click
-- Accept payments from anyone, easily
-
-It’s fast, cheap, and permissionless, meaning anyone can build and use applications on Base.
-
-Base has become the hub for innovative use cases in media, entertainment, social, and even artificial intelligence. [Clanker](https://www.clanker.world), an autonomous AI agent on Base, generated more than $13 million in revenue within three months of its inception. As a cultivator of innovation, Base enables developers to focus on improving their products while retaining more of the upside they generate.
-
-Traditional app distribution models often require developers to sacrifice 30% of their revenue to app marketplaces. These platforms may incentivize predatory practices—selling user data or requiring personal information—and can restrict or deny access at their discretion. For instance, someone in Nairobi might be unable to use many U.S.-based fintech services.
-
-In contrast, decentralized finance (DeFi) apps—an onchain development sector—like [Moonwell](https://moonwell.fi) allow people anywhere in the world to access financial services directly from their phones. This means someone in Nairobi has the same level of access as someone in the U.S., opening opportunities that were previously inaccessible.
-
-
-
-## Expansive developer tools
-
-Developers choose Base for its:
-
-- Always-on global payment rail operating at internet speed
-- Low transaction costs (often less than a cent)
-- Robust developer tooling
-
-But there’s more: Base apps can be launched in hours, not days or weeks, thanks to an extensive suite of tools—many of which are open source. We’re reviving the spirit of innovation where two builders in a garage can create a massively successful business.
-
-Some of the tooling that makes this possible:
-
-- **Base Account:** Onboard your users quickly and securely. Users never have to worry about seed phrases again.
-- **Coinbase Developer Platform:** Access specialized developer services for onchain development, such as free node software, sponsored transactions, and other tools to help you fine-tune your application.
-- **Basenames:** More than just human-readable text to replace an address—Basenames are the front page to a builder’s onchain profile.
-- **Verifications:** Enable unique experiences for users with verified credentials.
-
diff --git a/docs/docs.json b/docs/docs.json
index ebc73aecc..10d4e9b06 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -84,7 +84,7 @@
},
{
"anchor": "Bridge",
- "href": "https://docs.base.org/base-chain/network-information/bridges-mainnet",
+ "href": "https://docs.base.org/base-chain/network-information/ecosystem-bridges",
"icon": "coin"
},
{
@@ -106,34 +106,19 @@
]
},
{
- "group": "Quickstart",
+ "group": "Introduction",
"pages": [
- "base-chain/quickstart/why-base",
- "base-chain/quickstart/deploy-on-base",
- "base-chain/quickstart/connecting-to-base",
- "base-chain/quickstart/base-solana-bridge"
+ "base-chain/overview"
]
},
{
- "group": "Network Information",
+ "group": "Core Concepts",
"pages": [
- "base-chain/network-information/base-contracts",
- "base-chain/network-information/network-fees",
- "base-chain/network-information/block-building",
+ "base-chain/network-information/transaction-ordering",
"base-chain/network-information/transaction-finality",
- "base-chain/network-information/diffs-ethereum-base",
- "base-chain/network-information/troubleshooting-transactions",
- "base-chain/network-information/configuration-changelog",
- "base-chain/network-information/network-faucets"
- ]
- },
- {
- "group": "Flashblocks",
- "pages": [
- "base-chain/flashblocks/overview",
- "base-chain/flashblocks/app-integration",
- "base-chain/flashblocks/architecture",
- "base-chain/flashblocks/faq"
+ "base-chain/network-information/throughput-and-limits",
+ "base-chain/network-information/network-fees",
+ "base-chain/network-information/bridging-and-withdrawals"
]
},
{
@@ -142,10 +127,28 @@
"base-chain/node-operators/run-a-base-node",
"base-chain/node-operators/performance-tuning",
"base-chain/node-operators/snapshots",
- "base-chain/node-operators/node-providers",
"base-chain/node-operators/troubleshooting"
]
},
+ {
+ "group": "Network Reference",
+ "pages": [
+ "base-chain/quickstart/connecting-to-base",
+ "base-chain/node-operators/node-providers",
+ "base-chain/network-information/base-contracts",
+ {
+ "group": "Bridges",
+ "pages": [
+ "base-chain/network-information/base-solana-bridge",
+ "base-chain/network-information/ecosystem-bridges"
+ ]
+ },
+ "base-chain/network-information/network-faucets",
+ "base-chain/flashblocks/faq",
+ "base-chain/network-information/troubleshooting-transactions",
+ "base-chain/network-information/configuration-changelog"
+ ]
+ },
{
"group": "API Reference",
"pages": [
@@ -186,11 +189,11 @@
"group": "Flashblocks API",
"pages": [
"base-chain/api-reference/flashblocks-api/flashblocks-api-overview",
- "base-chain/api-reference/flashblocks-api/eth_simulateV1",
"base-chain/api-reference/flashblocks-api/base_transactionStatus",
+ "base-chain/api-reference/flashblocks-api/eth_simulateV1",
"base-chain/api-reference/flashblocks-api/newFlashblockTransactions",
- "base-chain/api-reference/flashblocks-api/pendingLogs",
- "base-chain/api-reference/flashblocks-api/newFlashblocks"
+ "base-chain/api-reference/flashblocks-api/newFlashblocks",
+ "base-chain/api-reference/flashblocks-api/pendingLogs"
]
},
{
@@ -369,7 +372,7 @@
"anchors": [
{
"anchor": "GitHub",
- "href": "https://github.com/base",
+ "href": "https://github.com/base/base",
"icon": "github"
},
{
@@ -387,11 +390,6 @@
"href": "https://basescan.org/",
"icon": "magnifying-glass"
},
- {
- "anchor": "Support",
- "href": "https://discord.com/invite/buildonbase",
- "icon": "discord"
- },
{
"anchor": "Blog",
"href": "https://blog.base.dev/",
@@ -659,7 +657,8 @@
{
"group": "Quickstart",
"pages": [
- "apps/quickstart/build-app"
+ "apps/quickstart/build-app",
+ "apps/quickstart/deploy-on-base"
]
},
{
@@ -778,7 +777,7 @@
],
"primary": {
"type": "button",
- "label": "Base Dashboard",
+ "label": "Dashboard",
"href": "https://dashboard.base.org/"
}
},
@@ -924,7 +923,67 @@
},
{
"source": "/base-chain/flashblocks/api-reference#endpoints",
- "destination": "/base-chain/api-reference/rpc-overview#endpoints"
+ "destination": "/base-chain/api-reference/rpc-overview#flashblocks"
+ },
+ {
+ "source": "/base-chain/flashblocks/overview",
+ "destination": "/base-chain/network-information/transaction-ordering#flashblocks"
+ },
+ {
+ "source": "/base-chain/flashblocks/app-integration",
+ "destination": "/base-chain/api-reference/rpc-overview#flashblocks"
+ },
+ {
+ "source": "/base-chain/flashblocks/architecture",
+ "destination": "/base-chain/network-information/transaction-ordering#flashblocks"
+ },
+ {
+ "source": "/base-chain/network-information/block-building",
+ "destination": "/base-chain/network-information/transaction-ordering"
+ },
+ {
+ "source": "/block-building",
+ "destination": "/base-chain/network-information/transaction-ordering"
+ },
+ {
+ "source": "/base-chain/network-information/sequencing-policy",
+ "destination": "/base-chain/network-information/transaction-ordering"
+ },
+ {
+ "source": "/base-chain/network-information/transaction-lifecycle",
+ "destination": "/base-chain/network-information/transaction-ordering"
+ },
+ {
+ "source": "/base-chain/network-information/flashblocks",
+ "destination": "/base-chain/network-information/transaction-ordering#flashblocks"
+ },
+ {
+ "source": "/base-chain/network-information/bridges",
+ "destination": "/base-chain/network-information/ecosystem-bridges"
+ },
+ {
+ "source": "/base-chain/network-information/bridge-options",
+ "destination": "/base-chain/network-information/ecosystem-bridges"
+ },
+ {
+ "source": "/base-chain/network-information/diffs-ethereum-base",
+ "destination": "/base-chain/overview"
+ },
+ {
+ "source": "/base-chain/network-information/base-execution-differences",
+ "destination": "/base-chain/overview"
+ },
+ {
+ "source": "/base-chain/quickstart/base-solana-bridge",
+ "destination": "/base-chain/network-information/base-solana-bridge"
+ },
+ {
+ "source": "/base-chain/quickstart/deploy-on-base",
+ "destination": "/apps/quickstart/deploy-on-base"
+ },
+ {
+ "source": "/base-chain/quickstart/why-base",
+ "destination": "/base-chain/overview"
},
{
"source": "/ai-agents/reference/contracts",
@@ -1756,7 +1815,7 @@
},
{
"source": "/base-chain/tools/cross-chain",
- "destination": "/base-chain/network-information/bridges"
+ "destination": "/base-chain/network-information/ecosystem-bridges"
},
{
"source": "/base-chain/tools/account-abstraction",
@@ -1808,7 +1867,7 @@
},
{
"source": "/base-chain/quickstart/bridge-token",
- "destination": "/base-chain/network-information/bridges"
+ "destination": "/base-chain/network-information/ecosystem-bridges"
},
{
"source": "/apps/builder-codes/builder-codes-faq",
@@ -1840,7 +1899,7 @@
},
{
"source": "/base-chain/network-information/bridges-mainnet",
- "destination": "/base-chain/network-information/bridges"
+ "destination": "/base-chain/network-information/ecosystem-bridges"
},
{
"source": "/base-app/introduction/beta-faq",
@@ -2116,15 +2175,15 @@
},
{
"source": "/chain/bridge-an-l1-token-to-base",
- "destination": "/base-chain/network-information/bridges"
+ "destination": "/base-chain/network-information/ecosystem-bridges"
},
{
"source": "/chain/bridges-mainnet",
- "destination": "/base-chain/network-information/bridges-mainnet"
+ "destination": "/base-chain/network-information/ecosystem-bridges"
},
{
"source": "/chain/builder-anniversary-nft",
- "destination": "/base-chain/quickstart/why-base"
+ "destination": "/base-chain/overview"
},
{
"source": "/chain/connecting-to-base",
@@ -2132,7 +2191,7 @@
},
{
"source": "/chain/cross-chain",
- "destination": "/base-chain/tools/cross-chain"
+ "destination": "/base-chain/network-information/ecosystem-bridges"
},
{
"source": "/chain/data-indexers",
@@ -2140,15 +2199,15 @@
},
{
"source": "/chain/decentralizing-base-with-optimism",
- "destination": "/base-chain/quickstart/why-base"
+ "destination": "/base-chain/overview"
},
{
"source": "/chain/deploy-on-base-quickstart",
- "destination": "/base-chain/quickstart/deploy-on-base"
+ "destination": "/apps/quickstart/deploy-on-base"
},
{
"source": "/chain/differences-between-ethereum-and-base",
- "destination": "/base-chain/network-information/diffs-ethereum-base"
+ "destination": "/base-chain/overview"
},
{
"source": "/chain/fees",
@@ -2156,15 +2215,15 @@
},
{
"source": "/chain/flashblocks",
- "destination": "/base-chain/flashblocks/app-integration"
+ "destination": "/base-chain/network-information/transaction-ordering#flashblocks"
},
{
"source": "/chain/flashblocks/apps",
- "destination": "/base-chain/flashblocks/app-integration"
+ "destination": "/base-chain/api-reference/rpc-overview#flashblocks"
},
{
"source": "/base-chain/flashblocks/apps",
- "destination": "/base-chain/flashblocks/app-integration"
+ "destination": "/base-chain/api-reference/rpc-overview#flashblocks"
},
{
"source": "/chain/flashblocks/node-providers",
@@ -2244,7 +2303,7 @@
},
{
"source": "/chain/why-base",
- "destination": "/base-chain/quickstart/why-base"
+ "destination": "/base-chain/overview"
},
{
"source": "/cookbook/growth/cast-actions",
@@ -2716,11 +2775,11 @@
},
{
"source": "/tutorials/deploy-with-foundry",
- "destination": "/base-chain/quickstart/deploy-on-base"
+ "destination": "/apps/quickstart/deploy-on-base"
},
{
"source": "/tutorials/deploy-with-remix",
- "destination": "/base-chain/quickstart/deploy-on-base"
+ "destination": "/apps/quickstart/deploy-on-base"
},
{
"source": "/use-cases/accept-crypto-payments",
@@ -3016,7 +3075,7 @@
},
{
"source": "/cookbook/testing-onchain-apps",
- "destination": "/base-chain/quickstart/deploy-on-base"
+ "destination": "/apps/quickstart/deploy-on-base"
},
{
"source": "/cookbook/ai-prompting",
diff --git a/docs/get-started/base.mdx b/docs/get-started/base.mdx
index 50714f33f..8645f6253 100644
--- a/docs/get-started/base.mdx
+++ b/docs/get-started/base.mdx
@@ -21,14 +21,14 @@ mode: "wide"
### Tokens
[Launch a B20 Token](/get-started/launch-b20-token)
[Launch a Token](/get-started/launch-token)
- [Bridge from Solana](/base-chain/quickstart/base-solana-bridge)
+ [Bridge from Solana](/base-chain/network-information/base-solana-bridge)
### Products
-
+
Network, nodes, and infrastructure
@@ -37,7 +37,7 @@ mode: "wide"
Build and deploy autonomous onchain agents
-
+
Cross-chain asset transfers
diff --git a/docs/get-started/learning-resources.mdx b/docs/get-started/learning-resources.mdx
index 1868f243c..77ac467d4 100644
--- a/docs/get-started/learning-resources.mdx
+++ b/docs/get-started/learning-resources.mdx
@@ -18,6 +18,6 @@ We will be adding more learning resources to help you build on Base. Stay tuned
- New educational content
In the meantime, check out the following resources:
-- [Base Account](/base-account/overview/what-is-base-account), [Apps](/apps/quickstart/build-app), and [Base Chain](/base-chain/quickstart/why-base) for building on Base.
+- [Base Account](/base-account/overview/what-is-base-account), [Apps](/apps/quickstart/build-app), and [Base Chain](/base-chain/overview) for building on Base.
- [CryptoZombies](https://cryptozombies.io/) and [Solidity by Example](https://solidity-by-example.org/) for learning Solidity.
- [Base Prompt Library](/get-started/prompt-library) for building with AI.
diff --git a/docs/get-started/resources-for-ai-agents.mdx b/docs/get-started/resources-for-ai-agents.mdx
index 93e54d96a..f2ce06cae 100644
--- a/docs/get-started/resources-for-ai-agents.mdx
+++ b/docs/get-started/resources-for-ai-agents.mdx
@@ -79,7 +79,7 @@ Once your agent has docs context, point it at the section that matches what you'
| Adding payments or onchain transactions | [Make x402 payments](/agents/guides/x402-payments) |
| Registering an agent for onchain attribution | [Builder Codes for Agents](/apps/builder-codes/agent-developers) |
| Using AI tools with Base Account | [Base Account quickstart for AI tools](/base-account/quickstart/ai-tools-available-for-devs) |
-| Deploying contracts | [Deploy on Base](/base-chain/quickstart/deploy-on-base) |
+| Deploying contracts | [Deploy on Base](/apps/quickstart/deploy-on-base) |
| Building an app on Base | [Build a Base app](/apps/quickstart/build-app) |
## Example prompts
diff --git a/docs/llms-full.txt b/docs/llms-full.txt
index 8f1c04173..e0fe01537 100644
--- a/docs/llms-full.txt
+++ b/docs/llms-full.txt
@@ -13,7 +13,7 @@
### Networks and environments
Sources:
- `https://docs.base.org/base-chain/quickstart/connecting-to-base.md`
-- `https://docs.base.org/base-chain/network-information/diffs-ethereum-base.md`
+- `https://docs.base.org/base-chain/overview.md`
- `https://docs.base.org/base-chain/node-operators/node-providers.md`
> Base runs on Ethereum L2 with mainnet and Base Sepolia testnet. Use official RPCs from trusted node providers. Typical chain IDs: Base mainnet (8453), Base Sepolia (84532). Prefer HTTPS RPCs behind TLS, pin to provider domains, and handle occasional reorgs. For clients (e.g., Viem), configure the chain and transport explicitly; avoid relying on window-injected providers in server contexts.
@@ -109,7 +109,7 @@ const client = createPublicClient({ chain: base, transport: http() })
- [Resources for AI agents](https://docs.base.org/get-started/resources-for-ai-agents): Base-first resources for AI agents, including docs indexes, MCP access, skills, and recommended starting points
## Base Chain
-- [Flashblocks Overview](https://docs.base.org/base-chain/flashblocks/overview): Understand the sequencer architecture, block building algorithm, and integration options for Flashblocks on Base.
+- [Chain Overview](https://docs.base.org/base-chain/overview): Start here for Base Chain docs, including concepts, network reference, node operation, APIs, and protocol specifications.
- [Overview](https://docs.base.org/base-chain/specs/overview): Technical specification of the Base Chain protocol, covering block derivation, execution, transaction propagation, and state verification.
- [Specification](https://docs.base.org/base-chain/specs/protocol/consensus/index): Specification of the Base rollup node, describing its components and role in L2 block derivation and consensus.
- [L2 Execution Engine](https://docs.base.org/base-chain/specs/protocol/execution/index): Specification of the L2 execution engine, detailing EIP-1559 parameters, fee vaults, Engine API usage, and execution layer behavior.
@@ -162,27 +162,24 @@ const client = createPublicClient({ chain: base, transport: http() })
- [newFlashblockTransactions](https://docs.base.org/base-chain/api-reference/flashblocks-api/newFlashblockTransactions): Subscribe to receive each transaction as it is pre-confirmed into a Flashblock. Only available on Flashblocks WebSocket endpoints.
- [pendingLogs](https://docs.base.org/base-chain/api-reference/flashblocks-api/pendingLogs): Subscribe to logs from pre-confirmed transactions matching an optional filter. Only available on Flashblocks WebSocket endpoints.
- [Base RPC Overview](https://docs.base.org/base-chain/api-reference/rpc-overview): Complete reference for all JSON-RPC and Flashblocks methods available on Base nodes.
-- [App Integration](https://docs.base.org/base-chain/flashblocks/app-integration): Integrate Flashblocks into your app for 200ms transaction confirmations using RPC APIs and popular libraries like Ethers, Wagmi and Viem.
-- [Flashblocks Architecture](https://docs.base.org/base-chain/flashblocks/architecture): Understand the sequencer architecture and infrastructure components that power Flashblocks on Base.
-- [Flashblocks FAQ](https://docs.base.org/base-chain/flashblocks/faq): Frequently asked questions about Flashblocks, including block building, WebSocket data, RPC usage, and node setup.
+- [Flashblocks Reference](https://docs.base.org/base-chain/flashblocks/faq): Reference for Flashblocks on Base — key concepts, architecture, and frequently asked questions about block building, WebSocket data, RPC usage, and node setup.
- [Contract Addresses](https://docs.base.org/base-chain/network-information/base-contracts): A comprehensive list of contract addresses for Base Mainnet and Base Testnet, including links to their respective blockchain explorers.
-- [Block Building](https://docs.base.org/base-chain/network-information/block-building): This page outlines how Base blocks are built.
-- [Bridges](https://docs.base.org/base-chain/network-information/bridges): Documentation for bridging assets to Base. This page covers how to bridge assets between Ethereum, Solana, Bitcoin, and Base.
+- [Base-Solana Bridge](https://docs.base.org/base-chain/network-information/base-solana-bridge): Bridge tokens and messages between Base and Solana Mainnet
+- [Bridging and Withdrawals](https://docs.base.org/base-chain/network-information/bridging-and-withdrawals): How deposits and withdrawals work on Base, including the standard withdrawal flow and faster bridge options.
- [Configuration Changelog](https://docs.base.org/base-chain/network-information/configuration-changelog): A log of configuration changes to the Base networks.
-- [Differences between Ethereum and Base](https://docs.base.org/base-chain/network-information/diffs-ethereum-base)
+- [Ecosystem Bridges](https://docs.base.org/base-chain/network-information/ecosystem-bridges): Available bridge providers and routes for moving assets to and from Base.
- [Network Faucets](https://docs.base.org/base-chain/network-information/network-faucets): Documentation for Testnet Faucets on the Base network.
- [Network Fees](https://docs.base.org/base-chain/network-information/network-fees): Documentation about network fees on Base. This page covers details of the two-component cost system involving L2 execution fees and L1 security fees, and offers insights on fee variations and cost-saving strategies.
+- [Throughput and Limits](https://docs.base.org/base-chain/network-information/throughput-and-limits): Gas limits and throughput-related network parameters on Base.
- [Transaction Finality](https://docs.base.org/base-chain/network-information/transaction-finality): Detailed information about transaction finality on Base.
+- [Transaction Ordering](https://docs.base.org/base-chain/network-information/transaction-ordering): This page outlines how Base transactions are ordered.
- [Troubleshooting Transactions](https://docs.base.org/base-chain/network-information/troubleshooting-transactions): Guide to diagnosing and resolving transaction issues on Base.
- [Node Providers](https://docs.base.org/base-chain/node-operators/node-providers): Documentation for Node Providers for the Base network. Including details on their services, supported networks, and pricing plans.
- [Node Performance](https://docs.base.org/base-chain/node-operators/performance-tuning): Hardware specifications, storage requirements, client recommendations, and configuration settings for running a performant Base node.
- [Run a Node](https://docs.base.org/base-chain/node-operators/run-a-base-node): A tutorial that teaches how to set up and run a Base Node.
- [Node Snapshots](https://docs.base.org/base-chain/node-operators/snapshots): Download and restore Base node snapshots to significantly reduce initial sync time for both archive and pruned nodes.
- [Node Troubleshooting](https://docs.base.org/base-chain/node-operators/troubleshooting): Solutions to common issues when setting up and running a Base node, covering sync problems, networking, snapshots, and performance.
-- [Base-Solana Bridge](https://docs.base.org/base-chain/quickstart/base-solana-bridge): Bridge tokens and messages between Base and Solana Mainnet
-- [Connecting to Base](https://docs.base.org/base-chain/quickstart/connecting-to-base): Documentation about Base Mainnet and Base Testnet. This page covers network information for the Base network, including network names, descriptions, RPC endpoints, chain IDs, currency symbols, and block explorers.
-- [Deploy on Base](https://docs.base.org/base-chain/quickstart/deploy-on-base)
-- [Why Base?](https://docs.base.org/base-chain/quickstart/why-base)
+- [Connecting to Base](https://docs.base.org/base-chain/quickstart/connecting-to-base): Network details and wallet setup for Base Mainnet, Base Testnet (Sepolia), and Base Vibenet.
- [How to avoid getting your app flagged as malicious](https://docs.base.org/base-chain/security/avoid-malicious-flags): The Base bug bounty program and procedures for reporting vulnerabilities.
- [Bug Bounty](https://docs.base.org/base-chain/security/bug-bounty)
- [Reporting Vulnerabilities](https://docs.base.org/base-chain/security/report-vulnerability): The Base procedures for reporting vulnerabilities.
@@ -372,6 +369,7 @@ const client = createPublicClient({ chain: base, transport: http() })
- [Accept B20 payments](https://docs.base.org/apps/guides/accept-b20-payments): Accept B20 token payments in your app and match each transaction to an order with onchain memos.
- [Migrate to a Standard Web App](https://docs.base.org/apps/guides/migrate-to-standard-web-app): Migrate your Farcaster mini-app to work in the Base App. Covers replacing deprecated SDK methods, and registering on Base.dev.
- [Build an app on Base](https://docs.base.org/apps/quickstart/build-app): A step-by-step guide to building a Next.js tally app on Base using wagmi and viem, with wallet connection, contract reads and writes, and batch transaction support.
+- [Deploy on Base](https://docs.base.org/apps/quickstart/deploy-on-base): Deploy a smart contract to Base Sepolia with Foundry.
- [Add notifications](https://docs.base.org/apps/technical-guides/base-notifications): Send in-app notifications to your app's users through the Base Dashboard REST API.
## Agents
diff --git a/docs/llms.txt b/docs/llms.txt
index ec324f4ee..b1fd97cdf 100644
--- a/docs/llms.txt
+++ b/docs/llms.txt
@@ -21,7 +21,7 @@
- [Resources for AI agents](https://docs.base.org/get-started/resources-for-ai-agents): Base-first resources for AI agents, including docs indexes, MCP access, skills, and recommended starting points
## Base Chain
-- [Flashblocks Overview](https://docs.base.org/base-chain/flashblocks/overview): Understand the sequencer architecture, block building algorithm, and integration options for Flashblocks on Base.
+- [Chain Overview](https://docs.base.org/base-chain/overview): Start here for Base Chain docs, including concepts, network reference, node operation, APIs, and protocol specifications.
- [Overview](https://docs.base.org/base-chain/specs/overview): Technical specification of the Base Chain protocol, covering block derivation, execution, transaction propagation, and state verification.
- [Specification](https://docs.base.org/base-chain/specs/protocol/consensus/index): Specification of the Base rollup node, describing its components and role in L2 block derivation and consensus.
- [L2 Execution Engine](https://docs.base.org/base-chain/specs/protocol/execution/index): Specification of the L2 execution engine, detailing EIP-1559 parameters, fee vaults, Engine API usage, and execution layer behavior.
@@ -74,27 +74,24 @@
- [newFlashblockTransactions](https://docs.base.org/base-chain/api-reference/flashblocks-api/newFlashblockTransactions): Subscribe to receive each transaction as it is pre-confirmed into a Flashblock. Only available on Flashblocks WebSocket endpoints.
- [pendingLogs](https://docs.base.org/base-chain/api-reference/flashblocks-api/pendingLogs): Subscribe to logs from pre-confirmed transactions matching an optional filter. Only available on Flashblocks WebSocket endpoints.
- [Base RPC Overview](https://docs.base.org/base-chain/api-reference/rpc-overview): Complete reference for all JSON-RPC and Flashblocks methods available on Base nodes.
-- [App Integration](https://docs.base.org/base-chain/flashblocks/app-integration): Integrate Flashblocks into your app for 200ms transaction confirmations using RPC APIs and popular libraries like Ethers, Wagmi and Viem.
-- [Flashblocks Architecture](https://docs.base.org/base-chain/flashblocks/architecture): Understand the sequencer architecture and infrastructure components that power Flashblocks on Base.
-- [Flashblocks FAQ](https://docs.base.org/base-chain/flashblocks/faq): Frequently asked questions about Flashblocks, including block building, WebSocket data, RPC usage, and node setup.
+- [Flashblocks Reference](https://docs.base.org/base-chain/flashblocks/faq): Reference for Flashblocks on Base — key concepts, architecture, and frequently asked questions about block building, WebSocket data, RPC usage, and node setup.
- [Contract Addresses](https://docs.base.org/base-chain/network-information/base-contracts): A comprehensive list of contract addresses for Base Mainnet and Base Testnet, including links to their respective blockchain explorers.
-- [Block Building](https://docs.base.org/base-chain/network-information/block-building): This page outlines how Base blocks are built.
-- [Bridges](https://docs.base.org/base-chain/network-information/bridges): Documentation for bridging assets to Base. This page covers how to bridge assets between Ethereum, Solana, Bitcoin, and Base.
+- [Base-Solana Bridge](https://docs.base.org/base-chain/network-information/base-solana-bridge): Bridge tokens and messages between Base and Solana Mainnet
+- [Bridging and Withdrawals](https://docs.base.org/base-chain/network-information/bridging-and-withdrawals): How deposits and withdrawals work on Base, including the standard withdrawal flow and faster bridge options.
- [Configuration Changelog](https://docs.base.org/base-chain/network-information/configuration-changelog): A log of configuration changes to the Base networks.
-- [Differences between Ethereum and Base](https://docs.base.org/base-chain/network-information/diffs-ethereum-base)
+- [Ecosystem Bridges](https://docs.base.org/base-chain/network-information/ecosystem-bridges): Available bridge providers and routes for moving assets to and from Base.
- [Network Faucets](https://docs.base.org/base-chain/network-information/network-faucets): Documentation for Testnet Faucets on the Base network.
- [Network Fees](https://docs.base.org/base-chain/network-information/network-fees): Documentation about network fees on Base. This page covers details of the two-component cost system involving L2 execution fees and L1 security fees, and offers insights on fee variations and cost-saving strategies.
+- [Throughput and Limits](https://docs.base.org/base-chain/network-information/throughput-and-limits): Gas limits and throughput-related network parameters on Base.
- [Transaction Finality](https://docs.base.org/base-chain/network-information/transaction-finality): Detailed information about transaction finality on Base.
+- [Transaction Ordering](https://docs.base.org/base-chain/network-information/transaction-ordering): This page outlines how Base transactions are ordered.
- [Troubleshooting Transactions](https://docs.base.org/base-chain/network-information/troubleshooting-transactions): Guide to diagnosing and resolving transaction issues on Base.
- [Node Providers](https://docs.base.org/base-chain/node-operators/node-providers): Documentation for Node Providers for the Base network. Including details on their services, supported networks, and pricing plans.
- [Node Performance](https://docs.base.org/base-chain/node-operators/performance-tuning): Hardware specifications, storage requirements, client recommendations, and configuration settings for running a performant Base node.
- [Run a Node](https://docs.base.org/base-chain/node-operators/run-a-base-node): A tutorial that teaches how to set up and run a Base Node.
- [Node Snapshots](https://docs.base.org/base-chain/node-operators/snapshots): Download and restore Base node snapshots to significantly reduce initial sync time for both archive and pruned nodes.
- [Node Troubleshooting](https://docs.base.org/base-chain/node-operators/troubleshooting): Solutions to common issues when setting up and running a Base node, covering sync problems, networking, snapshots, and performance.
-- [Base-Solana Bridge](https://docs.base.org/base-chain/quickstart/base-solana-bridge): Bridge tokens and messages between Base and Solana Mainnet
-- [Connecting to Base](https://docs.base.org/base-chain/quickstart/connecting-to-base): Documentation about Base Mainnet and Base Testnet. This page covers network information for the Base network, including network names, descriptions, RPC endpoints, chain IDs, currency symbols, and block explorers.
-- [Deploy on Base](https://docs.base.org/base-chain/quickstart/deploy-on-base)
-- [Why Base?](https://docs.base.org/base-chain/quickstart/why-base)
+- [Connecting to Base](https://docs.base.org/base-chain/quickstart/connecting-to-base): Network details and wallet setup for Base Mainnet, Base Testnet (Sepolia), and Base Vibenet.
- [How to avoid getting your app flagged as malicious](https://docs.base.org/base-chain/security/avoid-malicious-flags): The Base bug bounty program and procedures for reporting vulnerabilities.
- [Bug Bounty](https://docs.base.org/base-chain/security/bug-bounty)
- [Reporting Vulnerabilities](https://docs.base.org/base-chain/security/report-vulnerability): The Base procedures for reporting vulnerabilities.
@@ -284,6 +281,7 @@
- [Accept B20 payments](https://docs.base.org/apps/guides/accept-b20-payments): Accept B20 token payments in your app and match each transaction to an order with onchain memos.
- [Migrate to a Standard Web App](https://docs.base.org/apps/guides/migrate-to-standard-web-app): Migrate your Farcaster mini-app to work in the Base App. Covers replacing deprecated SDK methods, and registering on Base.dev.
- [Build an app on Base](https://docs.base.org/apps/quickstart/build-app): A step-by-step guide to building a Next.js tally app on Base using wagmi and viem, with wallet connection, contract reads and writes, and batch transaction support.
+- [Deploy on Base](https://docs.base.org/apps/quickstart/deploy-on-base): Deploy a smart contract to Base Sepolia with Foundry.
- [Add notifications](https://docs.base.org/apps/technical-guides/base-notifications): Send in-app notifications to your app's users through the Base Dashboard REST API.
## Agents
diff --git a/docs/style.css b/docs/style.css
index dd22f016d..37fef9e11 100644
--- a/docs/style.css
+++ b/docs/style.css
@@ -45,6 +45,15 @@
height: 1.25rem;
}
+#navbar a[href="https://github.com/base"],
+#navbar a[href="https://discord.com/invite/buildonbase"],
+#navbar a[href="https://dashboard.base.org/"],
+#navbar a[href="https://dashboard.base.org"],
+#navbar a[href="https://dashboard.base.org/"] > span.absolute,
+#navbar a[href="https://dashboard.base.org"] > span.absolute {
+ border-radius: 1rem !important;
+}
+
.homepage_wrapper {
width: 75%;
max-width: 1376px;