Add claim management to nip 86#2408
Draft
staab wants to merge 1 commit into
Draft
Conversation
Member
|
Looks good to me. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is so admins can manage NIP 43 invite codes. The use case I have which requires this is collecting payment for a community relay before the user's identity has even been created. This allows me to create an invite code associated with a role, collect payment, give the user the invite code and redirect to flotilla. They then use the invite code, meanwhile my bot listens to the kind 28935 sent to the relay, then assigns a role to the user automatically granting them access to a specific room.
Labyrithine, but pretty cool that I can compose this stuff to support increasingly arbitrary flows.