POSDAO activation

Dear @xdai-validators

We are going to activate POSDAO on xDai chain at block 9186425 (Wednesday, 1-Apr-2020 ~08:18 am UTC).

For that, we need to update both Parity (to our v2.7.2-posdao-stable fork) and spec.json. The spec file of xDai network is updated for the HF.

Please follow the steps below:

  1. ssh login to your node
  2. stop parity service
sudo systemctl stop poa-parity
  1. switch to home directory (NOTE: if you’re updating a bootnode, path is /home/bootnode)
cd /home/validator

output should be

  1. remove older backups
sudo rm -rf backups-version
  1. create a new backup
sudo mkdir backups-version
sudo touch backups-version/BEFORE-2.7.2
BKPFLDR="backups-version/$(date '+%Y%m%dT%H%M%S' -u)"
sudo mkdir -p "$BKPFLDR"
sudo mv parity spec.json "$BKPFLDR"
  1. switch to validator user (NOTE: if you’re updating a bootnode, username should be bootnode)
sudo -i -u validator
  1. download new parity binary from our repo
curl -LO 'https://github.com/poanetwork/open-ethereum/releases/download/v2.7.2-posdao-stable/parity'
  1. check binary integrity
echo 'b8c5822c9e7c70fa553a8fd00dde07f4fd026b7116098c7e565779d56febd05a parity' | sha256sum -c

output should be

parity: OK
  1. set permission to execute the binary
chmod +x parity
  1. download new spec file
curl -LO 'https://raw.githubusercontent.com/poanetwork/poa-chain-spec/dai/spec.json'
  1. check that new spec contains a transition block set to 9186425
grep 9186425 spec.json

output should be

            "9186425": {
          "9186425": "0x481c034c6d9441db23Ea48De68BCAe812C5d39bA"
          "9186425": "0x5870b0527DeDB1cFBD9534343Feda1a41Ce47766"
        "posdaoTransition": 9186425
    "transactionPermissionContractTransition": 9186425
  1. login back to sudo-enabled user
  1. restart services
sudo systemctl start poa-parity && sleep 10 && sudo systemctl restart poa-netstats
  1. check that your node is “green” in netstats https://dai-netstat.poa.network (this may take a couple of minutes)
  2. wait to see if your node produces new blocks https://blockscout.com/poa/xdai/
1 Like

:green_circle: POA Network
:green_circle: Syncnode
:green_circle: Anyblock Analytics
:green_circle: Lab10 collective
:green_circle: Burner Wallet
:green_circle: MakerDAO
:green_circle: Protofire
:green_circle: Giveth
:green_circle: Portis
:green_circle: Gnosis
:green_circle: Galt Project
:green_circle: Nethermind


Hello! Syncnode validator updated


Ahoy! Giveth node updated


Hola! Protofire node updated :slight_smile:


Anyblock Analytics updated.

Outstanding instructions, as always :+1:


@matilote Please check your xDai node, seems it has 0 peers and thus skipping blocks.

A friendly ping to update your nodes for upcoming POSDAO activation on 2020-04-01T07:00:00Z

@chebykin (Galt Project) please restart your node since it’s offline and isn’t producing blocks: https://blockscout.com/poa/xdai/address/0x0000999dc55126CA626c20377F0045946db69b6E/validations

This can be done with the following command:

sudo systemctl stop poa-parity && sleep 10 && sudo systemctl start poa-parity && sleep 10 && sudo systemctl restart poa-netstats

1 Like

@varasev this is done, had some issues with firewall setup.


@varasev done, there was an issue with a server itself, not a parity client. thanks for quick reaction


@varasev - lab10 has been updated

1 Like

Three days left before the hard fork.

Portis @tomteman
Gnosis @denisgranha
MakerDAO @lollike @savdao

Please update.

Good afternoon @varasev Gnosis node has just been updated https://dai-netstat.poa.network/


@varasev MakerDAO node updated


Hi @tomteman We have less than 24 hours before POSDAO activation. All nodes (except yours) have already been updated. Please, follow the instruction above to switch your spec and client to a new version.

1 Like

@varasev Portis is live, sorry for the delay :slight_smile:



@saschagoebel (Anyblock Analytics)
@chebykin (Galt Project)

We’re observing a slow work of your nodes when committing/revealing random numbers. This makes the next validators (after you in AuRa round - Syncnode and Nethermind respectively) skip blocks sometimes (because the previous block time is 8-9 seconds instead of 5).

The reason is unknown yet, but the logs on Nethermind’s node and our node show that the bottleneck is definitely in the code responsible for making committing/revealing transactions.

This is only observed on your nodes. The rest validators are fine.

To help us find the bottleneck in Parity’s code, please switch the logs on your node to the detailed mode.

For that, you need to set

logging = "engine=trace,miner=trace"

in [misc] section of node.toml and restart the node with

sudo systemctl stop poa-parity && sleep 10 && sudo systemctl start poa-parity && sleep 10 && sudo systemctl restart poa-netstats

This will turn on advanced logs which we will be able to analyze a bit later.

@varasev, done…

Done. 350G free disk space, should be enough for some logs :wink: