Releases: ergoplatform/ergo
Ergo Protocol Reference Client 5.0.22
What's Changed
- Add excludeMempoolSpent Query Parameter to /blockchain/box/unspent/byAddress by @anon-yum2 in #2131
- Fix for duplicates in /blockchain/boxByAdress results #2167
- Fixes for IndexedErgoTransaction format and double quotes in examples by @kushti in #2176
New Contributors
- @anon-yum2 made their first contribution in #2131
Full Changelog: v5.0.21...v5.0.22
Contributors:
@anon-yum2 , @jellymlg , @kushti
Ergo Protocol Reference Client 5.0.21
Ergo reference protocol 5.0.21
- #2100 - fix for large integer overflows in swagger-ui
- #2113 - refactoring of Message class hierarchy (p2p messages)
- #2116 - a fix for ErgoStateContextSpec sporadic failures
- #2119 - better error message for wallet unlocking failure
- #2125 - token burning added to panel UI
- #2132 - ergo-core tests reffactoring
- #2135 - fix for ergo-core publishing in build.sbt
- #2139 - fixes for integrations tests
Contributors: @ccellado @deadit @salmanahmad22 @SethDusek @stenolog
Ergo Protocol Reference Client 5.0.20
Ergo protocol reference client 5.0.20 release. It contains following PRs:
- #2102 - fix for binaries auto-publishing
- #2103 - refactoring and documentation for ergo-core module
- #2104 - more tests for ContextExtension semantics
- #2109 - fix for proofsHash related sporadic concurrency bug
- #2110 - fix for limit in chainSlice API method
and README updated with modules info
Ergo Protocol Reference Client 5.0.19
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
andoffset
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