NUT-XX: Token possession proof #360
No reviewers
Labels
No labels
breaking change
bug
documentation
enhancement
needs discussion
needs implementation
new nut
ready
wallet-only
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo-admin/nuts!360
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "joemphilips/nut-token-possession"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Define a mechanism for mints to restrict endpoint access based on possession of tokens from a specific keyset with a minimum token count requirement. Generalizes NUT-22 from identity-based auth to possession-based authorization without spending proofs.
Context: When I was updating the spec for Conditional Token Framework (https://github.com/cashubtc/nuts/pull/337/),
I noticed that I want to grant access to some Mint endpoints only to the user who holds the token.
22.md was not good enough because it was only proof-of-authentication, what I wanted was proof of possession.
24.md was also not good because it requires a payment from the user.
To give more details, I want to introduce a new kind of token in https://github.com/cashubtc/nuts/pull/337/, so to speak, "Market Owner token".
Market owner will receive this token when they register a
conditionfor the CTF.A mint can take an additional swap fee for each conditional token transaction, and then later, the Market Owner Token holders can redeem the fee collected in exchange for that market owner token. This incentivizes users to create a more popular market.
If the market is a company, then this token is like a stock.
I want to have an endpoint that only the market owner can access. e.g. "total fee accumulated for this market". This spec is the prerequisite
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.