Skip to content

bpos-setup.md

Latest commit

 

History

History
72 lines (48 loc) · 3.18 KB

bpos-setup.md

File metadata and controls

72 lines (48 loc) · 3.18 KB
Raw

BPoS Setup

A new stake model to make consensus networks more decentralized as well as to improve the security and stability of the network, read more about Elastos BPoS.

DPoS Supernode smooth transition to BPoS Supernode

Users who have already registered a DPoS super node register a BPoS super node through Essentials. The BPoS super node can share the nodepublickey of the DPoS 1.0 super node, and DPoS 1.0 node users do not need to change server configuration. The ELA mainnet node turns on BPoS consensus, then the BPoS super node participates in consensus and gets the reward.

First BPoS Supernode setup

After registering the BPoS node with Essentials, complete the BPoS node build with the following steps. A BPoS node only requires the ELA main chain, so it runs the mainchain profile (a Council node, which also runs the side chains and arbiter, uses the full profile instead).

Preparation

  1. BPoS Supernode Ops please read security
  2. BPoS Supernode Ops please configure your server according to the server requirements

ELA node setup

  1. Install node.sh with the one-liner, then install the dependencies it needs:

    $ curl -fsSL https://raw.githubusercontent.com/elastos/Elastos.Node/master/build/skeleton/install.sh | bash
$ sudo apt-get install -y jq lsof apache2-utils curl openssl

  2. Select the mainchain profile so only the ELA node is installed and managed:

    $ ~/node/node.sh profile set mainchain

  3. Initialize the node, open the peer/consensus ports, and start it, then bind the nodepublickey using Essentials:

    $ ~/node/node.sh init
$ ~/node/node.sh firewall
$ ~/node/node.sh start

  4. Check the status of the node. The status command shows the program is Running. Watch the Height to make sure the chain is synchronized.

    $ ~/node/node.sh status

    For a one-row glance, use ~/node/node.sh summary. To read the node's public key for Essentials once synced, run ~/node/node.sh ela status --verbose.

Governance commands

Registration is normally done through Essentials, but node.sh exposes the on-chain governance actions directly. They run only after ELA is fully synced. Commands may be written in snake_case or kebab-case (register_bpos or register-bpos).

$ ~/node/node.sh ela register_bpos NAME URL BLOCKS [REGION]
$ ~/node/node.sh ela activate_bpos
$ ~/node/node.sh ela vote_bpos PUB_KEY AMOUNT BLOCKS
$ ~/node/node.sh ela stake_bpos AMOUNT
$ ~/node/node.sh ela claim_bpos AMOUNT [ELA_ADDRESS]
$ ~/node/node.sh ela unstake_bpos AMOUNT [ELA_ADDRESS]
$ ~/node/node.sh ela unregister_bpos

Node upgrade tools

  • Keep the script current with ~/node/node.sh update_script (checksum-verified; script_update also works). Update the chain binaries with ~/node/node.sh update.
  • Use this tool Elastos.ELA.MiscTools to quickly complete node upgrades

FAQ