Kroma Security Council
Last updated
Last updated
Kroma, the first OP Stack rollup with active fault proofs utilizing zkEVM, has launched its mainnet on September 5th, 2023. Current proof system of Kroma requires a Security Council that can complement its weaknesses as mentioned in this article. The Security Council will primarily act as the final security layer of Kroma, and it will also act as the upgrade mechanism of Kroma for the L1 and L2 contracts.
The Kroma Security Council is a multisig-based override and upgrade mechanism that consists of at least 8 different parties(Currently, there are 10 different parties). It holds two primary responsibilities: safeguarding assets on the platform and proposing/voting on Layer 1 and Layer 2 contract upgrades.
The members of the Security Council shall do the following:
Run a Validator node with Guardian mode on Kroma
Maintain vigilant oversight of the validator network, immediately addressing and reporting any performance or security anomalies.
Actively engage in the deliberation and decision-making processes pertinent to L1 and L2 contract modifications.
For more information on the Security Council’s role as the final security layer for Kroma’s assets and an upgrade mechanism, please refer to this article.
Each member of the Security Council is minted with an SBT that represents the membership of the Security Council. Only an account with the SBT can propose or vote in the Kroma Security Council DAO on Tally. Please note that the Kroma Security Council DAO exists on both L1 and L2.
The nine parties of the Security Council are as follows:
Various organizations have become part of Kroma’s Security Council, making the final security layer diversified. This diversity within the Security Council holds significant importance since its members play a dual role — safeguarding the Validator Network’s security and facilitating the ongoing upgrades for Kroma. It is essential for users to have confidence in the group responsible for both securing and advancing the chain.
