Replying to page394

#[4]​ consider removing option to export nsec key that was imported via this cold import method. See GitHub discussion with Vitor and Seth on the bounty.

Vitor said: “We need to figure out how to do that well. Right now there is no difference between this method and others... I am wondering if this should be inside the QR itself, as an NIP19 option.

…

I kinda want to make that a NIP to make sure the behavior is consistent with all apps. It feels weird to block the exporting of something the user knows the app has. I am sure this will trigger a lot of people in the wrong way. If people lose their keys on the main device, but have their keys inside Amethyst, do we just let them rot?”

Re:

#[5]

https://github.com/vitorpamplona/amethyst/issues/328

Avatar
jb55 2y ago

Exporting nsec in damus requires local authentication (faceid or pin)

Reply to this note

Please Login to reply.

Discussion

91
page394 2y ago

Yes but the point of this is to keep keys semi cold, not just transferring from one phone to another but from cold wallet to hot app

Avatar
jb55 2y ago

how cold is it when the nsec is on the screen

91
page394 2y ago

Lol “semi” cold

91
page394 2y ago

I mean nip 26 sounds a lot better all around. What can I do to push that forward, any bounties?

#[5]​ #[6]

Avatar
Seth For Privacy 2y ago

Planning on opening a bounty tomorrow for this in Amethyst, have some ideas on ideal flow!

91
page394 2y ago

Maybe an advanced option when signing in, irreversible, ‘mark nsec as cold import’ switch to disable export for this particular case and users who want that