pull down to refresh
792 sats \ 2 replies \ @petertodd 15 Feb 2023 \ on: What are you working on this week? bitcoin
Among other things, I contacted almost every pool I could find to pitch them on running full-rbf.
Good example of how Bitcoin really works actually: Core developers don't have any direct power. To make something change, users and miners have to be convinced to run new code and/or change configuration options. In some cases, not very many people have to be convinced: full-rbf just needs a few miners opting in to be useful. In other cases, pretty much everyone needs to be convinced: tail emission isn't going to happen without a hard fork and wide support.
https://petertodd.org/2023/why-you-should-run-mempoolfullrbf
Of course, I'm personally being sued by Craig Wright, who claims I among other people can give him coins that he claims are stolen (with zero hard evidence). It's a laughable lawsuit: can't even get full-rbf widely enabled without convincing a lot of people. 😂
Just so you know, if the courts order you to make a change to Bitcoin Core to reassign UTXOs to a fraudster, I will 100% definitely not be running that code. 😆
reply
It's probably helpful if more people make clear statements like this. So thanks.
In any case, at the moment it would not only be morally wrong to write that node. It might even be legally dangerous: there's every reason to think those coins aren't his. So by writing that code you could arguably be participating in theft.
reply