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

Was this helpful?

  1. BUILDERS

Node Operators

This page describes how to run a node on Kroma.

PreviousOraclesNextKroma MPT Migration Guide

Last updated 10 months ago

Was this helpful?

This document serves as a guide for setting up different nodes on Kroma, taking you through the necessary hardware requirements and the installation and setup process. It also provides information on how to effectively run the node to contribute to the network's decentralization and earn rewards.

Kroma comprises three types of nodes: sequencer, validator, and full node. For more detailed information on Kroma’s architecture, please refer to this .

Currently, validator and full nodes can be run by anyone, whereas the operation of sequencer nodes is exclusively handled by the Kroma Foundation. The following components listed down below are used to run each code. For a detailed description of each node, please refer to the .

Node

Components

Full node

kroma-geth, kroma-node

Sequencer

kroma-geth, kroma-node, kroma-batcher

Validator

kroma-geth, kroma-node, kroma-validator, kroma-prover

The following are the minimum and recommended hardware requirements to run each client on Kroma:

Minimum

Recommended

kroma-geth

  • CPU with 2+ cores

  • 4GB RAM

  • 512GB free storage space to sync the Mainnet

  • 8 MBit/sec download Internet service

  • Fast CPU with 4+ cores

  • 16GB+ RAM

  • High-performance SSD with at least 512GB of free space

  • 25+ MBit/sec download Internet service

kroma-node

  • CPU with 1+ cores

  • 2GB RAM

  • CPU with 2+ cores

  • 4GB+ RAM

kroma-validator

  • CPU with 1+ cores

  • 2GB RAM

  • CPU with 2+ cores

  • 4GB+ RAM

kroma-prover

  • CPU with 48 cores

  • 384GB RAM

  • CPU with 128 cores

  • 1024GB RAM

Note: kroma-prover is expensive and only needed when a challenge occurs. It is recommended to turn it on and off as needed to generate a ZK fault proof.

You can find step-by-step guides on how to run a full node and a validator node in next pages.

Medium article
Github documentation