Skip to content
Bloxberg Genesis file and Bootnodes
Branch: master
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
README.md
bloxberg.json
bootnodes.txt
exampleNode.pwd
exampleNode.toml

README.md

NetworkSpec

Bloxberg Genesis file and Bootnodes

Remote Machine Minimum System Requirements:

  • Ubuntu 16.04 or 18.04 Image,
  • Minimum 1 CPU,
  • Minimum 1GB Memory,
  • Anything > 4GB will be good, but may need to be upgraded in the future,

In order to connect to the bloxberg network, you will need to install the latest stable parity version (https://github.com/paritytech/parity-ethereum) on the server. You will also find the genesis file, an example config, and the initial bootnodes located here.

Furthermore, you must install a clock synchronizer as the consensus algorithm that bloxberg relies on (AuRa) establishes that the clocks must be synced between the validation nodes. You can utilize chrony or NTP for this purpose, you can find brief instructions (Only Installation is necessary) for your OS here: https://www.tecmint.com/install-chrony-in-centos-ubuntu-linux/

To join the bloxberg network after installing parity:

  1. Change the account section in exampleNode.toml to your node address and password to unlock the account. Change the engine_signer section with your validator address. Also, change the nat parameter under [network] to your external IP.
  2. Launch parity with ‘parity --tracing on –config exampleNode.toml’. This will throw an error because the account doesn’t exist but will generate the folder structure.
  3. Add your keystore (UTC file) to ./bloxbergData/exampleNode/keys/Bloxberg
  4. Upon parity launch, it will also generate an enode address to download the blockchain. Add this address to bootnodes.txt file
  5. Run parity again with ‘parity --tracing on –config exampleNode.toml’ and the blockchain should initialize and start downloading the current state of the chain from the bootnodes.
  6. We recommend daemonizing the process and adding as a startup process to the server so the node is stable.
You can’t perform that action at this time.