Search

Search for projects by name or address

SummaryValue SecuredRisk summaryRisk analysisStageData availabilityState validationUpdatesOperatorWithdrawalsPermissionsSmart contracts

Bug Buster logo
Bug Buster

This project is archived and no longer maintained.

Critical contract references can be changed by an EOA which could result in the loss of all funds.

Badges

About

Bug Buster is an open source bug bounty platform for web3, powered by Cartesi.

  • Total Value SecuredTVS
    $116.441.44%
  • Past day UOPSDaily UOPS
    No data
  • Type
    Other
  • Purpose
    Bug bounty
  • Host chain
    OP Mainnet

    • Tokens breakdown

    Sequencer failureState validationData availabilityExit windowProposer failure
    Explore more in Discovery UI

    Badges

    About

    Bug Buster is an open source bug bounty platform for web3, powered by Cartesi.

    Why is the project listed in others?

    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 here.

    Value Secured

    View TVS breakdown
    Total
    Canonically BridgedCanonically Bridged ValueCanonical
    Natively MintedNatively Minted TokensNative
    Externally BridgedExternally Bridged ValueExternal
    ETH & derivatives
    Stablecoins
    BTC & derivatives
    Other
    View TVS breakdown

    Risk summary

    There are 2 additional risks coming from the host chain OP Mainnet logoOP Mainnet

    Funds can be stolen if

    1. an invalid state root is submitted to the system by the configured Authority (CRITICAL),
    2. the DApp owner changes the consensus implementation maliciously (CRITICAL).

    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

    The L3 risks depend on the individual properties of L3 and those of the host chain combined.
    Critical contract references can be changed by an EOA which could result in the loss of all funds.
    SEQUENCER
    FAILURE    		STATE
    VALIDATION    		DATA
    AVAILABILITY    		EXIT WINDOWPROPOSER
    FAILURE
    OP Mainnet
    L2
    		Self sequenceFraud proofs (INT)OnchainNoneSelf propose
    Bug Buster
    L3 • Individual
    		Self sequenceNoneOnchainNoneCannot withdraw
    Bug Buster
    L3 • Combined
    		Self sequenceNoneOnchainNoneCannot withdraw
    L2 & L3 individual risks
    Sequencer failureState validationData availabilityExit windowProposer failure
    L3 combined risks
    Sequencer failureState validationData availabilityExit windowProposer failure
    L3 combined risks
    The information below reflects combined L2 & L3 risks.
    Sequencer failure
    Self sequence

    In the event of a sequencerA party responsible for ordering and executing transactions on the rollup. The sequencer verifies transactions, compresses the data into a block, and submits the data related to it to enable state reconstruction to Ethereum L1 as a single transaction. The data can be either transaction data or state diffs. failure, users can force transactions to be included in the project’s chain by sending them to L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.. There can be up to a 12h delay on this operation.

    State validation
    None

    Currently the system permits invalid state rootsA cryptographic hash succinctly representing a state using a Merkle tree.. More details in project overview.

    Data availability
    Onchain

    All of the data needed for proof construction is published on the base chain, which ultimately gets published on Ethereum.

    Exit window
    None

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

    Proposer failure
    Cannot withdraw

    Only the whitelisted proposers can publish state rootsA cryptographic hash succinctly representing a state using a Merkle tree. on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development., so in the event of failure the withdrawals are frozen.

    Stage

    Bug Buster
    Bug Buster is not even a
    Stage 0
    Appchain
    project.
    The requirement for available nodeA software client that participates in the network. software is under review
    Learn more about Stages
    Please keep in mind that these stages do not reflect project security, this is an opinionated assessment of project 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 transaction data is recorded on chain

    All executed transactions are submitted to an on chain smart contract. The execution of the rollupA blockchain that inherits consensus and data availability from another blockchain called L1. Rollups enable trust minimized bridges with the base layer via proof systems, either optimistic or zero-knowledge. A rollup without a bridge, or without considering the bridge, is called a sovereign rollup. is based entirely on the submitted transactions, so anyone monitoring the contract can know the correct state of the rollup chain.

    1. InputBox.sol#30 - Optimism Etherscan source code, addInput function
    Learn more about the DA layer here: Ethereum logoEthereum

    State validation

    No state validation

    Ultimately, Cartesi DApps will use interactive fraud proofs to enforce state correctness. This feature is currently in development and the Bug Buster DApp permits invalid state rootsA cryptographic hash succinctly representing a state using a Merkle tree..

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

    • Funds can be stolen if the DApp owner changes the consensus implementation maliciously (CRITICAL).

    1. Authority.sol#L48 - Optimism Etherscan source code, submitClaim function
    2. CartesiDApp.sol#L201 - Optimism Etherscan source code, migrateToConsensus function

    Updates

    2024 September 27, 16:44 UTC
    3changes

    Discovery rerun on the same block number with only config-related changes.

    Discovery rerun on the same block number with only config-related changes.

    New and verified contracts

    + Status: CREATED
    contract MerkleV2 (oeth:0x33436035441927Df1a73FE3AAC5906854632e53d)
    +++ description: None
    + Status: CREATED
    contract CartesiMathV2 (oeth:0xB634F716BEd5Dd5A2b9a91C92474C499e50Cb27D)
    +++ description: None
    + Status: CREATED
    contract Bitmask (oeth:0xF5B2d8c81cDE4D6238bBf20D3D77DB37df13f735)
    +++ description: Implementation of bit mask with dynamic array.
    2025 July 14, 12:47 UTC
    5changes

    Discovery rerun on the same block number with only config-related changes.

    Discovery rerun on the same block number with only config-related changes.

    New and verified contracts

    + Status: CREATED
    contract History (0x04395d494624D2B6e30C0dfDB74498a2839f805d)
    +++ description: None
    + Status: CREATED
    contract BugBuster (0x3FF5C7383F614256053c3F6B86A47bA974937299)
    +++ description: None
    + Status: CREATED
    contract Authority (0x4246F5b1E52Fef1C52c96a9b1B679AE818d4fb35)
    +++ description: None
    + Status: CREATED
    contract InputBox (0x59b22D57D4f067708AB0c00552767405926dc768)
    +++ description: None
    + Status: CREATED
    contract ERC20Portal (0x9C21AEb2093C32DDbC53eEF24B873BDCd1aDa1DB)
    +++ description: None
    2024 September 27, 16:44 UTC
    3changes

    BugBuster was redeployed to bring a bounty for the latest solidity compiler version (v0.8.27). New CartesiDAPP(Bugbuster) added to discovery (code-identical except for compiler version).

    BugBuster was redeployed to bring a bounty for the latest solidity compiler version (v0.8.27). New CartesiDAPP(Bugbuster) added to discovery (code-identical except for compiler version).

    + Status: CREATED
    contract History (0x04395d494624D2B6e30C0dfDB74498a2839f805d)
    +++ description: None
    + Status: CREATED
    contract BugBuster (0x3FF5C7383F614256053c3F6B86A47bA974937299)
    +++ description: None
    + Status: CREATED
    contract Authority (0x4246F5b1E52Fef1C52c96a9b1B679AE818d4fb35)
    +++ description: None
    2024 August 30, 11:36 UTC
    5changes

    Provide description of changes. This section will be preserved.

    Provide description of changes. This section will be preserved.

    Initial discovery

    + Status: CREATED
    contract History (0x04395d494624D2B6e30C0dfDB74498a2839f805d)
    +++ description: None
    + Status: CREATED
    contract Authority (0x4246F5b1E52Fef1C52c96a9b1B679AE818d4fb35)
    +++ description: None
    + Status: CREATED
    contract InputBox (0x59b22D57D4f067708AB0c00552767405926dc768)
    +++ description: None
    + Status: CREATED
    contract ERC20Portal (0x9C21AEb2093C32DDbC53eEF24B873BDCd1aDa1DB)
    +++ description: None
    + Status: CREATED
    contract BugBuster (0x9cb6C6E904cE6BF3Ca6d0002b9629acce74Ea89b)
    +++ description: None

    Operator

    The section considers only the L3 properties. For more details please refer to OP Mainnet logoOP Mainnet

    The system has a centralized operator

    The operatorAn operator is the entity charged with managing a rollup and progressing its state. A rollup operator can be a centralized sequencer, proposer, prover, challenger, pauser of admin that is able to perform upgrades. is the only entity that can propose blocksAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over.. 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.

    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.

    Withdrawals

    The section considers only the L3 properties. For more details please refer to OP Mainnet logoOP Mainnet

    Regular exit

    The user initiates the withdrawal by submitting a regular transaction on this chain. When the blockAn ordered list of transactions and chain-related metadata that gets bundled together and published to the L1/DA layer. Nodes execute the transactions contained within blocks to change the rollup chain’s state. Protocol rules dictate what constitutes a valid block, and invalid blocks are skipped over. containing that transaction is settled the funds become available for withdrawal on L1Layer 1 (L1) is a blockchain that is self-reliant on its validator set for its security and consensus properties. Ethereum is an example of a layer 1. Blockchains started receiving the moniker of layer 1 once layer 2 became a meaningful area of development.. The process of settling a block usually takes several days to complete. Finally the user submits an L1 transaction to claim the funds.

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

    Permissions

    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco

    OP Mainnet

    Actors:

    BugBuster Owner0x7f9e…1ed3

    Owner of the Bug Buster Cartesi DApp. Can change the consensusAn agreement on the latest and correct state of a blockchain. Unlike L1 blockchains which coordinate participating nodes with consensus rules, rollups rely on L1s for reaching consensus by checking the state of the rollup smart contract deployed thereon. reference and therefore steal all funds.

    Authority Owner0xD330…1cf5

    Owner of the Authority contract - the current consensusAn agreement on the latest and correct state of a blockchain. Unlike L1 blockchains which coordinate participating nodes with consensus rules, rollups rely on L1s for reaching consensus by checking the state of the rollup smart contract deployed thereon. implementation. Can make arbitrary claims about the current state of Bug Buster and steal all funds in the absence of fraud proofs.

    Smart contracts

    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    Disco UI BannerExplore in Disco

    OP Mainnet

    BugBuster
    Escrow
    0x3FF5…7299

    CartesiDApp instance for the Bug Buster DApp, responsible for holding assets and allowing the DApp to interact with other smart contracts.

    All supported tokens in this escrow are included in the value secured calculation.

    InputBox0x59b2…c768

    Contract that receives arbitrary blobsThe data that a rollup publishes to its L1/data availability (DA) layer. They consist of the L2 transactions that are rolled up, along with some metadata. Blobs are introduced as a new transaction type within Ethereum with EIP-4844, and has rollup scaling specifically in mind. Blobs persist on Ethereum’s Beacon Chain ephemerally. as inputs to Cartesi DApps.

    ERC20Portal0x9C21…a1DB

    Contract that allows anyone to perform transfers of ERC-20 tokens to Cartesi DApps (like e.g. Bug Buster).

    Authority0x4246…fb35

    Simple consensusAn agreement on the latest and correct state of a blockchain. Unlike L1 blockchains which coordinate participating nodes with consensus rules, rollups rely on L1s for reaching consensus by checking the state of the rollup smart contract deployed thereon. model controlled by a single address, the owner.

    History0x0439…805d

    Contract that stores claims for Cartesi DApps.