Skip to content

NUT-XX: Token possession proof#360

Open
joemphilips wants to merge 1 commit intocashubtc:mainfrom
joemphilips:nut-token-possession
Open

NUT-XX: Token possession proof#360
joemphilips wants to merge 1 commit intocashubtc:mainfrom
joemphilips:nut-token-possession

Conversation

@joemphilips
Copy link
Copy Markdown

@joemphilips joemphilips commented Apr 6, 2026

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 (#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 #337, so to speak, "Market Owner token".
Market owner will receive this token when they register a condition for 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

@github-project-automation github-project-automation bot moved this to Backlog in nuts Apr 6, 2026
Define a mechanism for mints to restrict endpoint access based on possession of tokens from a specific keyset with a minimum amount requirement. Generalizes NUT-22 from identity-based auth to possession-based authorization without spending proofs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

1 participant