The zaps must flow.

It's been some time in the making, but our latest major release, SeedSigner v0.6.0, dropped last night and it's a monster...
https://video.twimg.com/ext_tw_video/1628174326712213506/pu/vid/1920x1080/3DrwLqn8iZmNDTOn.mp4
This release has been ~8 months in the making and includes work from more contributors than any other previous release.
0.6.0's marquee feature is SeedSigner OS, that includes a custom Linux kernel created using Buildroot (https://buildroot.org).
(big kudos to #[0] & #[1] for all of their work on this amazing leap forward for our project!)
SeedSigner OS's key features include:
. Remove microSD after start-up
. Networking/BT/swap/usb removed from kernel
. Deployment image is ~100x smaller
. Build from scratch with minimal commands
Other new features in 0.6.0 include:
. Receive/change address explorer
. BIP-85 deterministic seed derivation
. p2tr (taproot) signing
. Compact SeedQR enabled by default
. MicroSD removal & reinsertion notification
. Keeper coordinator option
. Various UI tweaks & minor bugfixes
SeedSigner OS may also open the door for some interesting new features down the road, possibly including reproducible builds, PSBT transfer via MicroSD, and others... 🤞
Many of us are also very excited about #[2] ’s work on NIP-26 delegated signing using SeedSigner — many of the improvements to our current feature set will serve to enhance that functionality if/when it is introduced.
If you are receiving value from SeedSigner, or just appreciate the importance of the things we’re working on, please consider zapping this note. This Nostr profile is configured to route lightning payments to our development fund, the proceeds from which are distributed to our contributors:

Btw, I’ll be making an announcement soon on our next disbursement from the development fund for our contributors, stay tuned.
In the meantime, a big thank you to ALL of our contributors -- SeedSigner is an amazing FOSS tool that's been built for, and by, the bitcoin community.
Download link for 0.6.0:
https://github.com/SeedSigner/seedsigner/releases/tag/0.6.0
More info on our project at https://seedsigner.com & https://github.com/SeedSigner/seedsigner/
BIG🧡 to all of you!
Great release! BIP-85 support is sweet.
One issue though, is that when I try to export a taproot xpub, it gives an xpub rather than a zpub, and the addresses all start with 1 rather than bc1p. 0.5 did this too.
I’m not a technical person, but if anyone out there can speak to this, I’d love to know if this could be done. #[3]
If I’m a Christian missionary somewhere Christianity is banned, I don’t want the police to be able to log in with my npub and see who I’m talking to, even if they can’t read the content.
Interesting. This is what I wanted to ask. Seeing this answer makes me wonder: does fedwire have a fee market or it is first-come-first-served?
Someone might not even want people to know that the conversation is even happening. But could something like an HD wallet fix this? Say I want to DM you. I send you a message from a new npub that only exists for the purpose of initiating a conversation with you. Part of the message is proof that I have the key that controls my public-facing Nostr account, and part of the message is another new npub that you can respond to if you choose. If you respond to my message to you, you send the message to that npub, from a new npub of your own with proof that you have the key that controls your public-facing npub. Now we are chatting using npubs that only you and I know about. The only thing anyone else can see is that you received a message from an unknown sender. No one knows who that message was from or even if you responded. I’m not a coder, but it seems like this could be done. Or am I way off?
Would something like an HD wallet fix this? Say I want to DM you. I send you a message and part of the message is proof that I have the key that controls my public-facing Nostr account, and part of the message is a new npub that only exists for the purposes of my conversation with you. If you respond to my message to you, you send the message to that npub, from a new npub of your own and proof that you have the key that controls your public-facing npub. Now we are both chatting using npubs that only you and I know about. The only thing anyone else can see is that you received a message from an unknown sender. No one knows who that message was from or even if you responded.
Wait, are people already getting bored of monkey jpgs on the time chain? I thought we were never supposed to clear the mempool again.

Tell me you’ve made it big (i.e., added value to the Bitcoin circular economy) without telling me you’ve made it big.
Lol. I had noticed that.
Or is it more? I would imagine each relay you’re connected to is a potential leak of info. VPN is probably a must.
I wonder about the safety implications, though. How much about ourselves are we doxxing on Nostr, and who can see it?
