Why this over just making every client a NIP-46 signer that can not only log you into other services, but also sign events?
This option seems like it would work for log in, but not for anything that actually requires signing of events.
Consider how most users onboard to Nostr. They download a client they heard about like Primal, Amethyst, or Damus, and they generate their keys in that client. So that first client is going to have their private key unless they have a friend who helped them get set up through a dedicated signer app like Amber. If that's the case, then those "flagship" clients ought to be able to serve as remote signers, similar to how Gossip on desktop can be a remote signer, allowing users to log in and to sign events from the client where they generated their keys.
NIP-97 seems to just allow the first part, which is unnecessarily limiting when we already have NIP-46. We would just need a more smooth way for a website to request a connection string from the remote signer app/Nostr client.
Dikaios1517
npub1ku…v3lhe
2025-03-30 23:11:26
in reply to nevent1q…tft5
Author Public Key
npub1kun5628raxpm7usdkj62z2337hr77f3ryrg9cf0vjpyf4jvk9r9smv3lhePublished at
2025-03-30 23:11:26Event JSON
{
"id": "3dc5bc21cc744a94f3cc4b8512d10f9e4c2d083f46d3e9bbe91295d2ac80f244",
"pubkey": "b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb",
"created_at": 1743376286,
"kind": 1,
"tags": [
[
"p",
"b9e76546ba06456ed301d9e52bc49fa48e70a6bf2282be7a1ae72947612023dc",
"wss://relay.momostr.pink/",
"TheGuySwann"
],
[
"p",
"9989500413fb756d8437912cc32be0730dbe1bfc6b5d2eef759e1456c239f905",
"wss://relay.nostrview.com/",
"nostr.build"
],
[
"p",
"f8e6c64342f1e052480630e27e1016dce35fc3a614e60434fef4aa2503328ca9",
"wss://relay.damus.io/",
"corndalorian"
],
[
"e",
"3596d6c827b54eaf04329ea77f514bfe4640f619bd80592dcd448ecd1b1b9ec8",
"wss://relay.damus.io/",
"root",
"b9e76546ba06456ed301d9e52bc49fa48e70a6bf2282be7a1ae72947612023dc"
]
],
"content": "Why this over just making every client a NIP-46 signer that can not only log you into other services, but also sign events?\n\nThis option seems like it would work for log in, but not for anything that actually requires signing of events.\n\nConsider how most users onboard to Nostr. They download a client they heard about like Primal, Amethyst, or Damus, and they generate their keys in that client. So that first client is going to have their private key unless they have a friend who helped them get set up through a dedicated signer app like Amber. If that's the case, then those \"flagship\" clients ought to be able to serve as remote signers, similar to how Gossip on desktop can be a remote signer, allowing users to log in and to sign events from the client where they generated their keys.\n\nNIP-97 seems to just allow the first part, which is unnecessarily limiting when we already have NIP-46. We would just need a more smooth way for a website to request a connection string from the remote signer app/Nostr client.",
"sig": "9c2c2b8b531d8e25cceb74107e6eeb94a97ad340108b665cc1c794337964852f2b203230636cf38018aaecfc54a073e2fef2c0700a449ea2f1a555afc78391b0"
}