Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NUT-18 Payment Requests: Make mints mandatory #227

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

ok300
Copy link
Contributor

@ok300 ok300 commented Feb 17, 2025

A core aspect of cashu is that users must somewhat trust the mints. This means receivers shouldn't receive tokens from just any mint. For merchants this is an existential distinction, so for them this becomes less a recommendation and more an imperative. Otherwise, accepting tokens from any mint as payment for goods and services is a sure way to be defrauded, allowing e.g. any fakewallet payment to be accepted as real.

Since this NUT is targeted at merchants, it has to indicate that receivers MUST indicate a list of trusted mints in their Payment Requests.

ok300 and others added 2 commits February 17, 2025 11:26
Co-authored-by: lollerfirst <43107113+lollerfirst@users.noreply.github.com>
Co-authored-by: lollerfirst <43107113+lollerfirst@users.noreply.github.com>
@callebtc
Copy link
Contributor

A merchant can receive tokens from any mint if they melt the token to their LN wallet before regarding the transaction as settled.

@findingsov
Copy link
Contributor

The Receive to Trusted Mint functionality (via Lightning) can help here too.

@thesimplekid
Copy link
Collaborator

This also removes the use case for something like a donation address where the receiver does not care what mint it is from as it is funds it would not receive anyway. Then as pointed out above the receiver can swap or melt as they see fit.

@callebtc
Copy link
Contributor

concept nACK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants