NIP-46

The next discussion.

nostr:note1awj6hqu9m6g6gjm8vlxvev4frjs0wqg2nscvxgh9alzgdlf7syfqjwz2sc

Reply to this note

Please Login to reply.

Discussion

We always be talking about nip46.

Since were on the topic I opened this a while ago, but haven't progressed on it

https://github.com/nostr-protocol/nips/issues/1207

So, this is basically signing with NIP-05 addresses instead of nsec directly, so that they just have to "keysign" NIP-05 once and then the server that hosts it becomes their signer?

Basically nip-46 directly over http instead of websocket rpc. Direct to the signing server instead of via relays. No nip04 encryption and extra keypairs and such. They made very valid points, like using the nip46 direct websocket connection, but I just feel like a plain http version would be ideal, although that does put more stress on clients, so thats asking too much.

Well, we could offer both, right? We don't have to care, if anyone else builds it. So long as we sign the events validly, they have to take them.

Hmmm yeah I guess so

In this case I may redirect my efforts on NVault to focus on a signing API instead of the internal web extension API