Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Example Config following SON config file is used as a template for SON test network.
Each node will require fine tuning to this config file, to set the parameters specific to that node.
On config file recreation, default values will be assigned to some of the properties, but some of them need to be changed or added manually for more complex testing environment.
To find values you need to put into config file, for particular SON, you need to get full SON Account info and its private key, using cli_wallet. Execute these commands with initialized wallet.
Our config params should look like this now
Now, we need to create a new bitcoin address and get its public and private key, and add them to config file
Our config param should look like this now
For more realistic test scenario, witnesses also need to be configured with their own IDs, public and private keys.
The minimum system requirements of the server which will host your SON Node.
Example config.ini settings and their explanations for SON Node operation.
Compile and run the source code without a Docker container.
Use a pre-configured Docker container to run a SON Node.
CLI checks to ensure the successful installation of Bitcoin-SON node.
The config.ini
file consist of all the necessary details to configure the node based on the operator's requirements. It has the option to enable/disable the use of specific asset, endpoint, wallets, etc.,
The set of active plugin options such as witness, debug_witness, account_history, market_history, and peerplay_sidechain are available.
There are other set of plugins such as elastic_search, es_object, snapshot, and delayed_node available to use based on the operator's requirements. (Disabled by default)
The config.ini can be divided into two section,
End point configuration
Plugin options (only active configurations are explained here)
The user must provide the details such as which network interfaces & ports to listen on and which seed nodes to use for peer discovery. Also, to be a SONs operator, the relevant plugin must be enabled.
The default configuration file looks as follows:
Only the essential details to configure SON node is mentioned below. The operator must provide their details for configuration. Example configuration values as follows:
The list of active plugins available in the config file are,
witness
debug_witness
account_history
market_history
peerplay_sidechain
The witness plugin default config is provided below and there is no manual configuration required if the SON operator is not also a block-producing witness on the same machine.
The debug_witness default config is provided below. By default the keys will be added after the node creation,
The account_history default config is provided below and no manual changes are required unless your use case necessitates it.
The market_history default config is provided below and no manual changes are required unless required.
This plugin consists of all the necessary details about various asset, IPs, private keys, wallet details, and API endpoints. In order to make the SON node work as required, the operator must carefully input their values and requirement in this configuration.
The default plugin configuration is mentioned below,
An example configuration to enable basic requirements for a SON node is explained below,
Config file contains all the default public/private keys for SON account, no changes are required here. But unused key pairs may be removed.
List of keypairs is ordered. The first one belongs to sonaccount1, last to sonaccount16
By using the cli_wallet, the SON account information, private key can be collected. Execute the below command in the wallet,
The config parameter should look like the below example,
SONs manual installation process is similar to witness node installation. However, the SONs will perform the assets transfer between Peerplays blockchain and other blockchains, we need to connect to another chain to be of any use. This document features the steps to configure and install Ethereum-SON.
The following steps outline the Manual Installation of a ETH-SON.
Build Peerplays node
Primary Requirements
Installation steps
Peerplays ETH-SON configuration
Start the SON
Before we begin, to set up a SON node requires about 110 PPY. This is to pay for an upgraded account (5 PPY) and to fund two vesting balances (50 PPY each). The remaining funds are to pay for various transaction fees while setting up the node. Please see Obtaining Your First Tokens for more info.
Note that these fees will likely change over time as recommended by the Committee of Advisors.
The detailed steps to build the Peerplays node is explained in the below readme file. Click the link to follow the steps.
It covers the initial steps in bringing up the node which includes latest Ubuntu installation and its software dependencies, building Peerplays, building docker images, starting & upgrading a Peerplays node, wallet setup, and finally witness node creation.
A Peerplays account to act as the SON operator.
An Ethereum account to join the ETH SON multisig on the ETH chain. The account can be created using Metamask, wallet, etc.,
An accessible Ethereum API node to communicate with the Ethereum network.
The SON node installation steps are explained in the below section. Click the link based on your preferences,
The generated config.ini
file will be located at /home/ubuntu/witness_node_data_dir/config.ini
. We'll begin by editing this config file.
The config file is large and only the required section is focused here. This section contains all the SON related configuration. Ensure the following config settings are in the config.ini
file under the peerplays_sidechain plugin options.
Make sure to add peerplays_sidechain
plugin along with existing plugins in config.ini
file. Find the plugins
option in the initial section of the config.ini
file and add the peerplays_sidechain
plugin to the list as shown below
In order to enable Ethereum sidechain, replace 0 by 1 in the below command.
By default, the value is "0" in the config.ini file.
After setting up the config.ini
file for SON operation, we'll start the node back up.
SON node is UP and it's time to play around !
Up until this point we have been running the node in the foreground which is fragile and inconvenient. So let's start the node as a service when the system boots up instead.
After that, it would be smart to create a backup server to enable you to make software updates, troubleshoot issues with the node, and otherwise take your node offline without causing service outages.
Now you have a SON, but have you thought about becoming a Witness? It will be a piece of cake for you since you've already set up a SON.
If you have a node that is accessible from the internet (for example, an API or Seed node) it would be wise to enable SSL connections to your node.
SON: Sidechain Operator Node - An independent server operator which facilitates the transfer of off-chain assets (like Bitcoin or Ethereum tokens) between the Peerplays chain and the asset's native chain.
Witness: An independent server operator which validates network transactions.
Witness Node: Nodes with a closed RPC port. They don't allow external connections. Instead these nodes focus on processing transactions into blocks.
Ethereum: Ethereum is a decentralized blockchain with smart contract functionality. Ether is the native cryptocurrency of the platform.
CLI checks to ensure the successful installation of Bitcoin-SON node.
After installing a Bitcoin SON node, you might want to run some basic tests to ensure everything is running smoothly with your Bitcoin node. Here are a few bitcoin-cli commands that you can run to check your node's functionality.
You can use these commands to get an overview of the Bitcoin network, how your node connects to the network, and your configured wallet and address settings.
List all commands, or get help for a specified command.
The "command"
in the above code block can be one of any bitcoin-cli commands listed in the reference doc. It's also optional and if left out will list all available commands. The help command is a good place to start to ensure the bitcoin-cli is actually available on your system.
Returns an object containing various state info regarding blockchain processing.
This command doesn't have any parameters. Running this command will list a lot of important information about the chain and your node. This is the command to use to see how much of the chain your node has validated and that you are connected to Bitcoin's mainnet. Here's what is returned in the call:
Returns details on the active state of the TX memory pool.
The TX memory pool, or "mempool", is the pool of unverified transactions that don't yet belong to a block in the chain. These transactions are basically waiting for miners to verify and include them in blocks to make them official.
This command is useful to view the network backlog of transactions. Here's what is returned:
Returns an object containing various state info regarding P2P networking.
This command is important for understanding the network connections of your node. Here is what is returned in this call:
Returns an object containing various wallet state info.
This shows the configuration of any wallets belonging to your node. In our case this will show us the "son-wallet" we should have set up. Here's what's returned:
Return information about the given bitcoin address.
Some of the information will only be present if the address is in the active wallet.
This is how you can view the pubkey for your Bitcoin addresses. Much more than that is returned:
Set up a Sidechain Operator Node (SON) by building the source code
The process of manually installing a SON is similar to installing a Witness Node. This is an introduction for new SONs to get up to speed on the Peerplays blockchain. It is intended for SONs planning to join a live, already deployed, blockchain.
This tutorial will take you through the steps required to have an operating SON. Since SONs serve the purpose of facilitating transfers of assets between the Peerplays blockchain and other blockchains, we'll need to connect to another chain to be of any use...
Please review the Requirements for setting up a SON before continuing to run a manual install following this guide.
The following steps outline the manual installation of a (Bitcoin enabled) SON.
Preparing the Environment
Build Peerplays
Connect to the Bitcoin Network and Generate an Address
Create a SON Account
Configure the SON
Start the SON
(Optional) Automatically Start the Node as a Service
Before we begin, to set up a SON node requires about 110 PPY. This is to pay for an upgraded account (5 PPY) and to fund two vesting balances (50 PPY each). The remaining funds are to pay for various transaction fees while setting up the node. Please see Obtaining Your First Tokens for more info.
Note that these fees will likely change over time as recommended by the Committee of Advisors.
Please see the general SON hardware requirements.
For the manual install, we'll be using a self-hosted Bitcoin node. The requirements that we'll need for this guide would be as follows (as per the hardware requirements doc):
The memory requirements shown in the table above are adequate to operate the node. Building and installing the node from source code (as with this manual installation guide) will require more memory. You may run into errors during the build and install process if the system memory is too low. See Installing vs Operating for more details.
The following dependencies are necessary for a clean install on Ubuntu 18.04 LTS:
Boost is a C++ library that handles common program functions like generating config files and basic file system i/o. Peerplays uses Boost to handle such functions. Since Boost is a dependency, we must build it here.
Now we build Peerplays with the official source code from GitHub.
Note: "1.5.18" can be replaced with the most recent release tag. For example: git checkout 1.5.18
where 1.5.18 is the latest production release tag as of July 2022. The list of releases is located here.
We start the SON Node with the witness_node
command although we are only intending to set up this node as a SON. This is because the same program is used to operate different types of nodes depending on how we configure the program. For more information on this, see Peerplays Node Types.
If we have installed the blockchain following the above steps, the node can be started as follows:
Running the witness_node program will create a config.ini
file with some default settings. We'll need to edit the config file so we'll stop the program for now. Stop the program with ctrl + c
.
There are two options available to connect to the Bitcoin network.
Run a Bitcoin node yourself
Find an open Bitcoin node to connect to
For the purposes of this guide, I'll discuss how to run a node yourself as that will be a more reliable connection for now. Either way you go, you'll need to collect the following information to use in the config.ini
file:
The IP address of a Bitcoin node you can connect to (127.0.0.1 if self-hosting)
ZMQ port of the Bitcoin node (default is 1111)
RPC port of the Bitcoin node (default is 8332)
Bitcoin RPC connection username (default is 1)
Bitcoin RPC connection password (default is 1)
Bitcoin wallet label (default is son-wallet)
Bitcoin wallet password
A new Bitcoin address
The Public key of the Bitcoin address
The Private key of the Bitcoin address
First we'll download and install one of the official Bitcoin Core binaries:
The official Bitcoin Core binaries can be found here: https://bitcoincore.org/en/download/
The latest supported version is 22.0 as of July 2022.
Then we make a config file to manage the settings of our new Bitcoin node.
in the Vim text editor we'll set the following:
Save and quit the Vim editor.
The settings in the config file above are set to reduce the requirements of the server. Block pruning and setting the node to Blocks Only save network and storage resources. For more information, see https://bitcoin.org/en/full-node#reduce-storage.
Lastly we'll set a Cron job to ensure the Bitcoin node starts up every time the server starts.
At the bottom of the crontab file, add the following:
Save and quit the crontab file. Now we're ready to fire up the Bitcoin node!
If successful, you'll see Bitcoin Core starting
. As an extra check to see if everything is working, try the bitcoin-cli -version
or bitcoin-cli getblockchaininfo
commands.
Your Bitcoin node should now be downloading the Bitcoin blockchain data from other nodes. This might take a few hours to complete even though we cut down the requirements with block pruning. It's a lot of data after all.
We'll need a wallet to store the new Bitcoin address.
Now we will create a Bitcoin address.
Then we'll use this address to get its keys.
Now we get the private key.
That was a lot to go over. Let's collect our data.
Keep this tuple handy. We'll need it in the Peerplays config file.
Becoming a SON is very similar to becoming a witness. You will need:
An active user account, upgraded to lifetime member, which will be the owner of the SON account
Create two vesting balances (types "son" and "normal") of 50 PPY, and get their IDs
The Bitcoin address created for the SON account
Create the SON account, and get its ID
Set the signing key for the SON account (usually, its a signing key of the owner account)
Set the Bitcoin address as a sidechain address for the SON account
We can run the Peerplays cli wallet connecting to the Peerplays node we have set up so far. Before we can do that we'll need to make a quick edit to the config.ini file.
in the first section of the config.ini file is the rpc-endpoint setting. We have to open our rpc-endpoint so we can use the Peerplays cli wallet. We'll enter the following:
Save the file and quit.
Our Peerplays node will have to be completely in sync with the blockchain before we can use the cli wallet so we'll start the node and wait for it to download all the data.
downloading all the transaction and block data will take hours. Unfortunately this is unavoidable the first time the node syncs with the blockchain. You might want to let this run overnight.
If you just can't wait for your node to sync, you can run the cli_wallet program on someone else's node. Simply pass the IP address of the other node like so. (In another command line window)
A good resource for server-rpc-endpoints is https://beta.eifos.org/status. They will be listed as API nodes and use the wss:// protocol.
Now that we have the cli_wallet running, you'll notice a new prompt.
This means we're in a cli_wallet session. First we'll make a new wallet and unlock it.
A list of CLI wallet commands is available here: https://devs.peerplays.tech/api-reference/wallet-api/wallet-calls
Assuming we're starting without any account, it's easiest to create an account with the Peerplays GUI Wallet. The latest release is located here https://github.com/peerplays-network/peerplays-core-gui/releases/latest. When you create an account with the GUI wallet, you should have a username and password. We'll need those for the next steps. First we'll get the private key for the new account.
The key beginning with "PPY" is the public key. The other key is the private key. We'll need to import this private key into the cli_wallet.
Next we'll upgrade the account to a lifetime membership.
At the time of writing this guide, this costs 5 PPY to perform this operation. You'll need that in your account first! To this end, see Obtaining Your First Tokens.
Next we'll create the vesting balances.
Now we have all the info we need to create a SON account.
To get the SON ID:
We'll set the signing key using the active key from the owning account:
Now we have our SON account ID and the public and private keys for the SON account. We'll need this for the config.ini
file.
The generated config.ini
file will be located at /home/ubuntu/witness_node_data_dir/config.ini
. We'll begin by editing this config file.
This file will be rather large so let's focus on the important part for configuring a SON node:
This section contains all the SON related configuration. Ensure the following config settings are in the config.ini
file under the peerplays_sidechain plugin options.
We're almost done, we also have to make sure the peerplays_sidechain plugin is listed in the plugins. Find the plugins
setting in the first section of the config.ini
file. If it's not already there, add the peerplays_sidechain
plugin to the list. Like so:
After setting up the config.ini
file for SON operation, we'll start the node back up.
Your SON is born! (pun intended)
Up until this point we have been running the node in the foreground which is fragile and inconvenient. So let's start the node as a service when the system boots up instead.
After that, it would be smart to create a backup server to enable you to make software updates, troubleshoot issues with the node, and otherwise take your node offline without causing service outages.
Why stop at Bitcoin?
Now you have a SON, but have you thought about becoming a Witness? It will be a piece of cake for you since you've already set up a SON.
If you have a node that is accessible from the internet (for example, an API or Seed node) it would be wise to enable SSL connections to your node.
SON: Sidechain Operator Node - An independent server operator which facilitates the transfer of off-chain assets (like Bitcoin or Ethereum tokens) between the Peerplays chain and the asset's native chain.
Witness: An independent server operator which validates network transactions.
Witness Node: Nodes with a closed RPC port. They don't allow external connections. Instead these nodes focus on processing transactions into blocks.
Vim: A text editing program available for Ubuntu 18.04. See vim.org
Peerplays Core release 1.6.0 will introduce changes to SONs operations, and SONs operators (those acting as a SON on the network) will need to upgrade to the latest software and make changes to their node configuration in the config.ini
file. These changes are critical to ensure un-interupted SONs network services.
A brief overview of changes is given here, followed by details in subsequent sections, including changes SONs operators will need to make to their nodes.
From 1.6.0 forward, following the hard-fork date, it will be possible for SONs operators to operate a subset of SONs. They will no longer be required to operate all supported SONs. I.e., if they wish to operate a Bitcoin SON but not a Hive SON, this will be possible following the hard fork.
1.6.0 Introduces experimental support for Libbitcoin.
Note: As support is experimental, it is recommended to continue using a bitcoind API access point at this time.
1.6.0 renames a configuration parameter for clarity. Existing config.ini
files will need to be adjusted.
1.6.0 adds some new configuration parameter, of which a few are mandatory. Existing config.ini
files will need to be adjusted.
1.6.0 adds a mandatory configuration parameter. Existing config.ini
files will need to be adjusted.
1.6.0 adds support for Ethereum SONs. SONs operators MAY add an Ethereum SON to their operations.
With this new upgrade, the bitcoin operators have two option to use for interfacing with the Bitcoin network. The two Bitcoin API endpoint options are,
Bitcoind
Libbitcoin (Experimental) (Note: The current recommendation is to continue using bitcoind until support for Libbitcoin reaches maturity.)
Important: Main-net SONs operators are recommended to use the bitcoind option at this point as the libbitcoin feature is considered experimental in this release. Test-net SONs operators may try out Libbitcoin if desired.
Operators upgrading from a previous version will need to edit their existing config.ini
file, as new config options are available and some are required in this release.
Parameter: use-bitcoind-client
(Recommended to use)
This option is used to select bitcoind as the API protocol for accessing the Bitcoin network. The user must add this option to their config and change the value from 0 to 1 to enable its usage. (Otherwise it will default to libbitcoin.)
Libbitcoin parameters The use of libbitcoin is not yet recommended for Main-net. These options MAY be added to the config file, but will be ignored so long as bitcoind is enabled. Example values are as follows:
Parameter: bitcoin-wallet-name
In 1.6.0, the bitcoin-wallet
option in config.ini is renamed to bitcoin-wallet-name
. The old option will not be recognized.
If the input is not updated, the SONs will not function. The following warning message will be shown at witness_node
startup:,
" Haven’t set up Bitcoin sidechain parameters "
After the upgrade, the HIVE plugin has only one new parameter added.
hive-wallet-account-name
The input for this parameter is the SON multisig account name on the HIVE network which is controlled by the SONs operators. This is the son-account
on HIVE mainnet.
New in this release, a SON operator may operate an ETH SON. Operators who wish to enable an ETH-SON can follow the steps from the link below,
Set up a Sidechain Operator Node (SON) using a pre-configured Docker container
This document assumes that you are running Ubuntu 18.04. Other Debian based releases may also work with the provided script.
This tutorial will take you through the steps required to have an operating SON. Since SONs serve the purpose of facilitating transfers of assets between the Peerplays blockchain and other blockchains, we'll need to connect to another chain to be of any use...
The following steps outline the Docker installation of a (Bitcoin enabled) SON:
Preparing the Environment
Installing Docker
The Bitcoin node
Installing the peerplays:son
image
Starting the environment
Using the CLI wallet
Update config.ini
with SON Account Info
Note that these fees will likely change over time as recommended by the Committee of Advisors.
For the docker install, we'll be using a self-hosted Bitcoin node. The requirements that we'll need for this guide are as follows (as per the hardware requirements docs):
Then we'll clone the Peerplays Docker repository.
It is required to have Docker installed on the system that will be performing the steps in this document.
Docker can be installed using the run.sh
script inside the Peerplays Docker repository:
Since the script has added the currently logged in user to the Docker group, you'll need to re-login (or close and reconnect SSH) for Docker to function correctly. You can check to see if the current user belongs to the Docker group with the groups
command. If the Docker group is still not listed after a re-login, you'll have to reboot the machine with sudo reboot
(This will be the case if your using Ubuntu 20.04).
Copy the example.env
to .env
located in the root of the repository:
We're going to have to make some changes to the .env
file so we'll open that now using the Vim editor.
Here are the important parts of the .env
file. These will be the parts that need to be edited or optionally edited. The rest of the file should be unchanged.
There are two options available to connect to the Bitcoin network.
Run a Bitcoin node yourself
Find an open Bitcoin node to connect to
For the purposes of this guide, I'll discuss how to run a node yourself as that will be a more reliable connection for now. Either way you go, you'll need to collect the following information to use in the config.ini
file:
The IP address of a Bitcoin node you can connect to (127.0.0.1 if self-hosting)
ZMQ port of the Bitcoin node (default is 1111)
RPC port of the Bitcoin node (default is 8332)
Bitcoin RPC connection username (default is 1)
Bitcoin RPC connection password (default is 1)
Bitcoin wallet label (default is son-wallet)
Bitcoin wallet password
A new Bitcoin address
The Public key of the Bitcoin address
The Private key of the Bitcoin address
First we'll download and install one of the official Bitcoin Core binaries:
The latest version is 0.21.1 as of July 2021. You may want to find and download the latest version of the binaries just like you would for the 0.21.1 version above.
Then we make a config file to manage the settings of our new Bitcoin node.
in the Vim text editor we'll set the following (You can copy and paste the content of this complete config file):
Save and quit the Vim editor.
Lastly we'll set a Cron job to ensure the Bitcoin node starts up every time the server starts.
At the bottom of the crontab file, add the following:
Save and quit the crontab file. Now we're ready to fire up the Bitcoin node!
If successful, you'll see Bitcoin Core starting
. As an extra check to see if everything is working, try the bitcoin-cli -version
or bitcoin-cli getblockchaininfo
commands.
If you use the Bitnodes website, your node will appear as "down" until it's almost done downloading and verifying the Bitcoin chain. This can take a while.
Your Bitcoin node should now be downloading the Bitcoin blockchain data from other nodes. This might take a few hours to complete even though we cut down the requirements with block pruning. It's a lot of data after all.
We'll need a wallet to store your Bitcoin address.
At this point we hit a fork in the road! You'll need to do one of the following:
Option 1: Generate a new Bitcoin address to use for your SON node. (see 3.2.a. below)
Option 2: Import an existing Bitcoin address to use for your SON node. (see 3.2.b. below)
Either way, you'll need the Bitcoin address, its public key, and its private key.
Now we will create a Bitcoin address.
Then we'll use this address to get its keys.
Now we get the private key.
You don't need to do this if you made a new address in step 3.3.a. above!
Now we will import an existing Bitcoin address. You'll need the private key of the existing address which should be obtainable from your current wallet. You may not be able to get the private key from online or cloud wallet providers (contact their support teams for assistance with this.)
Then you can get the public key with the getaddressinfo
command.
That was a lot to go over. Let's collect our data. Here's an example:
Keep your tuple handy. We'll need it in the Peerplays config file.
Use run.sh
to pull the SON image:
There are many example configuration files, make sure to copy the right one. In this case it is: config.ini.son-exists.example
Copy the correct example configuration:
We'll need to make an edit to the config.ini
file as well.
The important parts of the config.ini
file (for now!) should look like the following. But don't forget to add your own Bitcoin public and private keys!
Save the file and quit.
Once the configuration is set up, use run.sh
to start the peerplaysd and bitcoind containers:
The SON network will be created and the seed (peerplaysd) and bitcoind-node (bitcoind) containers will be launched. To check the status, inspect the logs:
If the logs are throwing errors, perform a replay.
After starting the environment, the CLI wallet for the seed (peerplaysd) will be available.
Open another terminal and use docker exec
to connect to the 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:
Set a password for the wallet and then unlock it:
The CLI wallet will show unlocked >>>
when successfully unlocked
The key beginning with "PPY" is the public key. The other key is the private key. We'll need to import this private key into the cli_wallet.
Next we'll upgrade the account to a lifetime membership.
Next we'll create the vesting balances.
Now we have all the info we need to create a SON account.
To get the SON ID:
We'll set the signing key using the active key from the owning account:
Now we have our SON account ID and the public and private keys for the SON account. We'll need this for the config.ini
file.
Lets stop the node for now so we can finish up the config.ini
.
Ensure the following config settings are in the config.ini
file under the peerplays_sidechain plugin options.
Then it's just a matter of starting the node back up!
Your SON is now good to go!
Up until this point we have been running the node in the foreground which is fragile and inconvenient. So let's start the node as a service when the system boots up instead.
After that, it would be smart to create a backup server to enable you to make software updates, troubleshoot issues with the node, and otherwise take your node offline without causing service outages.
Why stop at Bitcoin?
Now you have a SON, but have you thought about becoming a Witness? It will be a piece of cake for you since you've already set up a SON.
If you have a node that is accessible from the internet (for example, an API or Seed node) it would be wise to enable SSL connections to your node.
SON: Sidechain Operator Node - An independent server operator which facilitates the transfer of off-chain assets (like Bitcoin or Ethereum tokens) between the Peerplays chain and the asset's native chain.
Witness: An independent server operator which validates network transactions.
Witness Node: Nodes with a closed RPC port. They don't allow external connections. Instead these nodes focus on processing transactions into blocks.
Let's use Ethereum! 😃
Let's use Bitcoin!
Save the file and quit. Configuration of the Peerplays SON node is complete!
But seriously, that was no small feat. Congratulations on this accomplishment!
Let's use Bitcoin!
Before we begin, to set up a SON node requires about 110 PPY. This is to pay for an upgraded account (5 PPY) and to fund two vesting balances (50 PPY each). The remaining funds are to pay for various transaction fees while setting up the node. Please see for more info.
Please see the SON .
You can look at to learn more on how to install Docker. Or if you are having permission issues trying to run Docker, use sudo
or look at .
The official Bitcoin Core binaries can be found here:
The settings in the config file above are set to reduce the requirements of the server. Block pruning and setting the node to Blocks Only save network and storage resources. For more information, see .
You can also use this website to check the status of your node:
A list of CLI wallet commands is available here:
Assuming we're starting without any account, it's easiest to create an account with the Peerplays GUI Wallet. The latest release is located here: . When you create an account with the GUI wallet, you should have a username and password. We'll need those for the next steps. First we'll get the private key for the new account.
At the time of writing this guide, it costs 5 PPY to perform this operation. You'll need that in your account first! To this end, check out .
Vim is a text editing program available for Ubuntu 18.04. See
Bitcoin node type | CPU | Memory | Storage | Bandwidth | OS |
Self-Hosted, Reduced Storage | 2 Cores | 16GB | 150GB SSD | 1Gbps | Ubuntu 18.04 |
Bitcoin node type
CPU
Memory
Storage
Bandwidth
OS
Self-Hosted, Reduced Storage
2 Cores
150GB SSD
1Gbps
Ubuntu 18.04
16GB