pull down to refresh
Yeah, and it might also be a more interesting format for those that feel the Optech Recap is too technical or too long.
Maybe there is no wallet software that implements it, yet? Knots might have it, but they may have just introduced it on protocol level and not as a wallet feature, yet. Also, it is hard to import funds from mnemomic-based wallets into Bitcoin Core, so presumably the same is true for Knots.
From what I understand: they will be offering closed source binaries reproduced and signed by multiple developers for anyone that wants to upgrade immediately and resume running their node. For people that don’t want to upgrade to a closed source binary, they recommend to restart with --offline. The source code will be published two weeks later and allow anyone to verify that the released binary was reproducibly built from the later published source code.
The source code is being held back to make it harder for attackers to discover the vulnerability while people upgrade. This sort of situation is complicated and difficult, but their solution doesn’t require you to run closed source binaries if you don’t want to.
I spent 11th grade abroad. I was expecting things to be different on going abroad and the culture shock was quite manageable. I didn’t expect the reverse culture shock when I returned after missing a year of high school, especially the year that people turned 17.
Now that I’ve been living abroad for over nine years, some things also surprise me when I visit. You don’t really explicitly know the things you got used to abroad that just aren’t so back home.
The best would have been if Luke had resigned any time after stopping to perform the BIP Editor work. I had publicly asked for his resignation after him trying to assign a BIP number on Twitter for a BIP that hadn’t even been sent to the mailing list.
If we had removed Luke in the past few months, people like Giacomo would have said it’s retaliation for championing BIP110 or for calling us pedos all the same.
After not doing anything for years, all the crap he pulled, I don’t see how it would have been tenable to keep Luke on after he additionally announced his departure from Bitcoin development.
https://x.com/LukeDashjr/status/2086645671914840081
So, I’d be curious to hear what would have been a better time to remove Luke. What additional events would you have waited for, or which criteria would you have used?
I listed some other grievances in my second email on the mailing list thread: https://groups.google.com/g/bitcoindev/c/knbv3MFwlvU
E.g., when the Taproot authors wanted to amend their BIP to propose a deployment mechanism, he obstructed the update even after all three authors had signed off on it, because he favored a different deployment mechanism. He had also done next to no BIP Editor work in five years. If you don’t do the work, you don’t need the privileges necessary to do the work.
Yeah, we cracked 2.5h again this week.
Sometimes I think that our Optech episodes could provide higher value to our listeners if there was more post-production. I haven’t listened to ourselves in a long while, but I’m sure that there would be room for improvement by cutting a bit here and there.