5.0.0 RC3

5.0 Release Candidate 3 reference protocol client release. It has recent 4.0.104 codebase merged, and also PaiNet settings.

Ergo Protocol Reference Client 4.0.104

Ergo protocol reference client 4.0.104

• #1636 - BIP-32 secret key derivation is fixed in ergo-wallet library (only, a fix in the node is still not deployed)
• #1848 - SIGTERM now handled in the same way as /shutdown command
• #1858 - fixed height for EIP-37 activation is considered now, mining node not voting for EIP-37 if voting epoch start is not proposing vote for parameter #6
• #1864 - improvements and fixes in mempool (check for duplicates in mempool transaction collections, invalid transactions checks moved to p2p layer).

Contributors: @greenhat , @kushti , @pragmaxim

Ergo Protocol Reference Client 4.0.103

This version allows to vote for EIP-37 activation even if first block in a voting epoch is not proposing it.

It is also auto-voting for EIP-37.

Remove voting (ergo { voting ...) section completely from your config if you want to auto-vote for EIP-37, otherwise your voting section will override default one!

Please note, voting verification and activation is the same as in 4.0.100 and newer versions. This version allows to start voting within voting epoch as it is allowed by voting verification rules

Ergo Protocol Reference Client 4.0.102

Ergo Protocol Reference Client 4.0.102. It contains following changes:

• #1850 - In this PR, time limit for block sections processing in ModifiersFromRemote handling removed. That limit created temporary sync stop near blockchain tip, which is during slow blocks makes people think that sync is stuck.

This version is not auto-voting for EIP-37. To auto-vote, use 4.0.103 https://github.com/ergoplatform/ergo/releases/tag/v4.0.103 .

Ergo Protocol Reference Client 4.0.101

This version is 4.0.100 with auto-voting for EIP-37 inbuilt.

Ergo Protocol Reference Client 4.0.100

This release contains support for implementation and activation of EIP-37 as described in ergoplatform/eips#79.

Activation: it is possible to activate EIP-37 after block # 843,776 and before block # 942,081 . For activation, 232 or more votes for activation required in last 256 blocks, with voting checked every 128 blocks (for blocks which height % 128 == 1), and immediate activation once threshold is met.

Note: previous versions can be thrown from the blockchain in case of EIP-37 activation! Thus update to this version is highly recommended.

To vote for EIP-37, set in the config:

ergo {
...
  voting {
    6 = 2400 #vote for EIP-37
  }
}

Please use only this value (2400) for parameter #6 !

Alternatively, version 4.0.101 which is doing auto-voting, can be used: https://github.com/ergoplatform/ergo/releases/tag/v4.0.101

Also, in this PR:

• offlineGeneration is now true by default for the mainnet (which is what is needed by the pools all the time)

Ergo Protocol Reference Client 4.0.46

Ergo protocol reference client 4.0.46. It contains following PRs included:

• #1821 - the node now shows public REST API URLs of other nodes, if own REST API URL is not set
• #1838 - optimizations and transaction weight fixes done for chained transactions in the mempool
• #1840 - performance optimizations for AVL tree operations validation during block processing

Ergo Protocol Reference Client 4.0.45

Ergo protocol reference client 4.0.45. It fixes spam attack vector against p2p network: a peer can announce valid block section id with improper type, and then the node will try to re-download it from the peer and then random neighbours, penalizing them all on the way, and traffic spike happens as well.

Since this version, the node forget about block section with improper type asked, and also do not serve other peers asking for such block sections (helping peers of older version to avoid unnecessary traffic).

Ergo Protocol Reference Client 4.0.44

Ergo protocol reference client 4.0.44. It contains two bugfixes on top of 4.0.43:

• proper modifier type in broadcasting new block invs
• fixed "ErgoReadersHolder got improper input" message in logs

Ergo Protocol Reference Client 4.0.43

Ergo protocol reference client 4.0.43. It contains:

• #1830 - different optimization for node bootstrapping, as well as a fix for out-of-memory issue during bootstrapping
• #1834 - fix for REST API URL validation
• #1825 - fix for OOM issue wrapped by Guava cache ( #1824 )

Contributors: @kushti , @pragmaxim