POA Forum

Istanbul activation on SOKOL

Dear @poa-validators

We are going to activate Istanbul hard fork in Sokol at block 12095200 (Thursday, 05-Dec-19 11:00 UTC).

For that, we need to update both Parity (to v2.6.5) and spec.json. Spec file of Sokol network is updated for the HF.

This update is a little bit more involved than regular ones because both spec.json file and Parity should be updated at the same time. 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.6.5
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
curl -LO 'https://releases.parity.io/ethereum/v2.6.5/x86_64-unknown-linux-gnu/parity'
  1. check binary integrity
echo '62762f424ffcc9ea939f3e09904d64600c4966045a865cfd94f23cf967213a0d 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/sokol/spec.json'
  1. check that new spec contains a transition block set to 12095200
grep 12095200 spec.json

output should be

    "eip1283ReenableTransition": 12095200,
    "eip1344Transition": 12095200,
    "eip1706Transition": 12095200,
    "eip1884Transition": 12095200,
    "eip2028Transition": 12095200
          "12095200": {
          "12095200": {
          "12095200": {
          "12095200": {
  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://sokol-netstat.poa.network (this may take a couple of minutes)
  2. wait to see if your node produces new blocks https://blockscout.com/poa/sokol

Istanbul is already successfully activated on Kovan, Ropsten, Rinkeby, Goerli testnets.

1 Like

Done. You tagged both Core and Sokol, but only mentioned Sokol. What’s the plan for Core?

Best, MM

1 Like

We plan to have migrations for remaining networks

  • POA
  • xDai
    on the 12th of December after Mainnet upgrade.
    We will notify the validators on the 5th of December.

Vadim @varasev , Pavel @phahulin , and Andrew @AndrewG will coordinate the protocol upgrade.

@AndrewG please add dates to the Events page in GitBook and https://coinmarketcal.com/en/

Check out what’s new in the Istanbul protocol upgrade:



Tracking comment

:white_check_mark: Igor Barinov
:white_check_mark: Ian Ferrell
:white_check_mark: Stephen Arsenault
:white_check_mark: Oxana Kunets
:white_check_mark: John H. LeGassic
:white_check_mark: Ilmira Nugumanova
:white_check_mark: Jim O’Regan
:white_check_mark: Michael Milirud
:white_check_mark: Xiaobo Chen
:white_check_mark: Irvin Cardenas
:white_check_mark: Adam Kagy
:white_check_mark: John Storey
:white_check_mark: Sviataslau Vishneuski
:white_check_mark: Kristina Yevseyeva
:white_check_mark: Kiryl Ihnatsyeu
:white_check_mark: Alexey Emelyanov
:white_check_mark: Siarhei Barylau

1 Like

@poa-validators please don’t forget to update your Sokol node and spec.json before December 5th using the above instruction.

1 Like

Updated and verified Jim O’Regan Sokol Validator Chicago A.

Please don’t forget to update Chicago B before Dec 5th too

@ftl_C-Ian (Ian Ferrell) please check your Sokol and Core nodes - they are offline at the moment.

Thanks for the heads up, they’re back up.

updated my node “Adam Kagy Sokol Validator”


Updated and verified Sokol node: “Irvin Cardenas Validator”.


Sokol Validator Chicago B will be shut down until after the hard fork, at which time two different redundancy methods will be tested. For now, please list my Sokol Validator updates as complete. Thanks and good work everyone!

Istanbul was activated successfully.

@kristina @johndangerstorey your validator nodes & @igkirill your bootnode fell out of consensus. To update them now, follow the same procedure, but after step 11 before step 12 additionally run

./parity --config node.toml db kill

It will clear the blockchain database and start a resync which can take some time, so steps 14, 15 will not work immediately.