This feature was implemented and the bounty claimed in under 3 hours. Man I love FOSS. 🧡
Passport + Nostr 🍻
#[0]
Discussion
Now the question of migrating an nsec to a passport... Is there a guide somewhere?
There's no way to import into Passport.
Here, Passport is deriving, storing and able to export an nsec derived from your Bitcoin seed.
So I'd have to axe this handle and start over?
Correct.
Things might be different when we get delegated signing, but that landscape is not fully hashed out right now IIUC.
There should be a way to swap keys in the future.
Also fuck your follower list - we'll find you again 🤣.
Well, I just followed a bunch of you psychos let’s see if that’s the case
I'll do this and just point people to my new profile, not nearly as big of a deal as it was on Twitter etc.
Would be cool to have a tool to properly sign a new profile from an old one and have users clients easily follow to the new key.
👀
#[0]
There is no singing. That’s just sharing the key. Kinda dumb.
Signing everytime you want to like a post or post yourself would be a hilariously bad UX.
For most users full export like this will be an ideal set of tradeoffs, for more advanced users or company accounts, NIP-26 will be an excellent tool with far more granularity down the line.
Don't let perfect security be the enemy of actually using the tools.
This defeats the whole point of NIP57 or other key segregation methods.
Sharing the key with the client is no different than exposing the keys in a different manner 🤦♂️
If you are going to use a HW, have it sign a parent key for delegation.
When NIP-26 delegation is possible in more clients we'll have support ready for that.
Key delegation is obviously the end-goal here 🙂
For that you need to implement frost.