<oembed><type>rich</type><version>1.0</version><title>Willheim wrote</title><author_name>Willheim (npub1th…4zcux)</author_name><author_url>https://nostr.now/npub1thljewtf8rgskx8y2w5lgddtydzu7nqx6mvhwp96du8sf6s8a43qr4zcux</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>So weird to see so many blaming the CC and looking for a new device where they&#39;ll just practice the same poor security hygiene.  My advice to one panicked soul:&#xA;&#xA;Don&#39;t waste money on a  new device.  There&#39;s nothing wrong with using whatever CC model as a signer  The issue was in trusting the RNG to create the seed.  &#xA;Move your coins to a Sparrow wallet(s). Create first. &#xA;Test receive. &#xA;Delete. &#xA;Recover. &#xA;Test send back. &#xA;Full move.  &#xA;Wipe CC. &#xA;Update with new firmware. &#xA;Roll dice (don&#39;t trust RNGs anywhere on any device). &#xA;Add 6-8 word passphrase.&#xA;Import seed. &#xA;Test receieve. &#xA;Delete. &#xA;Recover. &#xA;Test send. &#xA;Move back.  &#xA;Use the CC as the air gapped signing device it was meant to be. &#xA;&#xA;Takes about 2hrs depending on the mempool and you can be rolling dice while waiting for test sends/receives.  &#xA;&#xA;Bonus: you get to practice UTXO hygiene at the same time! (Which you&#39;ve probably been ignoring for too long). &#xA;&#xA;</html></oembed>