Search

Search for projects by name

Value SecuredActivityOnchain costsData postedLivenessMilestones & IncidentsRisk summaryRisk analysisRollup stageData availabilityState validationOperatorWithdrawalsOther considerationsPermissionsSmart contracts

K2 logo
K2

Badges

About

K2 is a general-purpose L2, which rebranded to the OpenGDP Network to soon become an asset tokenization-focused L1.

  • Total Value SecuredTVS
    $9.22 M0.38%
  • Past day UOPSDaily UOPS
    0.0054.7%
  • Gas token
    ETH
  • Type
    Other
  • Purpose
    Universal
  • Chain ID
    2410

    • Tokens breakdown

    Value secured breakdown

    View TVS breakdown
    Sequencer failureState validationData availabilityExit windowProposer failure
    Explore more in Discovery UI

    Badges

    About

    K2 is a general-purpose L2, which rebranded to the OpenGDP Network to soon become an asset tokenization-focused L1.

    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 SecuredView TVS breakdown
    Total
    Canonically BridgedCanonically Bridged ValueCanonical
    Natively MintedNatively Minted TokensNative
    Externally BridgedExternally Bridged ValueExternal
    ETH & derivatives
    Stablecoins
    BTC & derivatives
    Other
    View TVS breakdown
    Activity

    2024 Dec 03 — 2025 Dec 03

    Past Day UOPS
    <0.01
    Past Day Ops count
    404
    Max. UOPS
    0.27
    2024 Mar 17
    Past day UOPS/TPS Ratio
    1.00
    Onchain costs

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

    Data in this section may be temporarily out of date due to third-party provider issues. We're working to resolve this.

    2024 Dec 03 — 2025 Dec 03

    Total cost
    $8.74 K
    Avg cost per L2 UOP
    $0.150984
    Avg cost per day
    $23.95
    Data posted

    This section shows how much data the project publishes to its data-availability (DA) layer over time. The project currently posts data toCelestiaCelestia.

    2024 Dec 03 — 2025 Dec 03

    Data posted
    631.46 MiB
    Avg size per day
    1.77 MiB
    Avg size per L2 UOP
    11.64 KiB
    Liveness

    This section shows how "live" the project's operators are by displaying how frequently they submit transactions of the selected type. It also highlights anomalies - significant deviations from their typical schedule.

    Data in this section may be temporarily out of date due to third-party provider issues. We're working to resolve this.
    No ongoing anomalies detected
    Avg. tx data subs. interval
    Avg. state updates interval
    Past 30 days anomalies
    No data
    Milestones & Incidents

    Karak rebrands to OpenGDP

    2025 Nov 17th

    Karak rebrands to OpenGDP.

    Learn more

    K2 Network Early Access Launch

    2024 Feb 27th

    K2 Network is live on mainnet.

    Learn more
    Risk summary

    Funds can be stolen if

    1. a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL),
    2. an invalid state root is submitted to the system (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
    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 stage
    K2
    K2 is not even a
    Stage 0
    project.
    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 onchain

    All the data that is used to construct the system state is published onchain in the form of cheap calldata. This ensures that it will always be available when needed.

    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 3d 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 KarakMultisig

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

    Guardian KarakMultisig

    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 EOA 1

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

    Sequencer EOA 2

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

    Actors:

    KarakMultisig 0x28A2…b920

    A Multisig with 3/5 threshold.

    • Can upgrade with no delay
      • L2OutputOracle
      • SystemConfig
      • L1ERC721Bridge
      • L1CrossDomainMessenger
      • L1StandardBridge
      • OptimismPortal
      • OptimismMintableERC20Factory
    • 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
    • A Challenger - acting directly
    • A Guardian - acting directly

    Participants (5):

    0xAb86…2cac0x7E97…8Cd00xBcB3…28d30x9883…A4f20x282D…D117
    EOA 1 0x4179…729e
    EOA 2 0x84Bd…1e4E
    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

    L2OutputOracle 0x0a23…1637Implementation (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 KarakMultisig
      • challenger: KarakMultisig
      • proposer: EOA 1
    Can be upgraded by:
    KarakMultisig with no delay
    SystemConfig 0x6223…88A7Implementation (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 KarakMultisig
      • batcherHash: EOA 2
      • owner: KarakMultisig
    Can be upgraded by:
    KarakMultisig with no delay
    OptimismPortal 0xeeCE…eA73Implementation (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 KarakMultisig
      • guardian: KarakMultisig
    • This contract stores the following tokens: ETH.
    Can be upgraded by:
    KarakMultisig with no delay
    L1ERC721Bridge 0x9528…491EImplementation (Upgradable)Admin

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

    • Roles:
      • admin: ProxyAdmin; ultimately KarakMultisig
    Can be upgraded by:
    KarakMultisig with no delay
    L1CrossDomainMessenger 0x9BFf…022dImplementation (Upgradable)Admin

    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.

    • Roles:
      • admin: ProxyAdmin; ultimately KarakMultisig
    Can be upgraded by:
    KarakMultisig with no delay
    L1StandardBridge 0xBA61…48A3Implementation (Upgradable)Admin

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

    • Roles:
      • admin: ProxyAdmin; ultimately KarakMultisig
    • This contract can store any token.
    Can be upgraded by:
    KarakMultisig with no delay
    ProxyAdmin 0x1612…065C
    • Roles:
      • owner: KarakMultisig
    OptimismMintableERC20Factory 0xF04a…13DBImplementation (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 OptimismMintableERC20 as this chain’s representation of a token on the host chain, or vice-versa.

    • Roles:
      • admin: ProxyAdmin; ultimately KarakMultisig
    Can be upgraded by:
    KarakMultisig with no delay

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

    Generic escrow 0xBA61…48A3Implementation (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 0xeeCE…eA73Implementation (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).