Run node: init

To deploy, mitum needs to be initialized it’s database and storage fs. With node config, init needs another config, which defines operations for genesis block, initial network policy and other configurations.

Genesis Config

genesis-design.yml
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
facts:
  - _hint: suffrage-genesis-join-fact-v0.0.1
    nodes:
      - _hint: node-v0.0.1
        address: no0sas
        publickey: bXTT1hoetSKYPUmfu3bMRcs8aU342MTTzhgeCQ1bTavBmpu

  - _hint: genesis-network-policy-fact-v0.0.1
    policy:
      _hint: network-policy-v0.0.1
      max_operations_in_proposal: 99
      suffrage_candidate_lifespan: 333333333
      suffrage_candidate_limiter:
        _hint: fixed-suffrage-candidate-limiter-rule-v0.0.1
        limit: 1
      max_suffrage_size: 3
  • facts lists the facts of genesis operations. It’s shape is almost identical of json output of operation fact.

Facts

  • _hint: suffrage-genesis-join-fact-v0.0.1

    Defines the initial suffrage nodes

  • _hint: genesis-network-policy-fact-v0.0.1

    Defines the initial network policy

init

$ ./mitum-example init genesis-degign.yml --design=first-node.yml

This will initialize storage and generates genesis block.