DOCSEARCHbyAlgolia
Submit Docs

Base Documentation

website·Indexed 42 days ago

https://docs.base.org

Technical documentation for Base, including the Base Chain API, SDKs, and CLIs. Covers network concepts, authentication, error handling, rate limits, and quickstart guides.

Tokens
3.3K
Snippets
6
Records
40
Agent score
73%

What's inside Base

  1. Understand the Beryl upgrade features

    The Beryl upgrade focuses on issuance and scalability:

    • Introduces B20 native token standard for stablecoin, RWA, and equity issuers.
    • Reduces the single-proof dispute game finalization window from 7 days to 5 days (dual-proof fast path remains at 1 day).
    • Ships Reth V2 as the reference execution client for improved sync speed and throughput.

  2. Understand the Isthmus hardfork features

    The Isthmus upgrade incorporates Ethereum Pectra EIPs and introduces an operator fee mechanism for sequencer revenue. Key technical changes include:

    • Addition of operatorFeeScalar and operatorFeeConstant to SystemConfig.
    • Introduction of the OperatorFeeVault contract.
    • L2ToL1MessagePasser storage root added to block headers.

  4. Base Protocol Specifications Overview

    The Base protocol specifications cover the technical architecture of the L2 rollup, including:

    • Consensus: Details on the rollup node, L2 block derivation from L1 data, P2P gossip protocols, and the RPC interface (including optimism_outputAtBlock).
    • Execution: The L2 execution engine (EIP-1559 parameters, fee vaults), as well as precompiles, predeploys, and preinstalls available in the genesis state.
    • Bridging: Standard bridge contracts for ETH and ERC-20 transfers, the 7-day challenge period for withdrawals, cross-domain messengers, and the Base-Solana bridge.
    • Data Availability: The batcher component responsible for posting L2 sequencer data to L1.
    • Proofs: The Azul proof system, including offchain services and onchain contracts for verifying L2 checkpoints and the challenger service for detecting invalid games.

  5. Understand the Granite hardfork features

    The Granite upgrade restricts the input size of the bn256Pairing precompile to prevent unbounded gas consumption and updates the CHANNEL_TIMEOUT protocol parameter.

  6. Install Base-Anvil CLI for Foundry

    To use Base's Foundry build, install base-forge, base-cast, and base-anvil. These tools teach Foundry about Base's native precompiles.

  7. Understand the Ecotone hardfork features

    The Ecotone upgrade integrates Ethereum Dencun changes, specifically supporting EIP-4844 blob transactions as a data availability source and EIP-4788 beacon block roots.

  8. Utilize Flashblocks for low-latency data

    Flashblocks provide a high-performance architecture for block building on Base. Developers can interact with Flashblocks via WebSockets and specific RPC calls for real-time data and node setup.

  9. Understand the Delta hardfork and Span-Batches

    The Delta hardfork introduced 'span batches' to the Base network. This new batch format compresses multiple L2 blocks into single batcher transactions, which reduces L1 data costs by making L1 data posting more efficient.

  10. Understand the Jovian hardfork features

    The Jovian upgrade introduces a configurable minimum base fee via SystemConfig to reduce priority-fee auction durations and adds a DA footprint gas scalar to L1 attributes transactions for improved fee market stability.

  11. Understand the Fjord hardfork features

    The Fjord upgrade introduces:

    • FastLZ-based L1 fee estimation (replacing the previous estimator).
    • RIP-7212 secp256r1 precompile.
    • Brotli channel compression.
    • Updated protocol parameters for max sequencer drift and channel bank size.

  12. Understand the Cobalt upgrade features

    The Cobalt upgrade introduces several key improvements:

    • B20 token standard enhancements
    • Validity transactions
    • Dynamic node upgrades (using an Ethereum smart contract to store upgrade timestamps, allowing forks to activate without client restarts)
    • Migration of Base to a Trusted Execution Environment (TEE)