Ergo Protocol Reference Client 5.0.18

Candidate for 5.0.18 release. It contains following PRs:

• #2085 - do-release.sh script which is ensuring that proper Java version was used to build .jar and also that version in config files is corresponding to release git tag
• #2087 - first IPv6 seed node added to the seed list
• #2088 - fix for block sections hashCode() (caused issues in NiPoPoWs comparison)

Contributors: @kushti , @ross-weir

Thanks @satsen for proposing new seed node and testing

Ergo Protocol Reference Client 5.0.17

Ergo Protocol Reference Client 5.0.17 reference client release. It contains following PRs:

• #2054 - by default, 7 days of logs stored now by default (instead of 30)
• #2059 - tests for collecting storage rent from utxos with invalid ergo-tree
• #2060 & #2070 - ergo-core module extracted (with dedicated publishing), containing PoW, NiPoPoWs and other basic functionalities for building alternative clients
• #2074 - limit and offset parameters added to /wallet/boxes/unspent
• #2078 - extra indexer reworked, to fix issues with missing tokens and indexer being stuck

Ergo Protocol Reference Client 5.0.16

5.0.16 release, contains only update of sigma-state dependency (https://github.com/ScorexFoundation/sigmastate-interpreter/releases/tag/v5.0.13) which is fixing serialization bug happened in previous version (fix: ergoplatform/sigmastate-interpreter#941).

Update for 5.0.15 to this version is mandatory for miners and recommended for others. Update from other version is not strictly needed.

Ergo Protocol Reference Client 5.0.15

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

• #1456 - /script/p2shAddress API method which is generating P2SH for a script provided is enabled again
• #1907 - /scan/p2sRule API method added which is allowing to track boxes associated with a P2S address
• #2029 - /blockchain/box/unspent/byAddress and /blockchain/box/unspent/byErgoTree can now also include mempool boxes, see new includeUnconfirmed flag
• #2033 - estimated next block header is now used in mempool and API validation
• #1959 & #2048 - simplified p2p logic - lastStoredActivity time field now removed from ConnectedPeer
• #2036 - IndexedErgoBox API schema fixed in openapi.yaml
• #2040 - ErgoTree interpreter and ErgoScript compiler updated to 5.0.12 version, its release notes @ https://github.com/ScorexFoundation/sigmastate-interpreter/releases/tag/v5.0.12
• #2042 - /utxo/withPool/byIds API method added to get multiple boxes from the current UTXO set and mempool
• #2043 - /blocks/headerIds API method added to get multiple full-blocks for given header ids
• #2044 - new API methods /blockchain/box/byTokenId/{tokenId} and /blockchain​/box​/unspent​/byTokenId​/{tokenId} to track tokens

Contributors: @aslesarenko , @ccellado , @jellymlg , @kushti

Ergo Protocol Reference Client 5.0.14

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

• #2008 - ChatGPT plugin for API, see hackernoon article for details
• #2012 - improving CPU footprint of offchain transactions processing
• #2021 - the client now dropping connections with peers having version < 4.0.100
• #2022 - the client is now reporting to peers if it was bootstrapped via UTXO set snapshot
• #2024 - dropping connections to local networks (if localOnly == false , which is by default)
• #2025 - more descriptive comments for Extension section of a block
• #2027 - sigma interpreter updated to 5.0.10 (release notes)
• #2028 - readme updated with information on running the client in different modes etc

Contributors: @aslesarenko , @glasgowm148 , @jellymlg , @kushti , @pragmaxim

Ergo Protocol Reference Client 5.0.13

It contains following PRs:

• #1937 , #2017, #2018 - headers - chain bootstrapping via NiPoPoWs. Bootstrapping is configured via ergo.node.nipopow section:

    # settings related to headers-chain bootstrapping via NiPoPoWs
    nipopow {
        # Download PoPoW proof on node bootstrap
        nipopowBootstrap = false

        # how many different proofs we are downloading from other peers
        # and comparing with each other, before choosing best one
        p2pNipopows = 2
    }

You can use NiPoPoW-based bootstrapping with UXTO-set snapshot based bootstrapping or stateless client mode with keeping less than 52,224 full blocks suffix. The latter mode is not tested and not recommended now (will be tested and polished in next versions).

To combine NiPoPoW-based and UXTO-set snapshot based bootstrapping, set

ergo.node.nipopow.nipopowBootstrap = true
ergo.node.utxo.utxoBootstrap = true

• #2009 - fixed /blockchain API paging - fixed an issue with address segment paging that happened when the first segments were retrieved. The bug caused duplicate segments the be returned.

There is no need to update nodes to this version for miners and exchanges!

Contributors: @ApexTheory , @kushti , @jellymlg

Ergo Protocol Reference Client 5.0.12

5.0.12 release. It contains following PRs:

• #1985 & #1444 & #1999 - support for bootstrapping with UTXO set snapshots

creating and using UTXO set snapshots is configured via new ergo.node.utxo section:

ergo {
  ...
 node {
  ...
    utxo {
        # Download and apply UTXO set snapshot and full-blocks after that
        utxoBootstrap = false

        # how many utxo set snapshots to store, 0 means that they are not stored at all
        storingUtxoSnapshots = 2

        # how many utxo set snapshots for a height with same id we need to find in p2p network
        # in order to start downloading it
        p2pUtxoSnapshots = 2
    }
  }
}

If ergo.node.utxo.utxoBootstrap is set to true, the new node will download headers in the first place, then ask its peers for UTXO set snapshots and when p2pUtxoSnapshots same snapshots found around, download their chunks, restore UTXO set and apply full blocks after the UTXO set. As UTXO set snapshots stored every 52224 blocks, please do not try to bootstrap with UTXO set snapshot before height 1,044,480 (there are only two nodes having some snapshots before that height, so little chance to get snapshots from them)

There's also new API method /utxo/getSnapshotsInfo which returns information (height and id) about stored UTXO set snapshots.

• #2003 - sigma interpreter update to 5.0.8

There is no need to update nodes to this version for miners and exchanges!

Contributors: @aslesarenko , @kushti

Ergo Protocol Reference Client 5.0.11

Ergo protocol reference client 5.0.11 release. It contains following fixes and features:

• #1975 - optimizations for wallet scan operations
• #1993 - automatically substitute version into configuration files
• #1998 - specific API error if extra indexes not enabled, but related API methods called
• #2002 - fixing recently introduced API methods not accepting JSON (now both JSON and plaintext options supported for them)

Contributors: @jellymlg , @kushti

Ergo Protocol Reference Client 5.0.10

Ergo protocol reference client 5.0.10. It contains following PRs:

• #1960 - another part of bootstrapping from UTXO set snapshot code (not affecting observable behaviour of the client)
• #1978 - new /wallet/getPrivateKey API method to dump private key bytes for a pubkey, if the wallet knows it (and unlocked). Example request is curl -X POST "http://213.239.193.208:9053/wallet/getPrivateKey" -H "accept: application/json" -H "api_key: hello" -H "Content-Type: application/json" -d "{\"address\":\"9fLbJ9eThdC2PyzZUgR9E97ejhWCtmYVni6kn3LRBy9WcvJ3bCg\"}"
• #1984 - ErgoTree interpreter and ErgoScript compiler updated to 5.0.7
• #1988 - fixes in additional indexes , such as fixes for paging in /blockchain endpoints

Contributors: @aslesarenko , @greenhat , @jellymlg , @kushti

Ergo Protocol Reference Client 5.0.9

Ergo protocol reference client 5.0.9. Only nodes maintaining additional indexes (introduced) do need to be updated. The release contains following PRs:

• #1957 - speeding up storage rent related checks
• #1971 & #1983 - fixing indexer issues (for additional indexes)

Contributors: @jozanek , @jellymlg