Quick joining GLADIATOR
Setup SONs and join GLADIATOR public TESTNET
This is a quick document which assumes that the user has experience in setting up various Graphene blockchains before. The following link can be a good refresher: https://community.peerplays.tech/witnesses/becoming-a-witness
In this document the executables are downloaded for the Gitlab CI-CD pipeline
1. Prepare the server
The following dependencies are necessary for a clean Ubuntu 18.04 LTS
sudo apt-get install autoconf bash build-essential ca-certificates cmake \
doxygen git graphviz libbz2-dev libcurl4-openssl-dev libncurses-dev \
libreadline-dev libssl-dev libtool libzmq3-dev locales ntp pkg-config \
wget2. Download SON executable
Go to https://gitlab.com/PBSA/peerplays/-/jobs and find the job ID for the build you want to use. Build should have the following properties
Job: features/SONs-base
Stage: build
Name: build
Example of such a job has ID 467332251:
To download executables, click Download button on the right side of the Job page, or execute the following command:
To unpack executables in current folder:
Execute the witness_node binary which will create the necessary files and folders under witness_node_data_dir
Stop the node (CTRL + c ) and edit config.ini to configure the node.
Connecting to PBSA's Gladiator Testnet
Inside config.ini, set the seed-nodes to:
In order to sync with PBSA's Gladiator Testnet, the genesis file must be exactly the same as used by the witness nodes. This file can be downloaded here: https://drive.google.com/file/d/1YmDbwUB-5D5vGzc9vYEva8yLkTkwva8r/view?usp=sharing
Move the genesis.json file to the root of the project directory alongside the witness_node binary.
Inside config.ini, specify the genesis.json
Start the witness_node and the blocks should start syncing.
If blocks have already been seeded during the initial startup, it may be necessary to reset the blockchain and p2p directories. Removing them is fine for this case.
At this point you will be able download a copy of the blockchain. Additional steps are required to run the cli_wallet and also become a SON.
SON configuration
Prerequisites
Your node is up and running and synced with the network.
You have access to a bitcoin node, with RPC and ZMQ notifications enabled
You have access to shared wallet used by all SONs (prerelease requirement only)
Configuration files
SON plugin is controlled by following parameters
These parameters are available from both command line and config file:
Edit add the following to your config.ini file
Edit the config file and add the RPC port
Becoming a SON
Becoming a SON is very similar to becoming a witness. You will need:
Active user account, upgraded to lifetime member, which will be the owner of SON account
Create two vesting balances (types son and normal) of 50 core assets, and get its IDs
Create Bitcoin address for SON account in shared SON wallet
Create SON account, and get its ID
Set the signing key for a son account (usually, its a signing key of owner account)
Set the bitcoin address as a sidechain address for a SON account
Update your config file with values obtained in previous steps, and restart the witness with peerplays_sidechain plugin enabled
Example:
Starting the node
Using the CLI wallet
In the terminal execute the CLI wallet:
If an exception is thrown and contains Remote server gave us an unexpected chain_id, then copy the remote_chain_id that is provided by it.
Pass the chain ID to the CLI wallet:
Enter a password for the CLI wallet:
Unlock the CLI wallet by providing the password set earlier:
The CLI wallet is now ready to be used.
Creating a Peerplays account
Use the CLI wallet to suggest a brain key:
Make sure to backup the information that is output
Create an account using the brain key generated:
Last updated
Was this helpful?
