New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

interest in handling passphrase-protected private keys (`ncryptsec1`-prefix files)? #47

Open

jzacsh opened this issue Feb 8, 2025 · 0 comments

jzacsh commented Feb 8, 2025 •

edited

Loading

Is there any interest in eventually handle ncryptsec1-prefixed private keys as input? I'm extremely new to nostr so maybe this ask doesn't even make sense, but if I'm following correctly I think this is what NIP-49 describes and it looks like the original nos2x is handling this case here: https://github.com/fiatjaf/nos2x/blob/f2c73d2992fa8c463571d5b2b67dbd52b0c7d25d/extension/options.jsx#L588-L590 (via NIP-49 helper) (granted there's discussion here, but I tried it on the latest chrome extension and it seems to work)

at version 1.17.0 when I paste an ncryptsec1 key into the extension's form, I get this JS error in devtools:

Error decoding NIP19 key: Error: unknown prefix ncryptsec options.js:28482:17

The text was updated successfully, but these errors were encountered:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment