Share This Post

Share on facebook
Share on linkedin
Share on twitter
Share on email

In order to ensure the stability and security of the Pirl Network, the Pirl team has been working on a network update to geth version Iceberg² (1.8.1).
Besides the advantages of the new geth, diff. algo and monetary policy, this update will be the cornerstone of even more amazing updates and changes to the pirl network.After successful testing of the client with the implemented Pirl specific changes, we are one step away from  rolling out the update.

What’s New?

There are several bug fixes in the client concerning stability and network connections.
Together with the bugs fixed, some vital changes for the Pirl network will be implemented.
For more information check out the changelog below.

Key advantages and improvements with this update.

  • Faster transactions due to transaction signing method update and fixes on txpool:
    We had reports from the community that p2p transactions and pool transactions would slow down intermittently.
    With the update of geth, we expect that the transaction times of the pools and all other p2p transaction will be significantly improved.
  • Faster node synchronization :
    This feature brings a vital speed boost during the initial wallet sync by vastly improving the synchronization of the chaindata.
    For example :
    If you install the wallet on a new PC and start it for the first time, the wallet has to synchronize/download the whole chaindata file.
    In big chains like Ethereum or other coins this step could take a long time.
    With the geth update, the time required to sync will now be reduced and you can use your wallet faster than ever before.
  • Faster dead peer detection and peer connection/detection :
    We had reports from the community that the wallet would sometimes take a long time to connect to an active peer .
    The connection to a peer is vital for the wallet, because of the data/chain synchronization.
    With the geth update, we get a faster “dead peer detection” and “peer detection”, this allows the wallet to connect to active peers and start to sync much faster.
  • Stuck transactions problem fixed:
    Transactions that were previously getting stuck due to missing the target block will now be re-entered if not mined in the target block.
    This will resolve the issue with stuck transactions.
  • Upgraded difficulty algorithm codename AHAB
    With the update, a new algorithm, called Ahab, will be implemented to regulate and control the difficulty adjustment.
  • Lower disk usage and memory load on the desktop wallet
    With various tweaks, client performance and resource usage are optimized.
  • Monetary policy implementation from block 2,000,001
    With block 2,000,001 our monetary policy will start to take effect.
    Read more about our monetary policy in the article https://pirl.io/blog/pirl-monetary-policy/

When will the update roll out?

We are planning to roll out the geth update as soon as possible.
If you are just a pirl wallet user there is no immediate action required.
Pool or masternode owners will need to act as soon as possible due to the required changes.
With block 2,000,001 the chain will fork, pool or masternodes will not be able to interact with the main network without their geth or .bin updated.

What do I have to do as a Pirl user ?
As Pirl-user, you will get a wallet update which you will to install/update.
The wallet will notify you about a new update and guide you to the download location of the new update.
Just simply download and install and you are ready to go.

What do I have to do as a Pirl node operator ?
As node operator or pool admin you will have to update your geth.
If you don’t do this, pirl will fork and you will not be part of the main network.
It is vital that you update your geth-client at the time of the fork, which will be block 2,000,001.
The new pirl-geth client will be provided by our dev-team and will be available for download.

What do I have to do as a Masternode operator ?

The owners of a Masternode need to update their masternode by installing the new .bin on their masternodes.
This .bin file will be released at https://release.pirl.io .
We recommend that you install the new .bin file as soon as possible.
The updated bin runs faster, smoother and is ready for upcoming changes of the pirl network.

Make sure that you as masternode owners have the new binary installed before block 2000001, otherwise your payments will stop from this block forward



  • Preparing the 2m hard fork
  • Changed the fixed difficulty algorithm to an exponential algo
  • Fixed txpool problems
  • Fixed transaction handling and default values
  • Fixed handling of SIGTERM corresponding to SIGINT
  • Fixed writing / closing database correctly after shutdown
  • Compatibility for Go 1.10 has been enabled
  • Faster sync of nodes
  • Faster dead peer detection
  • Faster peer detection and connection


  • Fix log filtering when specifying non-8-multiple starting block number
  • Fix replacement transaction propagation
  • Reduce disk overhead on keystore startup
  • Fix occasional Rinkeby chain split by additional fork selection logic
  • Fix JavaScript tracing to permit working with Address types
  • Fix missing commit hash in docker image versions


  • VM tracing is much improved and supports tracing entire block ranges.
  • In transaction sending RPC calls, the “input” field can be used instead of “data”
  • The gas price oracle is improved to handle tx price surges better
  • The RPC server now protects against DNS rebinding attacks
  • The new personal_signTransaction method signs a transaction without sending it to the network
  • HTTP OPTIONS requests no longer require the Content-Type header
  • admin_nodeInfo returns the chain configuration in light client mode
  • debug_storageRangeAt returns RLP-decoded values
  • The peer discovery protocol removes dead nodes more aggressively
  • Discovery v4 and the experimental discovery v5 protocol now run on the same UDP port
  • Several issues in the experimental discovery v5 protocol are resolved


  • Fix two light client data races resulting in crashes
  • Fix a discovery issue that incorrectly measured peer bond time
  • Fix compilation on Go 1.10

Subscribe To Our Newsletter

Get updates and learn from the best

More To Explore