The fatal commit https://open.substack.com/pub/btcpp/p/when-randombytes-runs-but-doesnt?utm_source=share&utm_medium=android&r=3r59

hashing and trusting are one-way functions.

abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon abandon

https://engineering.block.xyz/blog/predictable-rng-fallback-and-32-bit-reseed-in-coldcard-firmware

https://rlcore.ai/blogs/The-LLM-revolution-is-a-Computer-Science-revolution

Reposting again, because this is what I am focused on.

https://aeon.co/essays/are-we-witnessing-the-end-of-the-technocratic-international

https://open.substack.com/pub/ecosystemoperator/p/money-is-a-coordination-technology?utm_source=share&utm_medium=android&r=3r59

GN

F*** this.

Don't influence. Verify.

My bet this attack was weeks in the making. Once the attackers assembled enough private keys for high value utxos they executed. My biggest disappointment is relying on a hardware vendor that has 'Don't Trust. Verify.' plastered all over their product marketing and the primary motivation that led to the bug was a 'get out of open source' licensing issue. Let this be a lesson for all in the industry. 'Not your keys, not your coins' rings a bit hollow now. It's more like: 'God plays dice for those who self-custody.'

Me neither. Just trying to recover at the moment.

Yes, that ship has sailed.

This is the Ford Pinto moment for the Bitcoin hardware wallet industry. https://en.wikipedia.org/wiki/Ford_Pinto

I agree with you, wholeheartedly. Focused on recovery/migration first, rage/vengeance will then follow.

I generated my seed with firmware v3.1.9 (2020) and upgraded after the fact. I have taken all of the migration measures, but I might be ok

I notice that and websites are no longer considered as secure in the Google Chrome Browser. Any idea ? #asknostr