Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
276 lines (212 sloc) 7.13 KB

Intro for new developers and witnesses

This is a quick introduction to get new developers and witnesses up to speed on Peerplays blockchain. It is intended for witnesses plannig to join a live, already deployed blockchain.

Building on Ubuntu 18.04 LTS and Installation Instructions

The following dependencies were necessary for a clean install of Ubuntu 18.04 LTS:

sudo apt-get install gcc-5 g++-5 cmake make libbz2-dev\
    libdb++-dev libdb-dev libssl-dev openssl libreadline-dev\
     autoconf libtool git

Build Boost 1.67.0

mkdir $HOME/src
cd $HOME/src
export BOOST_ROOT=$HOME/src/boost_1_67_0
sudo apt-get update
sudo apt-get install -y autotools-dev build-essential  libbz2-dev libicu-dev python-dev
wget -c ''\
     -O boost_1_67_0.tar.bz2
tar xjf boost_1_67_0.tar.bz2
cd boost_1_67_0/
./ "--prefix=$BOOST_ROOT"
./b2 install

Building Peerplays

cd $HOME/src
export BOOST_ROOT=$HOME/src/boost_1_67_0
git clone
cd peerplays
git submodule update --init --recursive
make -j$(nproc)

make install # this can install the executable files under /usr/local

docker build -t peerplays .

Docker image

# Install docker
sudo apt install

# Add current user to docker group
sudo usermod -a -G docker $USER
# You need to restart your shell session, to apply group membership
# Type 'groups' to verify that you are a member of a docker group

# Build docker image (from the project root, must be a docker group member)
docker build -t peerplays .

# Start docker image
docker start peerplays

# Exposed ports
# # rpc service:
# EXPOSE 8090
# # p2p service:
# EXPOSE 1776

Rest of the instructions on starting the chain remains same.

Starting A Peerplays Node

For Ubuntu 14.04 LTS and up users, see this and then proceed with:

git clone
cd peerplays
git submodule update --init --recursive

Launching the witness creates required directories. Next, stop the witness and continue.

$ vi witness_node_data_dir/config.ini
p2p-endpoint =
rpc-endpoint =
seed-node =

Start the witness back up


Upgrading A Peerplays Node

To minimize downtime of your peerplays node when upgrading, one upgrade idea was written in this steemit article.

Wallet Setup

Then, in a separate terminal window, start the command-line wallet cli_wallet:


To set your initial password to 'password' use:

>>> set_password password
>>> unlock password

A list of CLI wallet commands is available here.

Testnet - "Beatrice"

  • chain-id - T.B.D.

Use the get_private_key_from_password command

You will to generate owner and active keys

get_private_key_from_password your_witness_username active the_key_you_received_from_the_faucet

This will reveal an array for your active key ["PPYxxx", "xxxx"]

import_keys into your cli_wallet

  • use the second value in the array returned from the previous step for the private key
  • be sure to wrap your username in quotes
  • import the key with this command
import_key "your_witness_username" xxxx

Upgrade your account to lifetime membership

upgrade_account your_witness_username true

Create your witness (substitute the url for your witness information)

  • place quotes around url
create_witness your_witness_username "url" true

Be sure to take note of the block_signing_key

IMPORTANT (issue below command using block_signing_key just obtained)

get_private_key block_signing_key

Compare this result to


You should see 3 pairs of keys. One of the pairs should match your block_signing_key and this is the one you will use in the next step!

Get your witness id

get_witness username (note the "id" for your config)

Modify your witness_node config.ini to include your witness id and private key pair.

Comment out the existing private-key before adding yours

vim witness_node_data_dir/config.ini

witness-id = "1.6.x"
private-key = ["block_signing_key","private_key_for_your_block_signing_key"]

start your witness back up


If it fails to start, try with these flags (not for permanent use)

./programs/witness_node/witness_node --resync --replay

Vote for yourself

vote_for_witness your_witness_account your_witness_account true true

Ask to be voted in!

Join @Peerplays Telegram group to find information about the witness group.

You will get logs that look like this:

2070264ms th_a       application.cpp:506           handle_block         ] Got block: #87913 time: 2017-05-27T16:34:30 latency: 264 ms from: bhuz-witness  irreversible: 87903 (-10)

Assuming you've received votes, you will start producing as a witness at the next maintenance interval (once per hour). You can check your votes with.

get_witness your_witness_account


It's important for your witness to start when your system boots up. The filepaths here assume that you installed your witness into /home/ubuntu/peerplays

Create a logfile to hold your stdout/err logging

sudo touch /var/log/peerplays.log

Save this file in your peerplays directory. vi /home/ubuntu/peerplays/


cd /home/ubuntu/peerplays
./programs/witness_node/witness_node &> /var/log/peerplays.log

Make it executable

chmod 744 /home/ubuntu/peerplays/

Create this file: sudo vi /etc/systemd/system/peerplays.service Note the path for Change it to match where your file is if necessary.

Description=Peerplays Witness


WantedBy =

Enable the service

sudo systemctl enable peerplays.service

Make sure you don't get any errors

sudo systemctl status peerplays.service

Stop your witness if it is currently running from previous steps, then start it with the service.

sudo systemctl start peerplays.service

Check your logfile for entries

tail -f /var/log/peerplays.log

Running specific tests

  • tests/chain_tests -t block_tests/name_of_test
You can’t perform that action at this time.