Ergo Protocol Reference Client 5.0.2

Ergo Protocol Reference Client 5.0.2 release. It contains following PRs:

• #1874 - aarch64 support for the Docker image, some minor fixes in image config
• #1882 - API now returns 400 for non-existing endpoints and 404 for non-existing resources
• #1887 and #1890 - optimizations in transaction assembly

Contributors:

@pragmaxim , @reqlez

Ergo Protocol Reference Client 5.0.1

This release contains only Sigma interpreter update to 5.0.1, which is fixing breaking changes in 5.0.0 serialization ( ergoplatform/sigmastate-interpreter#836 and ergoplatform/sigmastate-interpreter#837 )

Ergo Protocol Reference Client 5.0.0

5.0.0 release. It contains Sigma interpreter 5.0.0 https://github.com/ScorexFoundation/sigmastate-interpreter/releases/tag/v5.0.0 , new PaiNet testnet settings, and also EIP-39 (monotonic creation height rule) implementation:

• #1865

Note: this version has issue with processing mainnet block #855,650, update is not recommended

Ergo Protocol Reference Client 4.0.105

Ergo protocol reference client 4.0.105. It contains following PRs:

• #1841
• #1875

In this version, rare improper BIP-32 seed secret generation from mnemonic (with 1/256 probability) is fixed. New wallet initialization is now using a new fixed procedure. For restoring the wallet, it is possible to use old derivation (the flag is off by default, as with 255/256 probability new derivation is compatible with old one)

• #1869

New API methods to work with mempool transactions: /transactions/unconfirmed/{txId} , /transactions/unconfirmed/byTransactionId/{txId}, /transactions/unconfirmed/byErgoTree, * /transactions/unconfirmed/inputs/byBoxId/{boxId}*, /transactions/unconfirmed/outputs/byBoxId/{boxId}, /transactions/unconfirmed/outputs/byErgoTree, /transactions/unconfirmed/outputs/byTokenId/{tokenId} , /transactions/unconfirmed/outputs/byRegisters

• #1867

If the node is being asked by another peer about known peers, it now returns only peers recently connected

• #1871

Some GET methods in /utils API are having POST counter-parts now, to deal with potentially long p2s address strings, New POST methods are /utils/address, /utils/ergoTreeToAddress

• #1873

New ergo.wallet.profile setting now defines a wallet profile, which shows what kind of load is expected. Possible setting values: "user", "exchange", "appServer"

Contributors: @greenhat , @jellymlg , @kushti , @pragmaxim

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)