MilkyWay Docs
  • INTRODUCTION
    • Welcome to MilkyWay
    • Mission and Vision
    • MILK
      • Tokenomics
    • Whitepaper (PDF)
  • User Guides
    • For Liquid Stakers
      • Quick Start
      • For Celestia (milkTIA)
        • Technical Architecture
          • Liquid Staking Process
          • Withdrawal Process
          • Exchange Rate
          • Compound Staking Rewards
          • Claim Process
          • Limits and Restrictions
        • Integrating with milkTIA
          • Contract Specifications
          • APIs specification
        • Using third party apps
          • Camelot
          • Demex
          • Dymension
          • Levana
          • Margined
          • Mars
          • Osmosis
          • UX
      • For Initia (milkINIT)
        • Technical Architecture
          • Liquid Staking Process
          • Withdrawal Process
          • Exchange Rate
          • Compound Staking Rewards
          • Claim Process
          • Limits and Restrictions
        • Integrating with milkINIT
          • Liquid staking module specifications
          • Chains specifications
      • For Bablyon (milkBABY)
        • Technical Architecture
          • Liquid Staking Process
          • Withdrawal Process
          • Exchange Rate
          • Compound Staking Rewards
          • Claim Process
          • Limits and Restrictions
        • User Flow
        • One-Click Stake
        • Integrating with milkBABY
          • Liquid staking module specifications
          • Chains specifications
    • For Restakers
      • Quick Start
      • For Restakers
        • Creating a wallet
        • Restaking your assets
    • Bridging
      • Hyperlane
      • IBC Eureka
  • Infrastructure Operators
    • For MilkyWay Validators
      • Quick Start
      • For Validators
        • Consesus node
        • Validator node
    • For Service Operators
      • Quick Start
      • For Operators
        • Operator Management
        • Opt-in and Opt-out Services
  • For Service Developers
    • Quick Start
    • For Services Admins
      • Service Management
      • Inviting Operators to Join Your Service
      • Creating Rewards Distribution Plan
  • Architecture
    • Modular Liquid Staking
      • Overview
      • Liquid Staking 101
    • Modular Restaking
      • Overview
        • Technical Architecture
        • Design Philosophy
        • Programmable Rules
        • Economic Model
        • Use Cases
      • Restaking 101
  • Modules
    • x/assets
    • x/ibc-hooks
    • x/liquidvesting
    • x/operators
    • x/pools
    • x/restaking
    • x/rewards
    • x/services
    • x/tokenfactory
  • SECURITY
    • Audits
    • Bug Bounty Program
  • APPENDIX
    • Official Links
    • Frequently Asked Questions
    • Glossary
    • Branding Resources
Powered by GitBook
On this page
  • Hardware requirements
  • Setting up a validator node
  • 1. Set up a consensus node
  • 2. Create a wallet
  • 3. Delegate stake to your validator
  • 4. Run the Skip Connect sidecar
  1. Infrastructure Operators
  2. For MilkyWay Validators
  3. For Validators

Validator node

PreviousConsesus nodeNextFor Service Operators

Last updated 5 months ago

This section contains the information related to becoming a validator of our network. This page is NOT for operators. If you want to run an AVS operator, please refer to the "" section instead.

Hardware requirements

The following hardware minimum requires are recommended for running a validator node:

  • Memory: 8 GB RAM

  • CPU: 4 cores

  • Disk: 1 TB SSD Storage

  • Bandwidth: 1 Gbps for Download/1 Gbps for Upload

Setting up a validator node

The following tutorial is done on a Ubuntu Linux 20.02 (LTS) x64 instance machine.

1. Set up a consensus node

In order to run a validator node, you fist have to .

2. Create a wallet

Once you have setup a consensus node, you will have to .

3. Delegate stake to your validator

Finally, you will have to delegate some stake to your validator to make it so that it can join the active validator set and start taking part to the consensus of the chain.

To do so, you can run the following command:

milkywayd tx staking delegate \
  $(milkywayd keys show <You validator key name> --bech val -a) \
  1000000umilk \
  --from <Your validator key name> \
  --chain-id ceers-2112 \
  --gas auto --gas-prices 0ustake --gas-adjustment 1.5

Where:

  • <Your validator key name> represents the name of the key associated to your validator wallet

4. Run the Skip Connect sidecar

The final step you have to perform is running the Skip Connect application. We use this as an oracle form to include assets prices inside our chain via Tendermint's Vote Extensions.

To run the application, you can refer to the .

Operators
setup a consensus node
create a wallet
official guide