Search

Search for projects by name

SummaryValue SecuredActivityOnchain costsLivenessMilestones & IncidentsRisk summaryRisk analysisRollup stageData availabilityState validationOperatorWithdrawalsOther considerationsPermissionsSmart contracts

Boba Network logoBoba Network

Badges

About

Boba is an OP stack Optimistic Rollup built by the Enya team as core contributors to the Boba Foundation.

Value secured
$9.77 M4.13%
Canonically Bridged
$9.70 M
Natively Minted
$70.96 K
Externally Bridged
$0.00
View TVS Breakdown
  • Tokens
  • Past day UOPS
    0.0864.5%
  • 30D ops count
    129.25 K
  • Gas token
    ETH
  • Stage
  • Type
    Optimistic Rollup
  • Purpose
    Universal
    • Sequencer failureState validationData availabilityExit windowProposer failure
    Explore more in Discovery UI

    Badges

    About

    Boba is an OP stack Optimistic Rollup built by the Enya team as core contributors to the Boba Foundation.

    Recategorisation

    25d
    18h
    17m
    21s

    The project will be classified as "Other" due to its specific risks that set it apart from the standard classifications.

    The project will move to Others because:

    The proof system isn't fully functional

    Consequence: projects without a proper proof system fully rely on single entities to safely update the state. A malicious proposer can finalize an invalid state, which can cause loss of funds.

    Learn more about the recategorisation
    Value Secured

    2024 May 24 — 2025 May 24

    Total value securedTotal
    $9.77 M4.13%
    Canonically BridgedCanonically Bridged ValueCanonical
    $9.70 M4.15%
    Natively MintedNatively Minted TokensNative
    $70.96 K0.05%
    Externally BridgedExternally Bridged ValueExternal
    $0.000.00%
    View TVS breakdown
    Activity

    2024 May 24 — 2025 May 23

    Onchain costs

    The section shows the operating costs that L2s pay to Ethereum.

    2024 May 24 — 2025 May 23

    1 year total cost
    $49.23 K
    Avg cost per L2 UOP
    $0.060829
    1 year data posted
    1.74 GiB
    Avg size per L2 UOP
    2.25 KiB
    Liveness

    The chart illustrates how "live" the project's operators are by displaying how frequently they submit transactions of the selected type and if these intervals deviate from their typical schedule.

    2025 Apr 24 — May 24

    30D avg. tx data subs. interval
    56 minutes
    30D avg. state updates interval
    1 hour
    Past 30 days anomalies
    Milestones & Incidents

    Boba Anchorage Upgrade

    2024 Apr 16th

    Boba upgrades to Bedrock (OP Stack) and to EIP-4844 data blobs for L1 data availability.

    Learn more

    Boba launches L2 on BNB

    2022 Nov 1st

    Boba launches on BnB.

    Learn more
    Risk summary

    Funds can be frozen if

    1. the centralized validator goes down. Users cannot produce blocks themselves and exiting the system requires new block production (CRITICAL).

    MEV can be extracted if

    1. the operator exploits their centralized position and frontruns user transactions.
    Risk analysis
    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    Self sequence

    In the event of a sequencer failure, users can force transactions to be included in the project’s chain by sending them to L1. There can be up to a 12h delay on this operation.

    State validation
    None

    Currently the system permits invalid state roots. More details in project overview.

    Data availability
    Onchain

    All of the data needed for proof construction is published on Ethereum L1.

    Exit window
    None

    There is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.

    Proposer failure
    Cannot withdraw

    Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.

    Rollup stageBoba NetworkBoba Network is a
    Stage 0
    Optimistic Rollup.
    The requirement for available node software is under review

    Learn more about Rollup stages
    Please keep in mind that these stages do not reflect rollup security, this is an opinionated assessment of rollup maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal.
    Data availability

    All data required for proofs is published on chain

    All the data that is used to construct the system state is published on chain in the form of cheap blobs or calldata. This ensures that it will be available for enough time.

    1. Derivation: Batch submission - OP Mainnet specs
    2. BatchInbox - address
    3. OptimismPortal.sol - source code, depositTransaction function
    Learn more about the DA layer here: Ethereum logoEthereum
    State validation
    No state validation

    OP Stack projects can use the OP fault proof system, already being deployed on some. This project though is not using fault proofs yet and is relying on the honesty of the permissioned Proposer and Challengers to ensure state correctness. The smart contract system permits invalid state roots.

    • Funds can be stolen if an invalid state root is submitted to the system (CRITICAL).

    1. L2OutputOracle.sol - source code, deleteL2Outputs function
    Operator

    The system has a centralized operator

    The operator is the only entity that can propose blocks. A live and trustworthy operator is vital to the health of the system.

    • MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

    1. L2OutputOracle.sol - source code, CHALLENGER address
    2. L2OutputOracle.sol - source code, PROPOSER address

    Users can force any transaction

    Because the state of the system is based on transactions submitted on the underlying host chain and anyone can submit their transactions there it allows the users to circumvent censorship by interacting with the smart contract on the host chain directly.

    1. Sequencing Window - OP Mainnet Specs
    2. OptimismPortal.sol - source code, depositTransaction function
    Withdrawals

    Regular messaging

    The user initiates L2->L1 messages by submitting a regular transaction on this chain. When the block containing that transaction is settled, the message becomes available for processing on L1. The process of block finalization takes a challenge period of 7d to complete.

    • Funds can be frozen if the centralized validator goes down. Users cannot produce blocks themselves and exiting the system requires new block production (CRITICAL).

    1. OptimismPortal.sol - source code, proveWithdrawalTransaction function
    2. OptimismPortal.sol - source code, finalizeWithdrawalTransaction function
    3. L2OutputOracle.sol - source code, PROPOSER check

    Forced messaging

    If the user experiences censorship from the operator with regular L2->L1 messaging they can submit their messages directly on L1. The system is then obliged to service this request or halt all messages, including forced withdrawals from L1 and regular messages initiated on L2. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular message.

    1. Forced withdrawal from an OP Stack blockchain
    Other considerations

    EVM compatible smart contracts are supported

    OP stack chains are pursuing the EVM Equivalence model. No changes to smart contracts are required regardless of the language they are written in, i.e. anything deployed on L1 can be deployed on L2.

    1. Introducing EVM Equivalence
    Permissions
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco

    Ethereum

    Roles:

    Challenger Boba Multisig

    Allowed to challenge or delete state roots proposed by a Proposer.

    Guardian Boba Multisig

    Allowed to pause withdrawals. In op stack systems with a proof system, the Guardian can also blacklist dispute games and set the respected game type (permissioned / permissionless).

    Proposer 0xbfBA…21d0

    Allowed to post new state roots of the current layer to the host chain.

    Sequencer 0xe1B6…2230

    Allowed to commit transactions from the current layer to the host chain.

    Actors:

    Boba Multisig 0x5612…9bC4
    • A Multisig with 2/3 threshold.
    • Can upgrade with no delay
      • SystemConfig
        via - acting via ProxyAdmin
      • OptimismMintableERC20Factory
        via - acting via ProxyAdmin
      • OptimismPortal
        via - acting via ProxyAdmin
      • SuperchainConfig
        via - acting via ProxyAdmin
      • L1ERC721Bridge
        via - acting via ProxyAdmin
      • L2OutputOracle
        via - acting via ProxyAdmin
      • L1StandardBridge
        via - acting via ProxyAdmin
    • Can interact with SystemConfig
      • it can update the preconfer address, the batch submitter (Sequencer) address and the gas configuration of the system
    • Can interact with AddressManager
      • set and change address mappings
        via - acting via ProxyAdmin
    • A Challenger - acting directly
    • A Guardian - acting directly

    Participants (3):

    0xCCDE…1C630x6976…02ab0x33A0…0AC1
    Smart contracts
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    Ethereum

    SystemConfig 0x158F…59EBImplementation (Upgradable)Admin

    Contains configuration parameters such as the Sequencer address, gas limit on this chain and the unsafe block signer address.

    • Roles:
      • admin: ProxyAdmin; ultimately Boba Multisig
      • batcherHash: EOA 2
      • owner: Boba Multisig
    Can be upgraded by:
    Boba Multisig with no delay
    OptimismPortal 0x7B02…eE7eImplementation (Upgradable)Admin

    The main entry point to deposit funds from host chain to this chain. It also allows to prove and finalize withdrawals.

    • Roles:
      • admin: ProxyAdmin; ultimately Boba Multisig
      • guardian: Boba Multisig
    • This contract stores the following tokens: ETH.
    Can be upgraded by:
    Boba Multisig with no delay
    L2OutputOracle 0xbB7a…8741Implementation (Upgradable)Admin

    Contains a list of proposed state roots which Proposers assert to be a result of block execution. Currently only the PROPOSER address can submit new state roots.

    • Roles:
      • admin: ProxyAdmin; ultimately Boba Multisig
      • challenger: Boba Multisig
      • proposer: EOA 1
    Can be upgraded by:
    Boba Multisig with no delay
    SuperchainConfig 0x996f…c076Implementation (Upgradable)Admin

    This is NOT the shared SuperchainConfig contract of the OP stack Superchain but rather a local fork. It manages the PAUSED_SLOT, a boolean value indicating whether the local chain is paused, and GUARDIAN_SLOT, the address of the guardian which can pause and unpause the system.

    • Roles:
      • admin: ProxyAdmin; ultimately Boba Multisig
      • guardian: Boba Multisig
    Can be upgraded by:
    Boba Multisig with no delay
    L1CrossDomainMessenger 0x6D45…f69eImplementation (Upgradable)

    Sends messages from host chain to this chain, and relays messages back onto host chain. In the event that a message sent from host chain to this chain is rejected for exceeding this chain’s epoch gas limit, it can be resubmitted via this contract’s replay function.

    L1ERC721Bridge 0xA6Ad…f87eImplementation (Upgradable)Admin

    Used to bridge ERC-721 tokens from host chain to this chain.

    • Roles:
      • admin: ProxyAdmin; ultimately Boba Multisig
    Can be upgraded by:
    Boba Multisig with no delay
    L1StandardBridge 0xdc16…1c00Implementation (Upgradable)Admin

    The main entry point to deposit ERC20 tokens from host chain to this chain.

    • Roles:
      • admin: ProxyAdmin; ultimately Boba Multisig
    • This contract can store any token.
    Can be upgraded by:
    Boba Multisig with no delay
    OptimismMintableERC20Factory 0x4d89…f0c3Implementation (Upgradable)Admin

    A helper contract that generates OptimismMintableERC20 contracts on the network it’s deployed to. OptimismMintableERC20 is a standard extension of the base ERC20 token contract designed to allow the L1StandardBridge contracts to mint and burn tokens. This makes it possible to use an OptimismMintablERC20 as this chain’s representation of a token on the host chain, or vice-versa.

    • Roles:
      • admin: ProxyAdmin; ultimately Boba Multisig
    Can be upgraded by:
    Boba Multisig with no delay
    ProxyAdmin 0x6e59…a0Dc
    • Roles:
      • owner: Boba Multisig

    Value Secured is calculated based on these smart contracts and tokens:

    Generic escrow 0xdc16…1c00Implementation (Upgradable)Admin

    Main entry point for users depositing ERC20 token that do not require custom gateway.

    Can be upgraded by:
    ProxyAdmin with no delay
    Escrow for ETH 0x7B02…eE7eImplementation (Upgradable)Admin

    Main entry point for users depositing ETH.

    Can be upgraded by:
    ProxyAdmin with no delay

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).