Nominal amt of sats to post seems like it would go a long way to resolve the spam issue. Pretty painful right now.

SMH, LoL.

Hmmmmm... have to phone-a-friend on this. Any idea @newtonick ?

Agree.

For sure, thanks for checking into it -- give this one a try:

At some point, Nunchuk stopped supporting static XPUBs. If you change your SeedSigner to the Sparrow export setting, it will animate the QR code that depicts the XPUB and the rest should work fine. I ran into this a couple of weeks ago as well.

Functioning DM notifications.

👀

I'm just going to agree to disagree with you here. I strongly disagree with what you’re saying, but I just don’t have the time to refute every far fetched exotic attack scenario. Have a great afternoon.

I guess I feel like I've tried to talk about tradeoffs a lot and have always been willing to admit there are some use cases where a conventional hardware wallet makes a lot of sense. Meanehile some manufacturers constantly misrepresent our project for seemingly self serving reasons. But I understand it can be frustrating from someone with your perspective. I just don't know what the answer is.

All side channel attacks I am aware of require running software that has been maliciously modified. So to avoid that, run our released code.

Just so you know, that is not me. No idea who "Roberts" is. I was an LEO however, but have been very candid that digital forensics was my specialty. You should really double check it your sources, would have been easy to find this out.

This is the same as our approach. Boot from attached storage, then remove the storage device to show the system is probably running from RAM. SeedSigner is just a single purpose, hardened, verifiably offline computer.

nostr:nevent1qqsfp0n4l6z2rk86q4nnu4yuygvk4qjrymekkteq3mzsz5rxm7gs4cgpr3mhxue69uhkummnw3ez6un9d3shjtnhd3m8xtnnwpskxegpzamhxue69uhkummnw3ezuendwsh8w6t69e3xj7spramhxue69uhhyetvv9ujumn0v3jhyatwdejhyuewdejhgam0wf4szxrhwden5te0wfjkccte9eekummjwsh8xmmrd9skcjjkkmd

We trust the manufacturer to do a lot less. We don't trust the device to validate software, we don't trust it to persistently store keys, and we don't trust it to make wireless or wired connections with other devices. We just trust it to execute SeedSigner code.

As of right now, just one, but progress on more is ongoing. But you're missing the point, it's not worth it to target the entire RPi supply chain at this point, and even if you wanted to target individuals, less than 0.01% of RPi products likely will end up as SeedSigners, so who knows which ones to pick. Whereas, at a certain point in a HWW's life, it's known that the device will be used to store PKs, and an attacker further knows that just about every device is going to someone who will potentially use it for that purpose. Different tradeoffs.

Yup.

And we will continue to be here with a compelling alternative model, that requires much less trust in manufacturers and distributors.

With SeedSigner yes, but unfortunately BlueWallet does not support testnet. You can, however, go through the same workflow with either Nunchuk on mobile, or sparrow wallet on the laptop/desktop and use testnet. The experience with bluewallet is much the same.

A FOSS tool built by bitcoiners, for bitcoiners, shared one bitcoiner at a time. nostr:note1v3u89lyn49222g7mn48q278j73mvvhurz65hua96rftxk3s23x2sh0arzn

Thank you for sharing our project with the bitcoiners there. 🧡