7d
Petite Badger 2y ago

Use NIP-26 to delegate authentication with NIP-42 to have zappers authenticate to payed relays on behalf of the user zapping.

The client would create a NIP-26 time limited delegation for kind 22242 and add it to the NIP-57 zap request. The zapper can then use this delegation to authenticate against payed relays and deliver the kind 9735 note. Relays would need to add a check of the delegation to their auth workflow.

This adds a little more load as as a relay needs to look for a delegation tag before dropping incoming notes. However there is no need to validate the delegation if the pubkey does not belong to a whitelisted user.

#[0]

#[1]

Good idea or bs?

Reply to this note

Please Login to reply.

Discussion

Avatar
jb55 2y ago

interesting...

7d
Petite Badger 2y ago

Its more complicated than just whitelisting zappers, but its open and general. Delegated authentication would be nice in any case, I guess. Unfortunately it adds more work to the ln node too, so

its harder to support as they need to login to each relay.

Avatar
fiatjaf 2y ago

Relays can just check if the contents of the zap request are from a whitelisted user and allow based on that. They can do this today, there is no need for anything extra. The ones that do can market themselves as "zap-friendly" and gain more users.

The same approach can also be used for replies, likes etc.

7d
Petite Badger 2y ago

ah, okay. that makes sense. didn't see that. But without authentication i can reply spam any relay, but thats normal spam handling, I guess.