Skip to content

Run a block producing node on Partisia Blockchain

You must finish the previous two sections(Reader node on VPS and Keys for BP) is a prerequisite.

Step 1 - Stop your reader node

Find the reader node container name:

docker ps

Stop the reader node:

docker stop yourContainerNamer

Step 2 - Change config.json to support block production

To fill out the config.json for a block producing node you need to add the following information:

  • Network privateKey
  • Account privateKey
  • Finalization privateKey
  • IP address of the server hosting your node (You get this from your VPS service provider)
  • Ethereum API endpoint. This is a URL address pointing to an Ethereum reader node on the Ethereum Mainnet (You should use a source you find trustworthy). This user made guide has a provider list and further information about endpoints.

Start by opening the config.json in nano:

sudo nano /opt/pbc-mainnet/conf/config.json

Config for the block producing nodes - baker nodes, ZK nodes and oracle nodes Put your private keys and IP inside the quotation marks replacing descriptions in capital letters. The IP address must be a public IPv4.:

  "restPort": 8080,
  "floodingPort": 9888,
  "networkKey": "NETWORK_PRIVATE_KEY",
  "producerConfig": {
    "finalizationKey": "FINALIZATION_PRIVATE_KEY_BLS",
  "knownPeers": [

To save the file press CTRL+O and then ENTER and then CTRL+X.

You can verify the contents of the files are what you expect by opening them with cat:

sudo cat /opt/pbc-mainnet/conf/config.json
# The config file should be printed here

Start your block producing node

docker-compose up -d

This should pull the latest image and start the reader node in the background. If the command was executed successfully it won't print anything. To verify that the node is running, run:

docker logs -f pbc-mainnet

This should print a bunch of log statements. All the timestamps are in UTC and can therefore be offset several hours from your local time.