"Goodbye, cruel world" - A post-mortem on the retirement of bitcoincore-rpc, a beloved and long-standing fixture of the Rust Bitcoin ecosystem. https://t.co/YJ5rhtMrpJ
Join us this Wednesday at 17UTC to test Bitcoin Core v26.0 release candidates (and lots of exciting new features)! m3dwards has prepared a testing guide: https://t.co/RmxH5GDp5y
that require a supermajority of opt-in nodes in order to be extended. That way there's no ambiguity over when/whether we should upgrade, plus it gives people a deadline.
There should be little friction to testing new ideas/protocols and similarly no cost to rolling back the ones that fail to gain traction. This could be achieved through regularly scheduled (2-4 years) soft forks with an automatic sunset on experimental features
I don't normally have a problem getting confirmed on layer 1 and part of the reason is I don't try to predict what fees will be in 3-6 blocks, as doing so is akin to gazing into a crystal ball. Instead I aim to get into the next 1-2 blocks by meeting the market where it's at..
trade in financial markets, albeit with no guarantee of success. Still, I would see it as a win if such a model had a mean-reverting effect on fees rather than the runaway fee spikes we're accustomed to. Arguably the most reliable insight into the prevailing fee market
is to note the distinction between mempool policy and consensus. Nodes are free to tinker with their mempool, however there is value in converging on a set of standardness rules in that it creates a more robust and streamlined p2p network and more accurate real time fee reporting
If anyone hasn’t read/heard the Waiting for Confirmation series, that’s your homework for the weekend. Thanks a lot to @bitcoinoptech@murchandamus@glozow . One takeaway I have...