Support for `nostr` key derivation #85

New Issue

Open

opened 2025-06-11 11:26:21 +00:00 by anton · 1 comment

anton commented

2025-06-11 11:26:21 +00:00

Owner

Nostr uses secpk256k1 (same as BTC)

ryan commented

2025-06-11 19:52:40 +00:00

Owner

Can nostr accept hex-encoded keys? I know they can accept bech32. Maybe we should make a bech32 deriver as well, if hex-encoded doesn't work.

If it is hex-encoded, it would likely "just" be:

keyfork derive key secp256k1 hex nstr --to-stdout

This derives a key at path m/[nstr]'/0'. Another consideration to be made: what should the derivation path be?

Can nostr accept hex-encoded keys? I know they can accept bech32. Maybe we should make a bech32 deriver as well, if hex-encoded doesn't work. If it is hex-encoded, it would likely "just" be: ```sh keyfork derive key secp256k1 hex nstr --to-stdout ``` This derives a key at path `m/[nstr]'/0'`. Another consideration to be made: what should the derivation path be?

No Label

No Milestone

No project

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/keyfork#85

No description provided.

Support for nostr key derivation #85

Support for `nostr` key derivation #85