# BaseHub

> BaseHub — reference for agents on Base. Every page is reachable as raw Markdown by appending .md to the URL.

BaseHub is the reference for agents on Base. Every page below is available as raw Markdown by appending `.md` to the URL (e.g. `/introduction/why-base.md`). The full corpus is at `/llms-full.txt`, a JSON index of all pages is at `/api/pages.json`, the MCP server is published at `https://www.npmjs.com/package/@wbnns/base-mcp`, and live activity feeds are mirrored at `/feeds/blog.xml` (Base engineering blog) and `/feeds/status.xml` (Base statuspage).

## Introduction

- [Base-Solana Bridge](https://basehub.org/introduction/base-solana-bridge/): Bridge tokens and arbitrary messages between Base and Solana with the official Base-Solana bridge contracts and programs.
- [Connecting to Base](https://basehub.org/introduction/connecting-to-base/): Network parameters, RPC endpoints, and wallet setup for connecting to Base Mainnet and Base Sepolia testnet.
- [Deploy on Base](https://basehub.org/introduction/deploy-on-base/): Set up Foundry, configure RPC and key management, and deploy a smart contract to Base Sepolia in a single workflow.
- [Why Base](https://basehub.org/introduction/why-base/): Base delivers sub-cent, sub-second transactions on a global, permissionless platform with developer tooling, grants, and built-in distribution.

## Network

- [Block Building](https://basehub.org/network/block-building/): How Base orders transactions inside blocks, including Flashblocks 200ms preconfirmations and the per-transaction gas cap enforced by the mempool.
- [Bridges](https://basehub.org/network/bridges/): Third-party bridges for moving assets between Base and Ethereum, Solana, or Bitcoin, plus contract addresses for the Base-Solana bridge.
- [Bridging and Withdrawals](https://basehub.org/network/bridging-and-withdrawals/): How deposits into Base and standard withdrawals back to Ethereum work, why withdrawals take seven days, and the faster bridge options available.
- [Configuration Changelog](https://basehub.org/network/configuration-changelog/): A dated log of block-building, fee, and other network parameter changes for Base Mainnet and Base Sepolia.
- [Contract Addresses](https://basehub.org/network/base-contracts/): Canonical L1 and L2 contract and admin addresses for Base Mainnet and Base Sepolia, with explorer links and notes on unused OP Stack contracts.
- [Differences Between Ethereum and Base](https://basehub.org/network/diffs-ethereum-base/): Short reference to the protocol-level differences developers encounter when moving apps from Ethereum to Base.
- [Ecosystem Contracts](https://basehub.org/network/ecosystem-contracts/): Deployed addresses for Multicall3, Uniswap v2, and Uniswap v3 on Base Mainnet and Base Sepolia, with block explorer links.
- [Network Faucets](https://basehub.org/network/network-faucets/): Testnet ETH faucets for Base Sepolia from Coinbase Developer Platform, Alchemy, QuickNode, Chainstack, and other providers.
- [Network Fees](https://basehub.org/network/network-fees/): How Base fees are split between L2 execution and L1 data, plus the minimum base fee, EIP-1559 parameters, and the GasPriceOracle.
- [Network Incident History](https://basehub.org/network/incident-history/): Paraphrased log of Base mainnet and Sepolia incidents and scheduled network events.
- [Throughput and Limits](https://basehub.org/network/throughput-and-limits/): Gas limits, Flashblock performance figures, fee parameters, data availability throttling, and endpoint limits that shape practical throughput on Base.
- [Transaction Finality](https://basehub.org/network/transaction-finality/): The four finality stages for Base L2 transactions and the 7-day window that applies only to withdrawals back to Ethereum.
- [Troubleshooting Transactions](https://basehub.org/network/troubleshooting-transactions/): Diagnose pending, rejected, failed, or slow Base transactions, with fixes for fee, nonce, gas, and Flashblocks issues.

## Flashblocks

- [App Integration](https://basehub.org/flashblocks/app-integration/): Integrate Flashblocks for 200ms confirmations using the pending RPC tag with Wagmi, Viem, Ethers, and Flashblocks-aware node providers.
- [Flashblocks Architecture](https://basehub.org/flashblocks/architecture/): Sequencer topology and infrastructure components — rollup-boost, base-builder, websocket-proxy, and base — that power Flashblocks on Base.
- [Flashblocks FAQ](https://basehub.org/flashblocks/faq/): Answers to common questions about Flashblocks block building, WebSocket data, RPC behavior, and node setup on Base.
- [Flashblocks Overview](https://basehub.org/flashblocks/overview/): Flashblocks deliver 200ms preconfirmed sub-blocks on Base, streaming state updates 10x faster than the standard 2-second block cadence.

## API Reference

- [base_transactionStatus](https://basehub.org/api-reference/flashblocks/base_transactionstatus/): Reports whether a transaction hash is present in the node mempool, useful for confirming submission before pre-confirmation lands.
- [debug_traceBlockByHash](https://basehub.org/api-reference/debug/debug_traceblockbyhash/): Replays every transaction in a block identified by hash and returns an EVM execution trace for each one.
- [debug_traceBlockByNumber](https://basehub.org/api-reference/debug/debug_traceblockbynumber/): Returns EVM execution traces for every transaction in a block identified by its block number or block tag.
- [debug_traceTransaction](https://basehub.org/api-reference/debug/debug_tracetransaction/): Replays a transaction and returns its full EVM execution trace, with opcode-level gas, stack, memory, and storage detail.
- [eth_blockNumber](https://basehub.org/api-reference/eth/eth_blocknumber/): Returns the latest block number on Base — the most recent block the node has imported, encoded as a hexadecimal string.
- [eth_call](https://basehub.org/api-reference/eth/eth_call/): Executes a read-only message call against Base state without broadcasting a transaction; pair with pending on Flashblocks for pre-confirmed reads.
- [eth_chainId](https://basehub.org/api-reference/eth/eth_chainid/): Returns the EIP-695 chain ID for the connected Base network — 0x2105 for Mainnet and 0x14a34 for Sepolia.
- [eth_estimateGas](https://basehub.org/api-reference/eth/eth_estimategas/): Estimates the gas required to execute a transaction on Base; use pending on Flashblocks to estimate against pre-confirmed state.
- [eth_feeHistory](https://basehub.org/api-reference/eth/eth_feehistory/): Returns historical base fees, gas-used ratios, and priority-fee percentile rewards across a range of Base blocks for fee estimation.
- [eth_gasPrice](https://basehub.org/api-reference/eth/eth_gasprice/): Returns the current gas price on Base in wei as a hexadecimal string; for EIP-1559 fee estimation use eth_maxPriorityFeePerGas and eth_feeHistory.
- [eth_getBalance](https://basehub.org/api-reference/eth/eth_getbalance/): Returns the ETH balance of an account at a given block on Base; use pending on Flashblocks for ~200ms pre-confirmed balances.
- [eth_getBlockByHash](https://basehub.org/api-reference/eth/eth_getblockbyhash/): Returns block information for a given 32-byte block hash on Base, with full transaction objects or just transaction hashes.
- [eth_getBlockByNumber](https://basehub.org/api-reference/eth/eth_getblockbynumber/): Returns block data by number on Base; the pending tag returns the live pre-confirmed block updated every ~200ms.
- [eth_getBlockReceipts](https://basehub.org/api-reference/eth/eth_getblockreceipts/): Returns every transaction receipt for a block on Base in one call; pair with pending on Flashblocks for pre-confirmed receipts.
- [eth_getBlockTransactionCountByHash](https://basehub.org/api-reference/eth/eth_getblocktransactioncountbyhash/): Returns the number of transactions included in the Base block matching the supplied 32-byte block hash.
- [eth_getBlockTransactionCountByNumber](https://basehub.org/api-reference/eth/eth_getblocktransactioncountbynumber/): Returns the transaction count for a Base block by number; the pending tag counts pre-confirmed transactions in the live Flashblock.
- [eth_getCode](https://basehub.org/api-reference/eth/eth_getcode/): Returns the deployed bytecode at an address on Base; use pending on Flashblocks to detect newly deployed contracts before block finalization.
- [eth_getLogs](https://basehub.org/api-reference/eth/eth_getlogs/): Returns event logs on Base matching a filter object; pair with pending on Flashblocks to query logs from pre-confirmed transactions.
- [eth_getStorageAt](https://basehub.org/api-reference/eth/eth_getstorageat/): Returns the 32-byte value stored at a contract storage slot on Base; use pending on Flashblocks for pre-confirmed storage reads.
- [eth_getTransactionByBlockHashAndIndex](https://basehub.org/api-reference/eth/eth_gettransactionbyblockhashandindex/): Returns transaction data on Base by combining a 32-byte block hash with the transaction's zero-based index inside that block.
- [eth_getTransactionByBlockNumberAndIndex](https://basehub.org/api-reference/eth/eth_gettransactionbyblocknumberandindex/): Returns transaction data on Base by pairing a block number or tag with the transaction's zero-based index inside that block.
- [eth_getTransactionByHash](https://basehub.org/api-reference/eth/eth_gettransactionbyhash/): Returns full transaction data for a 32-byte transaction hash on Base, or null when the node has not seen the transaction.
- [eth_getTransactionCount](https://basehub.org/api-reference/eth/eth_gettransactioncount/): Returns the transaction count (nonce) for an address. Use the pending tag to include pre-confirmed transactions.
- [eth_getTransactionReceipt](https://basehub.org/api-reference/eth/eth_gettransactionreceipt/): Returns the receipt for a mined transaction by hash, or null when the transaction is still pending or has not been included in a block.
- [eth_maxPriorityFeePerGas](https://basehub.org/api-reference/eth/eth_maxpriorityfeepergas/): Returns the suggested EIP-1559 priority fee (tip) per gas to pay the sequencer on top of the base fee.
- [eth_sendRawTransaction](https://basehub.org/api-reference/eth/eth_sendrawtransaction/): Submits a pre-signed RLP-encoded transaction to the network. Submit to a Flashblocks preconf endpoint for ~200ms pre-confirmation.
- [eth_simulateV1](https://basehub.org/api-reference/flashblocks/eth_simulatev1/): Simulates one or more transaction bundles against the current pre-confirmed Flashblock state, with state overrides and optional transfer tracing.
- [eth_subscribe](https://basehub.org/api-reference/eth/eth_subscribe/): Opens a real-time WebSocket subscription for new blocks, logs, and pending transactions over a node-provider WebSocket endpoint.
- [eth_syncing](https://basehub.org/api-reference/eth/eth_syncing/): Returns the sync status of the node. Returns false when the node is fully synced, otherwise an object describing sync progress.
- [eth_unsubscribe](https://basehub.org/api-reference/eth/eth_unsubscribe/): Cancels an active WebSocket subscription created with eth_subscribe and invalidates the subscription ID.
- [Flashblocks API overview](https://basehub.org/api-reference/flashblocks/overview/): Flashblocks-specific RPC methods, WebSocket subscriptions, and the infrastructure stream schema for Base pre-confirmations.
- [net_version](https://basehub.org/api-reference/eth/net_version/): Returns the current network ID as a decimal string. Base Mainnet is 8453 and Base Sepolia is 84532.
- [newFlashblocks](https://basehub.org/api-reference/flashblocks/newflashblocks/): Subscribe to the full Flashblock payload stream and receive each pre-confirmed block delta as the sequencer builds it, every ~200ms.
- [newFlashblockTransactions](https://basehub.org/api-reference/flashblocks/newflashblocktransactions/): Subscribe to receive each transaction the sequencer pre-confirms into a Flashblock, optionally with full transaction and log data.
- [pendingLogs](https://basehub.org/api-reference/flashblocks/pendinglogs/): Subscribe to logs from pre-confirmed transactions matching an optional address and topics filter, with sub-block latency over a WebSocket connection.
- [Rollup node RPC](https://basehub.org/api-reference/rollup-node-rpc/): Reference for the Base rollup node's optimism_outputAtBlock method, which returns the L2 output root and sync metadata for a given block, along with the supporting BlockID, L1BlockRef, L2BlockRef, and SyncStatus structures.
- [RPC overview](https://basehub.org/api-reference/rpc-overview/): Full reference for the JSON-RPC and Flashblocks methods exposed by Base nodes across the eth, net, web3, debug, txpool, and base namespaces.
- [web3_clientVersion](https://basehub.org/api-reference/eth/web3_clientversion/): Returns the version string identifying the underlying node client software running the JSON-RPC endpoint.

## Integration Guides

- [Connecting to Base](https://basehub.org/integration-guides/connecting/): Connect to Base mainnet or Sepolia using public endpoints, your own node, or a third-party provider.
- [Flashblocks RPC](https://basehub.org/integration-guides/flashblocks-rpc/): Read preconfirmed Base state and stream sub-block updates over JSON-RPC and WebSocket.
- [Metering RPC](https://basehub.org/integration-guides/metering-rpc/): Simulate transactions to return gas estimates, resource breakdowns, and builder metering metadata.
- [Transaction Pool](https://basehub.org/integration-guides/txpool/): Inspect and monitor the Base txpool through RPC extensions and tracing instrumentation.

## Run a Node

- [Building from Source](https://basehub.org/getting-started/building/): Clone the base/base repository and compile binaries with Just recipes or Cargo.
- [Development Workflow](https://basehub.org/getting-started/development/): Run the check, test, fix, and CI Just recipes used day-to-day on base/base.
- [Docker Builds](https://basehub.org/getting-started/docker/): Build and run base/base from the Dockerfiles under etc/docker without installing Rust on the host.
- [Local Devnet](https://basehub.org/getting-started/devnet/): Start a Docker Compose devnet for integration testing, debugging, and flashblocks experiments.
- [Prerequisites](https://basehub.org/getting-started/prerequisites/): Install Rust, Just, Foundry, build essentials, and optionally Docker before working on base/base.
- [Running the Node](https://basehub.org/getting-started/running/): Start the base-reth-node binary, configure RPC and metrics, and shut down cleanly.

## Node Operations

- [Adding a New Network Upgrade](https://basehub.org/node-operations/upgrades/): Every code change required to land a new Base network upgrade — config, traits, RollupConfig methods, EVM spec resolution, and precompile routing.
- [Azul Node Upgrade Guide](https://basehub.org/node-operations/azul-node-upgrade/): Migrate a Base node to base-reth-node and base-consensus for the Azul hardfork, including the op-node to base-consensus environment variable mapping.
- [Base Azul Upgrade](https://basehub.org/node-operations/base-v1-upgrade/): Migrate Base nodes to base-reth-node and base-consensus ahead of the Azul network upgrade, with environment variable mappings and timelines.
- [basectl](https://basehub.org/node-operations/basectl/): Configure and inspect Base nodes across mainnet, sepolia, devnet, and custom configs.
- [Configuration Reference](https://basehub.org/node-operations/configuration/): CLI flags, environment variables, and Cargo build profiles for base-reth-node.
- [Deployment](https://basehub.org/node-operations/deployment/): Run base-reth-node in production via the official Docker image or a custom source build.
- [Docker Operations](https://basehub.org/node-operations/docker/): Build and run base-reth-node, the builder, and the websocket proxy with Docker.
- [Monitoring](https://basehub.org/node-operations/monitoring/): Prometheus metrics, devnet status commands, log streaming, and profiling for base-reth-node.
- [Node Providers](https://basehub.org/node-operations/node-providers/): Hosted RPC providers for Base Mainnet and Base Sepolia, including Coinbase Developer Platform, Alchemy, QuickNode, and others.
- [Node Troubleshooting](https://basehub.org/node-operations/troubleshooting/): Diagnose setup, sync, performance, snapshot, and networking issues for Base nodes running the official Docker setup.
- [Performance Tuning](https://basehub.org/node-operations/performance-tuning/): Hardware, storage, and client recommendations for high-performance Base nodes, including production configurations and sync guidance.
- [Release Process](https://basehub.org/node-operations/release-process/): How base/base releases are produced — Start Release, automatic RC builds on push, and Publish Release for the final tag.
- [Releases](https://basehub.org/node-operations/releases/): Versioning, the pinned Reth tag, production image registry, and the GitHub Actions release flow.
- [Snapshots](https://basehub.org/node-operations/snapshots/): Restore Base nodes from official Reth and proofs snapshots for Base Mainnet and Base Sepolia to skip the initial sync window.

## Architecture

- [Architecture Overview](https://basehub.org/architecture/overview/): How the 8 crate groups in base/base fit together — from Reth integration to Flashblocks production.
- [Crate Dependency Graph](https://basehub.org/architecture/crate-graph/): Visual map of workspace dependencies across the 8 crate groups in base/base.
- [Engineering Blog Index](https://basehub.org/architecture/engineering-blog/): Running paraphrased index of architecture-relevant posts from the Base engineering blog.
- [Execution Pipeline](https://basehub.org/architecture/execution-pipeline/): Transaction flow from RPC receipt through the transaction pool, payload building, EVM execution, state trie update, and block production.
- [Flashblocks Pipeline](https://basehub.org/architecture/flashblocks-pipeline/): How the builder produces flashblocks at 200ms sub-block intervals, streams them over WebSockets, and reconciles state at block boundaries.
- [June 2026 Block Production Outage](https://basehub.org/architecture/june-2026-block-production-outage/): Postmortem of the two June 2026 Base mainnet block production halts caused by stale EVM journal state in the sequencer, plus the mitigation and follow-up work.
- [Multiproofs on Base](https://basehub.org/architecture/multiproofs/): How Base's multiproof system combines TEE and ZK provers to enable fast finality, satisfy Stage 2 decentralization requirements, and strengthen the proof system's security posture.
- [Protocol Overview](https://basehub.org/architecture/protocol-overview/): A tour of the Base rollup protocol — the network participants, the consensus, execution, bridging, batcher, and proof components, and the deposit, transaction, and withdrawal flows that connect L1 and L2.

## Crate Reference

- [alloy](https://basehub.org/crates/alloy/overview/): Alloy type extensions for Base — consensus types, EVM customizations, RPC types, and network definitions.
- [alloy/consensus](https://basehub.org/crates/alloy/consensus/): Base alloy consensus types — transactions, receipts with Base-specific fields.
- [alloy/evm](https://basehub.org/crates/alloy/evm/): EVM implementation with Base hardfork awareness.
- [alloy/hardforks](https://basehub.org/crates/alloy/hardforks/): Named bindings for Base-specific hardforks.
- [alloy/network](https://basehub.org/crates/alloy/network/): Base blockchain RPC behavior abstraction at the network layer.
- [alloy/provider](https://basehub.org/crates/alloy/provider/): Interface with a Base blockchain via the Engine API provider.
- [alloy/rpc-jsonrpsee](https://basehub.org/crates/alloy/rpc-jsonrpsee/): Base RPC client using the jsonrpsee framework.
- [alloy/rpc-types](https://basehub.org/crates/alloy/rpc-types/): Base RPC types for blocks and transactions.
- [alloy/rpc-types-engine](https://basehub.org/crates/alloy/rpc-types-engine/): Base RPC types for the engine namespace — SSZ, snappy, and sha2 hashing.
- [builder](https://basehub.org/crates/builder/overview/): Block building, flashblock production, metering, and block publishing for Base.
- [builder/core](https://basehub.org/crates/builder/core/): Core block builder for the OP Stack — the main builder logic for sequencing and flashblock production.
- [builder/metering](https://basehub.org/crates/builder/metering/): Resource metering backend for the OP Stack block builder.
- [builder/publish](https://basehub.org/crates/builder/publish/): WebSocket broadcast publisher for flashblock distribution.
- [client](https://basehub.org/crates/client/overview/): Node client — CLI, engine, flashblocks integration, metering, proofs, and transaction pool tracing.
- [client/cli](https://basehub.org/crates/client/cli/): CLI argument types for Base node consensus clients.
- [client/engine](https://basehub.org/crates/client/engine/): Engine validator for the Base Node — handles Engine API, trie computation, and flashblocks.
- [client/flashblocks](https://basehub.org/crates/client/flashblocks/): Flashblocks state management — WebSocket streaming, pending state, EVM re-execution.
- [client/flashblocks-node](https://basehub.org/crates/client/flashblocks-node/): Flashblocks node extension — integrates flashblocks into the node lifecycle.
- [client/metering](https://basehub.org/crates/client/metering/): Metering RPC for the Base node — resource and gas metering per block.
- [client/proofs](https://basehub.org/crates/client/proofs/): Proofs extension for the Base node — fault proof data via Execution Extensions.
- [client/txpool-tracing](https://basehub.org/crates/client/txpool-tracing/): Transaction tracing extensions — LRU caching, metrics, and streaming.
- [consensus](https://basehub.org/crates/consensus/overview/): OP Stack consensus implementation — derivation pipeline, gossip networking, P2P discovery, and sequencing.
- [consensus/cli](https://basehub.org/crates/consensus/cli/): Shared CLI utilities for Kona crates — tracing, metrics, and clap argument parsing.
- [consensus/derive](https://basehub.org/crates/consensus/derive/): A `no_std` derivation pipeline implementation for the OP Stack. Derives L2 blocks from L1 data.
- [consensus/disc](https://basehub.org/crates/consensus/disc/): Discovery service for the OP Stack using discv5 and libp2p.
- [consensus/engine](https://basehub.org/crates/consensus/engine/): OP Stack engine client implementation — makes Engine API calls to the execution layer.
- [consensus/genesis](https://basehub.org/crates/consensus/genesis/): Optimism genesis types including rollup config, system config, and hardfork definitions.
- [consensus/gossip](https://basehub.org/crates/consensus/gossip/): Gossip protocol implementation for the OP Stack using libp2p gossipsub.
- [consensus/hardforks](https://basehub.org/crates/consensus/hardforks/): Consensus hardfork type definitions for the OP Stack.
- [consensus/macros](https://basehub.org/crates/consensus/macros/): Utility procedural macros for kona crates.
- [consensus/peers](https://basehub.org/crates/consensus/peers/): Network peers library for the OP Stack — peer management, discv5, and libp2p integration.
- [consensus/protocol](https://basehub.org/crates/consensus/protocol/): Base-specific protocol types — batches, channels, frames, and compression (brotli, zlib).
- [consensus/providers-alloy](https://basehub.org/crates/consensus/providers-alloy/): Alloy-backed data providers for L1/L2 data including beacon, execution, and blob fetching with c-kzg.
- [consensus/registry](https://basehub.org/crates/consensus/registry/): Registry of superchain configurations — chain configs loaded from TOML.
- [consensus/rpc](https://basehub.org/crates/consensus/rpc/): RPC types and client for Base consensus using jsonrpsee.
- [consensus/service](https://basehub.org/crates/consensus/service/): OP Stack consensus node service — orchestrates derivation, gossip, discovery, and engine communication.
- [consensus/sources](https://basehub.org/crates/consensus/sources/): Data source types and utilities for the consensus node including remote signer and transport abstractions.
- [Crate Reference](https://basehub.org/crates/overview/): The 8 top-level crate groups that make up the base/base Cargo workspace.
- [execution](https://basehub.org/crates/execution/overview/): Execution layer crates covering the EVM, chain spec, payload building, storage, transaction pool, and state.
- [execution/chainspec](https://basehub.org/crates/execution/chainspec/): Defines OP chain parameters, genesis state, and hardfork activation for the Base execution layer.
- [execution/cli](https://basehub.org/crates/execution/cli/): Command-line entry point for the OP execution node with jemalloc, OpenTelemetry, and asm-keccak.
- [execution/consensus](https://basehub.org/crates/execution/consensus/): Validates OP blocks and verifies trie roots inside the execution layer.
- [execution/evm](https://basehub.org/crates/execution/evm/): OP EVM block executor and state transition logic for the Base execution environment.
- [execution/exex](https://basehub.org/crates/execution/exex/): Execution Extensions for OP-Reth, including the proofs ExEx that emits trie updates.
- [execution/hardforks](https://basehub.org/crates/execution/hardforks/): Defines Optimism hardforks and activation rules used throughout op-reth.
- [execution/node](https://basehub.org/crates/execution/node/): Assembles the OP execution node from EVM, RPC, payload, pool, and storage components.
- [execution/payload](https://basehub.org/crates/execution/payload/): Builds OP execution payloads from pending transactions for the engine API.
- [execution/primitives](https://basehub.org/crates/execution/primitives/): OP-specific transaction, receipt, and block primitive types shared across the execution layer.
- [execution/reth](https://basehub.org/crates/execution/reth/): Meta-crate that re-exports all OP reth components behind feature gates.
- [execution/rpc](https://basehub.org/crates/execution/rpc/): Implements the eth_, debug_, and op_ JSON-RPC namespaces for the OP execution layer.
- [execution/storage](https://basehub.org/crates/execution/storage/): Database codecs for OP storage types used by the execution layer.
- [execution/trie](https://basehub.org/crates/execution/trie/): Stores trie nodes so the node can serve proofs across the fault proof window.
- [execution/txpool](https://basehub.org/crates/execution/txpool/): OP-Reth transaction pool with gas estimation and L1 data cost accounting.
- [infra](https://basehub.org/crates/infra/overview/): Operational tooling for Base — basectl, ingress RPC, WebSocket proxy, mempool rebroadcaster, and tests.
- [infra/audit](https://basehub.org/crates/infra/audit/): Consumes transaction events from Kafka and archives them to S3 for audit retention.
- [infra/basectl](https://basehub.org/crates/infra/basectl/): Ratatui-based terminal UI for interacting with Base, with WebSocket, clipboard, and contract support.
- [infra/based](https://basehub.org/crates/infra/based/): Shared library for block header fetching and StatsD metrics emission via cadence.
- [infra/ingress-rpc](https://basehub.org/crates/infra/ingress-rpc/): Ingress JSON-RPC server that forwards transactions to the builder and writes a Kafka audit trail.
- [infra/mempool-rebroadcaster](https://basehub.org/crates/infra/mempool-rebroadcaster/): Rebroadcasts mempool transactions to multiple upstream providers to ensure propagation.
- [infra/system-tests](https://basehub.org/crates/infra/system-tests/): End-to-end test harness exercising the Base stack against Kafka, S3, and multiple providers.
- [infra/websocket-proxy](https://basehub.org/crates/infra/websocket-proxy/): WebSocket proxy built on axum with Brotli compression and exponential backoff reconnects.
- [proof](https://basehub.org/crates/proof/overview/): Fault proof crates covering the FPVM runtime, preimage oracle, driver, executor, and MPT verification.
- [proof/driver](https://basehub.org/crates/proof/driver/): no_std driver that sequences derivation and execution steps inside the fault proof program.
- [proof/executor](https://basehub.org/crates/proof/executor/): no_std stateless OP Stack block builder that runs the EVM inside the FPVM.
- [proof/mpt](https://basehub.org/crates/proof/mpt/): Merkle Patricia Trie utilities for traversal, lookup, and proof verification inside the FPVM.
- [proof/preimage](https://basehub.org/crates/proof/preimage/): Rust bindings and types for the PreimageOracle ABI used by fault proof programs.
- [proof/proof](https://basehub.org/crates/proof/proof/): OP Stack Proof SDK with KZG via ark-bls12-381, preimage oracle integration, and the full proof pipeline.
- [proof/std-fpvm](https://basehub.org/crates/proof/std-fpvm/): Platform APIs and a buddy allocator for programs targeting Fault Proof VM kernels.
- [proof/std-fpvm-proc](https://basehub.org/crates/proof/std-fpvm-proc/): Procedural macros that emit the entry point for kona-std-fpvm proof programs.
- [shared](https://basehub.org/crates/shared/overview/): Foundational crates for primitives, access lists, JWT auth, bundles, CLI utilities, and RPC types.
- [shared/access-lists](https://basehub.org/crates/shared/access-lists/): Implements Flashblock-level Access Lists (FAL), the EIP-7928 adaptation used by Base.
- [shared/bundles](https://basehub.org/crates/shared/bundles/): Defines transaction bundle types with UUID IDs, signing, and gas estimation for ordering.
- [shared/cli-utils](https://basehub.org/crates/shared/cli-utils/): Shared CLI helpers for tracing, Prometheus export, clap parsing, and Kona registry lookups.
- [shared/engine-ext](https://basehub.org/crates/shared/engine-ext/): In-process engine client that talks directly to Reth's execution layer without going over RPC.
- [shared/jwt](https://basehub.org/crates/shared/jwt/): Loads and validates JWT secrets that authenticate Engine API traffic between node components.
- [shared/node](https://basehub.org/crates/shared/node/): Core node harness with the types and traits used to build Base node runner extensions.
- [shared/primitives](https://basehub.org/crates/shared/primitives/): Shared primitive types, Brotli helpers, bundle types, and Solidity bindings used across Base.
- [shared/reth-rpc-types](https://basehub.org/crates/shared/reth-rpc-types/): Re-exports Reth RPC types so external consumers of the Base RPC interface get a stable surface.
- [shared/txpool-rpc](https://basehub.org/crates/shared/txpool-rpc/): Adds Base-specific RPC methods for inspecting and interacting with the transaction pool.

## Binaries

- [audit-archiver](https://basehub.org/binaries/audit-archiver/): Kafka-to-S3 audit log archival service with configurable worker pools.
- [base-reth-node](https://basehub.org/binaries/base-reth-node/): The main Base Reth Node binary — a Reth-based Ethereum execution client for the Base L2 network.
- [basectl](https://basehub.org/binaries/basectl/): TUI management utility for configuring and inspecting Base nodes across different network targets.
- [based](https://basehub.org/binaries/based/): Block-building sidecar service with health checks and StatsD metrics.
- [builder](https://basehub.org/binaries/builder/): The Base block builder binary for flashblock production and block building.
- [consensus](https://basehub.org/binaries/consensus/): The Base consensus node binary implementing the OP Stack consensus protocol via Kona.
- [ingress-rpc](https://basehub.org/binaries/ingress-rpc/): JSON-RPC ingress proxy with Kafka audit trail for transaction and bundle submission.
- [mempool-rebroadcaster](https://basehub.org/binaries/mempool-rebroadcaster/): Bidirectional Geth-Reth mempool transaction rebroadcasting service.
- [websocket-proxy](https://basehub.org/binaries/websocket-proxy/): Fan-out WebSocket proxy with Brotli compression, API key authentication, and rate limiting.

## Specifications

- [Access Lists Specification](https://basehub.org/specifications/access-lists/): Flashblock-Level Access Lists (FAL) — adapting EIP-7928 for flashblock chains.
- [Azul Execution Engine](https://basehub.org/specifications/azul-exec-engine/): Execution-engine changes in the Azul hardfork — the EIP-7825 transaction gas cap, Osaka-era EVM and precompile updates, eth/69 networking, a slimmed Flashblocks payload, and the eth_config RPC method.
- [Azul Proof System](https://basehub.org/specifications/azul-proofs/): Specification of the Azul multi-proof design — the AggregateVerifier dispute game, TEE and ZK proof paths, and the finality windows that govern L2 checkpoint withdrawals.
- [Azul Upgrade Overview](https://basehub.org/specifications/azul-overview/): Summary of the Azul hardfork — Osaka EVM features, a streamlined Flashblocks websocket format, and a multi-proof system for L2 checkpoints.
- [B20 Native Token Standard](https://basehub.org/specifications/b20/): Base's native token standard, serving creators of long-tail tokens, stablecoin issuers, and issuers of real-world assets (RWAs) and equities.
- [Beryl Upgrade Overview](https://basehub.org/specifications/beryl-overview/): Summary of the Beryl hardfork — the B20 native token standard, a shorter single-proof withdrawal window, and the Reth V2 node release.
- [Challenger](https://basehub.org/specifications/challenger/): Offchain service that detects invalid AggregateVerifier games and submits dispute transactions on L1 to nullify them.
- [Configuration](https://basehub.org/specifications/configuration/): Reference for Base Chain configuration parameters and the roles authorized to change them, grouped into consensus parameters, policy parameters, admin roles, and service roles.
- [Flashblocks Specification](https://basehub.org/specifications/flashblocks/): JSON-RPC methods, parameters, and return types exposed by the Flashblocks RPC provider.
- [Glossary](https://basehub.org/specifications/glossary/): Definitions for the terms used throughout the Base Chain protocol specification — from L1/L2 basics to sequencing, deposits, withdrawals, batch submission, derivation, and the execution engine.
- [Isthmus L2 Execution Engine](https://basehub.org/specifications/isthmus-exec-engine/): Execution-engine changes introduced by the Isthmus upgrade — the L2ToL1MessagePasser storage root in the block header, deposit-request handling, BLS precompiles, and the new operator fee.
- [Jovian L2 Execution Engine](https://basehub.org/specifications/jovian-exec-engine/): Execution-engine changes introduced by the Jovian upgrade — a configurable minimum base fee, the DA footprint block limit, the updated operator fee formula, and precompile input-size restrictions.
- [P2P Networking Stack](https://basehub.org/specifications/p2p/): How Base nodes discover peers and gossip blocks across two independent P2P stacks — discv5 plus libp2p on the consensus layer and DevP2P plus RLPx on execution.
- [Proof Contracts](https://basehub.org/specifications/contracts/): Onchain contracts that verify proof material, track game state, and release withdrawals for the Azul proof system.
- [Proof System Overview](https://basehub.org/specifications/proofs-overview/): Roles of the offchain services and onchain contracts that make Azul L2 checkpoint proposals verifiable from Ethereum.
- [Proposer](https://basehub.org/specifications/proposer/): Offchain service that turns canonical L2 checkpoint ranges into AggregateVerifier dispute games on L1.
- [Reth V2](https://basehub.org/specifications/reth-v2/): The Reth V2 node release — up to 50% smaller on disk, with a rebuilt state-root pipeline that raises throughput and lowers per-block execution latency.
- [TEE Prover](https://basehub.org/specifications/tee-prover/): Offchain service that re-executes L2 block ranges inside AWS Nitro Enclaves to produce signed proof material for AggregateVerifier games.
- [TEE Prover Registrar](https://basehub.org/specifications/registrar/): Offchain service that discovers TEE prover enclaves, attests them with a ZK proof, and maintains the onchain TEEProverRegistry of accepted signer identities.
- [Transaction Event Journal](https://basehub.org/specifications/transaction-events/): The transaction-event/v1 contract — a shared JSONL business-event journal for Base transaction observability.
- [ZK Prover](https://basehub.org/specifications/zk-prover/): Offchain service that drives SP1 programs to produce permissionless proofs for AggregateVerifier proposals and disputes.

## Security

- [Avoid Malicious Flags](https://basehub.org/security/avoid-malicious-flags/): Practical steps to keep your Base app from being flagged as malicious — verify contracts, request verification, and follow UX best practices.
- [Bug Bounty](https://basehub.org/security/bug-bounty/): Coinbase's million-dollar HackerOne bug bounty program covers Base, the Base bridge contracts, and Base infrastructure.
- [Reporting Vulnerabilities](https://basehub.org/security/report-vulnerability/): How to report Base vulnerabilities — HackerOne for offchain services and infrastructure, Cantina for deployed smart contracts.
- [Security Council for Base](https://basehub.org/security/security-council/): Composition, quorum rules, member criteria, and responsibilities of the Security Council that approves Base contract upgrades.

## Contributing

- [Contributing](https://basehub.org/contributing/): Issues and pull requests are off. Reach out on X.