NIP-46 (nostr connect) as a client #227

New issue

Open

opened 2023-02-15 15:00:06 +13:00 by mikedilger · 2 comments

mikedilger commented

2023-02-15 15:00:06 +13:00

(Migrated from github.com)

NIP-46 as currently specified is here: https://github.com/nostr-protocol/nips/blob/master/46.md
A rewrite that hasn't yet been merged is here: https://github.com/nostr-protocol/nips/pull/831
Enhancements for NIP-44 are here: https://github.com/nostr-protocol/nips/pull/746
Pablo's suggestion for signup using this along with a nip-05 address is here: nostr:nevent1qqsqwsev3yjctdz9erky4kcuaf4fjcppfr9r4wpm7k0fk6ndc0jpx6cpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgnwaehxw309ahkvenrdpskjm3wwp6kytcpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7mxs2vt

I will make a checklist of things we need to do to support all of that soon.

This issue is for NIP-46 support AS A CLIENT of a remote signer on some relay. For use of nostr-connect as a server, see #625

NIP-46 as currently specified is here: https://github.com/nostr-protocol/nips/blob/master/46.md A rewrite that hasn't yet been merged is here: https://github.com/nostr-protocol/nips/pull/831 Enhancements for NIP-44 are here: https://github.com/nostr-protocol/nips/pull/746 Pablo's suggestion for signup using this along with a nip-05 address is here: nostr:nevent1qqsqwsev3yjctdz9erky4kcuaf4fjcppfr9r4wpm7k0fk6ndc0jpx6cpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgnwaehxw309ahkvenrdpskjm3wwp6kytcpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7mxs2vt I will make a checklist of things we need to do to support all of that soon. This issue is for NIP-46 support AS A CLIENT of a remote signer on some relay. For use of nostr-connect as a server, see #625

ulrichard commented

2023-06-01 02:05:56 +12:00

(Migrated from github.com)

Using a private key stored on a YubiKey or Hardware wallet would be great.

👍 1

mikedilger commented

2023-11-07 09:32:25 +13:00

(Migrated from github.com)

This issue is now about nip-46. Delegation is done. Hardware support is #570. I will update the original post with a checklist