read.cash is a platform where you could earn money (total earned by users so far: $ 813,254.74).
You could get tips for writing articles and comments, which are paid in Bitcoin Cash (BCH) cryptocurrency,
which can be spent on the Internet or converted to your local money.
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.
BCHN users should consider this update as mandatory prior to May 15, 2021.
You do need to upgrade if you are running an economic node such as an exchange.
This is still a network upgrade, although not a fork.
The upgrade affects which transactions are accepted into your node's mempool, so as an exchange you want your nodes to adhere to the same rules about this as the rest of the network.
Also, the v22.x.0 will expire its RPC functionality on May 15, 2021 unless an override parameter is given - so we highly recommend to upgrade to v23.0.0 well ahead of that date.
If you have further questions, please join our Slack to discuss, the invite link is:
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!!!
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):
the unconfirmed chain limits (this is not a HF, but needs some coordination to avoid problem for 0-conf transactions during the activation)
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.
On which block number this fork will take place?