I a recent stream @ODELL pointed out something most self-proclaimed Bitcoiners seems to be unaware of. You don't HAVE TO update your nodes. If you're uncertain about what to do in regards to the op_return drama... don't update and let the mess play out. Some people still run core-17, true story.
Login to reply
Replies (5)
The 2 things this doesn't fix is:
- new & less competent users will just download the latest version of core or knots
- it doesn't send a strong message of I don't agree where core is headed
Long term, we need a fork of core that prioritises Bitcoin as money over all other BS. We can direct noobs to this software.
In the meantime I'd like to revert my version of core to an older version (I'm currently on V.28). This is purely to signal my dissatisfaction with Core rather than just indicating I'm slack with applying updates.
I'm not so sure we need developers working full time on Core.
What value did the last 5 updates deliver to node runners?
If it was easy to do, you would see more implementations already..
View quoted note →
Since v25:
Cutting initial blockchain download time in half, encrypting p2p communications, making lightning safer and cheaper to use, allow immediate bootstrap with assumeutxo, shipped better miniscript and descriptors support, easier compilation with cmake, fixed a bunch of CVEs that have been present since a long time, complete obfuscation of on-chain data, better coin selection, the mining interface for easy home mining with stratumv2, better and safer localnet hole punching with natpmp and pcp, and a whole bunch more.
You can read all about it at
.
Bitcoin Core
Releases
Releases