Ergo Protocol Reference Client 5.0.8

Ergo protocol reference client 5.0.8. It contains following PRs:

• #1954 - fix in peer propagation - now the node is sending peers which were active recently (not just handshaked)
• #1963 & #1968 - fixes and improved performance for additional indexes

Contributors: @ccellado , @jellymlg

Ergo Protocol Reference Client 5.0.7

Ergo protocol reference client 5.0.7. It contains following PRs:

• #1859 & #1944 & #1950 - the node now supports additional indexes (to store information about all the transactions, tokens, UTXOs, not just wallet-related), and a lot of additional requests on top of them, see /blockchain API methods. Additional indexes are switched off by default, to turn them on, set ergo.node.extraIndex = true in the config, to check availability of additional data on a public node, check new "isExplorer" flag in /info output

• #1940 & #1947 - more code imported from bootstrapping-with-UTXO-set-snapshot branch, still refactoring mostly at this point

• #1943 - network time got from a trusted NTP server is not used anymore (in particular, it led to header-timestamp-in-future issues)

• #1945 & #1951 - hot-fixes for mempool inconsistency (see #1952 )

• #1946 - sigma dependency (ErgoTree interpreter and ErgoScript compiler) are updated to 5.0.5 (release details https://github.com/ScorexFoundation/sigmastate-interpreter/releases/tag/v5.0.5 )

• #1948 - cross-compilation of ergo-wallet submodule with Scala 2.13

• #1949 - scala-sbt image updated for Docker build

Contributors: @aslesarenko , @jellymlg , @kushti , @reqlez

Ergo Protocol Reference Client 5.0.6

Ergo protocol reference client 5.0.6. It contains following PRs:

• #1927 - preliminary code changes for bootstrapping with UTXO set snapshot
• #1934 - fix for log level set via .conf file
• #1936 - fix for confusing error message when boxes to be spent not available (for mempool transaction)

Contributors: @ccellado , @kushti

Ergo Protocol Reference Client 5.0.5

Ergo protocol reference client 5.0.5. It includes following PRs:

• #1918 - new log level configuration code and logback dependency update
• #1926 - sigma updated to 5.0.3 (with 4.x interpreter removed)
• #1929 and #1931 - fixes for invalidated transactions staying in the pool for some time and redownloaded again
• #1932 - improved messages when no inputs (or data-inputs) found

Contributors: @aslesarenko , @ccellado , @kushti, @oskin1

SHA-256 checksum (if built with Java8): ea8e27a378f534b43e9304432b7bc0853f67a98e9cc1492c4c0d8a8231dbd389

Ergo Protocol Reference Client 5.0.4

Ergo protocol reference client 5.0.4. In contains following fixes and improvements:

• #1831 - readme typo fix
• #1880 - no RegisterMessageSpec from Scorex used anymore, Ergo protocol messages are hard-coded
• #1891 - per-peer and per-block total computational cost limits for offchain transactions
• #1901 - new API methods /transactions/bytes and /transactions/checkBytes , to broadcast and check transaction given as bytes
• #1908 - unused code removed
• #1917 - warning note for height in /wallet/rescan
• #1922 - fix for #1920 , which caused mining pool reward payment failures, as pay-to-reemission output had creation height equal to 0

Contributors: @ApexTheory , @ccellado , @futuristudios, @kushti

Ergo Protocol Reference Client 5.0.3

Ergo protocol reference client 5.0.3. It contains following PRs:

• #1872 - slicing in /scan/unspent boxes by inclusion height
• #1894 - do not erase wallet password on init and restore before unlock
• #1895 - checkpoint added to testnet settings. As some v.3 blocks in the PaiNet are violating monotonic creation height rule (due to 5.0 being activated before the monotonic introduced), this checkpoint is mandatory
• #1898 - obsolete readme sections updated

Contributors: @kushti , @pragmaxim

SHA-256 checksum (if built with Java 8): 20302cb38a97dfda8fc8eb0fa55839cd4eb3abf415fd14e76c74c6565f5498e0

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