@bitcoincashnode
edited
more from that month
Announcing Bitcoin Cash Node v23.0.0
April 14, 2021 Release announcement: Bitcoin Cash Node v23.0.0 The Bitcoin Cash Node (BCHN) project is pleased to announce its major release version 23.0.0. This release implements the May 15, 2021 network upgrade. It contains the removal of the unconfirmed transaction chain limits, enabling of multiple OP_RETURN (while keeping the total size limit of data carrier), introduction of Double Spend Proofs (beta), a lifting of the default soft limit for mining to 8MB, and a number of bugfixes and performance improvements. BCHN users should consider this update as mandatory prior to May 15, 2021. This is because of the coordination of the new policy rules around transaction chain limits and standardness of multiple OP_RETURN. The v22.2.0 software will expire some functionality on May 15, and will start to warn about ahead of time, from April 15, 2021 onward. For the full release notes, please visit: https://github.com/bitcoin-cash-node/bitcoin-cash-node/releases/tag/v23.0.0 Executables and source code for supported platforms are available at the above link, or via the download page on our project website at https://bitcoincashnode.org For more information about the May 15, 2021 network upgrade, visit https://upgradespecs.bitcoincashnode.org/2021-05-15-upgrade/ We hope you enjoy our latest release and invite you to join us to improve Bitcoin Cash. Sincerely, The Bitcoin Cash Node team.
4 comments
Updates are always welcome
This is exciting news! No more chained limit, more op returns, and better scaling? Im seriously sorry I ever doubted you guys. This is the sh**t right here!!!
I do not disagree with the features. In fact they seem like good news to me. But... didn't you propose that the next update would be in May 2022?
The date of May 2021 was already encoded by ABC under the date & the name "Tachyon". We decided to use this date for the upgrade of the two aspects which does not modify consensus rules (so no hard fork split risk): 1. the unconfirmed chain limits (this is not a HF, but needs some coordination to avoid problem for 0-conf transactions during the activation) 2. the allowance of multiple OP_RETURNs (a change to standardness, i.e. affecting which transactions are normally accepted and relayed) However, we also proposed that the next date for a *consensus* upgrade be in May 2022 - that is correct and is our current perspective. There are a number of consensus changed being reviewed for May next year.