Ergo Protocol Reference Client 4.0.26

Release 4.0.26. It includes:

• #1583 - SyncTracker optimizations (collections unification)
• #1612 - keepVersion is automatically set to 0 when chain tip is far ahead. This improves bootstrapping performance significantly.
• #1630 - optimized dumping of locally generated ADProofs sections into database
• #1649 - fix for transactions with estimated execution cost bigger than 1000000 are rejected since 4.0.23
• #1667 - new optional dustLimit setting to set threshold ERG value, if incoming box has less than the limit it will not be added to the wallet. This setting is good for exchanges to avoid spam.
• #1673 - use relative URL for default server in openapi spec
• #1679 - less verbose log output for uninitialized wallet
• #1680 - tests for headers coming out-of-order, small fix for headers application from cached
• #1681 - remove sigma-rust integration test files

Contributors: @kettlebell , @kushti , @pragmaxim , @ross-weir

EIP-27 Experimental Release Candidate 1 (RC1)

DO NOT USE THIS RELEASE FOR THE MAINNET!

This is experimental pre-release with EIP-27 support for the testnet.

Ergo Protocol Reference Client 4.0.25

Release 4.0.25. It includes:

• #1650 - fixing p2p errors with serving big modifiers
• #1655 - fixes and improvements in openapi.yaml
• fixed Docker publishing
• increased safety gap for the mainnet

Contributors: @pragmaxim , @ross-weir

Ergo Protocol Reference Client 4.0.24

Ergo Protocol Reference client 4.0.24. It contains following PRs:

• #1613 - UTXO set transformation proofs regenerated if announced hash differs from calculated one
• #1616 - the node is sending extension to peers on sync v2 protocol when fork is detected
• #1625 - extra check added to NipopowProof::hasValidConnections
• #1626 - publish docker image for sigma-rust integration tests
• #1637 - faster transaction processing (in ErgoState class)
• #1638 - reset delivery tracker when node may be stuck
• #1639 - limit for number of unspent boxes to be fetched in the wallet
• #1640 - caching for sync messages
• #1643 - optional checkpointing
• #1645 - fix for #1644: DefaultBoxSelector should collect needed inputs when needed for change in presence of assets

SHA-256 sum (if built with Java 8): badeb99797d75e5d9427179b714eb5e524c5875fe852e4e1fc2acf1ca20c961b

Contributors: @kettlebell, @kushti, @pragmaxim

Ergo Protocol Reference Client 4.0.23

Ergo Protocol Reference client 4.0.23. It contains following PRs:

• #1618 - fix for node being stuck in case of fork headers coming out-of-order (and other recoverable events)
• #1526 - batch Merkle proof for interlink vector (in extension, against a header)
• #1601 - transaction size now limited (the limit is 96 Kb by default), if transaction size is above the limit, it won't be accepted into memory pool (can be included into blocks still)
• #1585 & #1589 - API endpoint for delivery tracking
• #1597 & #1607 - minor memory optimizations
• #1602 - keepVersions parameter in versioned database made changeable

SHA-256 sum (if built with Java 8): 6690537cbf2084b3a8f02f720d47ca7a56e5a4897075500e81856faa6c49417a

Contributors: @ApexTheory , @knizhnik , @kushti , @pragmaxim

Ergo Protocol Reference Client 4.0.22

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

• #1540 - now wallet API supports burning tokens. Request example ( for /wallet/transaction/send ):

{
  "requests": [
    {
      "assetsToBurn": [
        {
          "tokenId": "4ab9da11fc216660e974842cc3b7705e62ebb9e0bf5ff78e53f9cd40abadd117",
          "amount": 1000
        }
      ]
    }
  ],
  "fee": 1000000,
  "inputsRaw": [ ],
  "dataInputsRaw": []
}

• #1569 - better logging and improved blacklist datastructures for the mempool

• #1579 - /script/executeWithContext is now executing a script exactly as in transaction validation

• #1584 - fixed float type input problems in Safari

• #1590 - fixing possible message queue overflow issue during active sync.

• #1593 - transaction generated with /wallet/transaction/send or /wallet/payment/send now checked like it is submitted into the mempool via posting to /transactions

• #1594 - small typo fix

SHA-256 sum (if built with Java 8): 63fc23475695cedbbdbe9614f029235902905580993533efd430de51e9274b0f

Contributors: @aslesarenko , @ccellado , @deadit , @kushti, @pragmaxim , @ross-weir

Ergo Protocol Reference Client 4.0.21.1

It was considered in p2p layer that any block section is no more than some limit, namely, 2MB. While this is true for transactions (where limit can be changed by miners though and so exceed 2MB) and extension section (10 KB max), there is no check for UTXO set transformations proofs (most of the nodes generating and not downloading).

It was the case that one transaction made 5K UTXOs https://explorer.ergoplatform.com/en/transactions/4268e2bf73cb9b8e7e36ed04da8fe6759dd723f164b3ca2ff43c3e406c9c6995 . Then a light client (working in "digest" mode) caused problems for public nodes storing UTXO set, as they did not considered violation of the rule and so stuck in endless loop.

This release relaxing the issue by making full nodes not stuck if they some have a block section more than allowed block section size. In this case the node is still sending it. On client side, there is some relaxation of the limit. However, to protect light clients fully we need to introduce consensus-level checks for UTXO set transformation proofs in a next soft-fork, or miners can vote on raising cost of an output.

Also, too much of syncing traffic appeared in the logs. This release tries to cool down syncing.

Ergo Protocol Reference Client 4.0.21

Ergo Protocol Reference Client 4.0.21. It contains following PRs merged:

• #1506 - transaction cost in mempool now limited (default limits are 800K for the testnet, 5M for the mainnet)
• #1563 - no global LaunchParameters used around the codebase anymore
• #1573 - node is now checking itself periodically for being stuck, printing debug information if so and also tries to repair db from one known issue
• #1574 - fixing logback oversized logfile issue
• #1575 - fixing errors in openapi.yaml
• #1580 - akka max uri length increased

Contributors: @kushti, @pragmaxim , @ross-weir

SHA-256 sum (if built with Java 8): 2025b61b2a2c1b02a9c5db0694abae4f2d22f9b92c7258070697491928549448

Ergo Protocol Reference Client 4.0.20.2

Ergo Protocol Reference Client 4.0.20.2. it contains:

• #1570 : randomized re-broadcasting, rebroadcasting transactions only if all the inputs are in UTXO set, decline but do not invalidate transactions if inputs are not in UTXO set

SHA-256 sum: 25c5448522cfb04a68f5b8c85afa09ec55328e8d829c93ff5838ca554e88a748
Contributors: @kushti

Ergo Protocol Reference Client 4.0.20.1

Ergo Protocol Reference Client 4.0.20.1. It contains:

• fix for inconsistent mempools #1565

SHA-256 sum: b8ab744cd29caa25e24f9327b20b94e5f4dd53216057b2a6e4a8eb152ffbb70b
Contributors: @pragmaxim