Search for projects by name
Kroma aims to develop a universal ZK Rollup based on the Optimism Bedrock architecture. Currently, Kroma operates as an Optimistic Rollup with ZK fault proofs, utilizing a zkEVM based on Scroll and a zkVM based proven with SP1.
Kroma aims to develop a universal ZK Rollup based on the Optimism Bedrock architecture. Currently, Kroma operates as an Optimistic Rollup with ZK fault proofs, utilizing a zkEVM based on Scroll and a zkVM based proven with SP1.
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:
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.
The section shows the operating costs that L2s pay to Ethereum.
SP1 fault proofs upgrade
2025 Feb 11th
Kroma adds an option to prove faults using the SP1 zk virtual machine.
Ecotone upgrade
2024 Apr 25th
Introduces EIP-4844 data blobs for L1 data availability and more L2 opcodes.
Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. ZK proofs are used to adjudicate the correctness of the last step. The challenge protocol can fail under certain conditions. The current system doesn’t use posted L2 txs batches on L1 as inputs to prove a fault (for the zkEVM prover path), meaning that DA is not always enforced.
There is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.
Kroma uses an interactive fraud proof system to find a single block of disagreement, which is then ZK proven. Once the single block of disagreement is found, the challenger is required to present a ZK proof of the fraud. This can be either a proof verified in a zkEVM verifier base on Scroll, or in a zkVM verifier built by Succinct SP1. If the proof is validated, the incorrect state output is deleted. The Security Council can always override the result of the challenge, it can also delete any L2 state root at any time. The protocol can fail under certain conditions.
Funds can be lost if the cryptography is broken or implemented incorrectly.
All executed transactions are submitted to an on chain smart contract. The execution of the rollup is based entirely on the submitted transactions, so anyone monitoring the contract can know the correct state of the rollup chain.
Kroma nodes source code, including full node, proposer and validator, can be found here. Also, the geth server, source maintained here, is a fork of go-ethereum. For more details on how they are different from the Optimism implementation, see here. The instructions to run the proposer (called validator) and the ZK prover, are documented here.
Data batches are compressed using the zlib algorithm with best compression level.
The genesis file can be found here.
While forcing transaction is open to anyone the system employs a privileged sequencer that has priority for submitting transaction batches and ordering transactions.
MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.
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.
Users can (eventually) exit the system by pushing the transaction on L1 and providing the corresponding state root. The only way to prevent such withdrawal is via an upgrade.
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.
Allowed to pause deposits and withdrawals.
Allowed to commit transactions from the current layer to the host chain.
forceDeleteOutput()
).Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
Is allowed to interact with SecurityCouncilTokenOwners - one of the signers of the KromaSecurityCouncil.
The L2OutputOracle contract contains a list of proposed state roots which Proposers assert to be a result of block execution. Anyone can participate as a Proposer by depositing in the ValidatorPool. A root can be proposed every 1800 blocks (2s block time).
Manages the set of Proposers (Validators in Kroma) and selects the next proposer with the window to submit the output root within 30m, after which anyone can propose for them. It is also the entry point for other contracts, such as the L2OutputOracle and the Colosseum, which distribute output rewards and slash challenge losers. It makes successive calls to the AssetManager to apply changes to the proposers’ assets.
Merkle Trie contract used to prove withdrawals that were initiated in the legacy system, deprecated for new withdrawals and succeeded by a merkle tree library in the KromaPortal.
This contract is the router for zk proof verification. It stores the mapping between identifiers and the address of onchain verifier contracts, routing each identifier to the corresponding verifier contract.
Implementation used in:
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.
Used to bridge ERC-721 tokens from host chain to this chain.
Contract used to challenge state roots and prove fraud. If successful, the wrong state root in the L2OutputOracle is replaced.
This contract stores the following tokens: USDC.
The main entry point to deposit ERC20 tokens from host chain to this chain. This contract can store any token.
Manages the delegation and undelegation of KRO tokens and Kroma Guardian House (KGH) NFTs for Proposers (Kroma Validators) and distributes rewards.
Implementation used in:
Contract used to compute hashes. It is used by the ZKMerkeTrie. The contract has been generated using the circomlibjs library.
Contract used to manage the Proposers. Anyone can submit a deposit and bond to a state root, or create a challenge. It also manages the Proposer rotation for each submittable block using a random selection. If the selected proposer fails to publish a root within 30m then the submission becomes open to everyone.
Main entry point for users depositing ERC20 token that do not require custom gateway.
Main entry point for users depositing ETH.
Main entry point for users depositing USDC.
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).