Kroma
GithubCommunity
  • Introduction
    • Overview
    • KRO Tokenomics
      • Token Allocation
      • Token Distribution
      • Token Utilities
      • Airdrops
        • Initial Airdrop
    • Official Links
  • BUILDERS
    • Developers
      • Contract Deployment Tutorial
        • Using Foundry
        • Using Remix IDE
        • Using Hardhat
      • JSON-RPC API
      • Oracles
    • Node Operators
      • Kroma MPT Migration Guide
      • Running a Full Node
      • Running a Kroma v2 Validator Node
        • How to Migrate Your Validator to KRO-based Validator System
      • How to Sync Blocks Using a Snapshot
      • FAQ
      • [Deprecated] Running a Kroma v1 Validator Node
        • How to Check and Claim the Validator Reward
    • Network Information
    • Protocol Contracts
    • Testnet
      • Setup
      • Faucet
      • Bridge
      • Contract Addresses
  • USERS
    • Wallet Configuration
    • Bridge
    • Block Explorer
    • How to Swap legacy USDC to upgradable USDC
  • Governance
    • Kroma Security Council
  • Kroma Guardian House
    • Overview
    • Philosophy
    • KRO & KGH NFT Staking
      • Validator Boosting by KGH NFT
      • How to Get KRO
      • FAQ
    • KGH NFT Migration & KYC
      • KGH NFT Migration
      • How to Complete KYC with Argos
    • KGH NFT Sales (Ended)
      • KGH Utilities
      • Referral Program: Expand Your Impact
      • Estimated Reward Value
    • Notice
  • Resources
    • Security
    • Brand Kit
    • FAQs
    • Glossary
Powered by GitBook
On this page
  • The Roles and Responsibilities of the Security Council
  • Proof of Membership
  • Members of the Security Council

Was this helpful?

  1. Governance

Kroma Security Council

PreviousHow to Swap legacy USDC to upgradable USDCNextOverview

Last updated 6 months ago

Was this helpful?

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 . 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 Roles and Responsibilities of the Security Council

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.

Proof of Membership

Members of the Security Council

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.

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 .

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

this article
L1
L2
Animoca Brands
Cosmostation
Hexlant
InfStones
Kroma Foundation
Luganodes
Neuler
Node Guardians
WEMIX Foundation
Xangle
this article