Damus
falsefaucet · 1w
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 ...
DevilishLemonBar ๐Ÿฆฅโšก๐Ÿณ๏ธโ€๐ŸŒˆ profile picture
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 the migration tx.

This is more jank tha it should because they don't have a first-party app. Something like Bitkey handled something similar in literally two clicks during the privacy upgrade update (which required a new 2-o-3 to be generated.
1
falsefaucet · 6d
But forcing seed regeneration would have been a HUGE red flag to anyone paying attention. And the commentator theory never mentioned anything other than a firmware update. I guess my point is if you are still listening to all these talking heads, half of them don't know what they are talking about...