Nostr Connect Within Nostr Connect

[alexgleason]

I am building a custom server that is configured by Nostr events. It uses various NIP-78 events to store its config. This config needs to be authored and signed by the server nsec.

But I also want users to be admins of this server. I want those users to be able to produce events signed by the server nsec.

So I had the idea to just make the server a remote signer. If I send a NIP-46 request tagging the server's pubkey, and my pubkey is one of the admin pubkeys, the server will sign the event and respond.

But then I realized... that I might already be using a remote signer for my admin user account.

So, I would be using Nostr Connect to sign another Nostr Connect event. I would be doing Nostr Connect within Nostr Connect.

[vitorpamplona]

Either a NIP-46 signer to manage access controls or a simple DVM/bot to manage users of any account, like this: https://github.com/nostr-protocol/nips/pull/1015/files

[vitorpamplona]

Well, I described it as a document, but there are no restrictions to being only that document. Since the DVM has the private key, it could write anything users want. We just need to specify who gets access to what in a way that any DVM implementing this can understand.

[alexgleason]

Doesn't the signer way seem more intuitive? What's the benefit over the DVM approach?

[vitorpamplona]

Either way would work. The signer is just another DVM in my mind. Both could use the same events to register permissions for each other pubkey.

I just like the idea of using off-the-shelf DVMs instead of having to setup signers everywhere.

[alexgleason]

I think it should be possible to implement a NIP-07 interface in front of it, eg:

• NostrSigner
• NSecSigner
• NSeedSigner
• NPhraseSigner

I'm planning to also do a NConnectSigner.

I agree using a DVM would also work. But it should be more like a pure signer, so I can actually implement a NDVMSigner matching the same interface.

[vitorpamplona]

Nice, yeah that would be awesome.