New #bounty alert: 750K sats to add nsec importing from QR code on #Amethyst's login page by #[0]

Tasks:

1. Add a leading icon on the Login's text field

2. Call the existing QR Code reader function

3. Enable extraction of the nsec from QR

4. Place it into the Login TextField

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

Reply to this note

Please Login to reply.

Discussion

Specific implementation requests from #[3] here:

#[1]

It needs to not be exportable again from the app if it’s imported this way

Maybe, but that is not required.

“When this approach is used, prevent export of the key in the app itself to provide better security around someone getting your nsec from your phone being open.”

?

Yep, for now the key should not be exportable via QR.

No I think he meant not exportable *at all* based on how it’s written and just the whole point of this is to keep offline keys as offline as possible, if someone is using a HW wallet to generate the keys wouldn’t need to export them from a hot app at all

Sure, then let's not export... I don't understand your point

Just clarifying since you said “via QR” at the end of your last reply. The text of the bounty says “When this approach is used, prevent export of the key in the app itself to provide better security around someone getting your nsec from your phone being open.”

So prevent export [entirely] just for keys that are imported in this way. Otherwise you go from cold to semi hot keys to fully hot. It’s an imperfect solution while we wait on nip 26 I believe.

Oh, yes... Makes sense. We don't have a separate export block for certain keys, but it shouldn't be hard to create.

👀

#[0]