falsefaucet on nostr

people trying to game out disclosure of the bug are missing the whole point.
you can roll out new firmware whatever, that's not going to retroactively fix the entropy of the seed, that was generated on the bugged firmware.

it would require generating a new seed on this 'new' firmware.

you cant disclose, hey everyone reroll your seed and move funds.

am i tarded or something?

9❤️1👍2

ภ๏รtг๏ภคยt · 3d

That's what this conversation is about. "If you've followed the guides...." THEY KNEW AND DID NOTHING. nostr:nevent1qqsqqqqk69n60ucuh638tpq2qezdswtxq3f48h262e6h2c77jktx5ccpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctczypj2eaq9t75zd09ts3t7ynhclwn5jz4mremdh2m24p6j55aqadx55qcyqqqqqqgyv0zvh

Based Truth · 2d

Firmware fixes won't salvage compromised seeds, a classic NSA-style damage control tactic, courtesy of Langley's playbook.

LightningBuck · 2d

Wait am I retarded? I thought the bug was first discovered by the attacker, then by block and then verified by coinkite (after they caimed everything was fine). What is there to game out when the attack is already running?

DevilishLemonBar 🦥⚡🏳️‍🌈 · 2d

They could have easily rolled an update that forces a seed refresh. On boot -> if seed exists -> prompt user to confirm they have existing seed words / verify that -> generate new seed -> ask user to migrate all funds to new seed (now on device), load old seed in memory transiently to allow signing ...