feat(mint): support BOLT11 description hashes - #1105
Open
sotach1 wants to merge 3 commits into
Open
Conversation
This was referenced Aug 4, 2026
❌ 2 Tests Failed:
View the top 2 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Member
|
@sotach1 a couple failed tests you should look at. |
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
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.
Summary
description_hashflag to the NUT-23 BOLT11 mint quote requestoptions.description_hashin mint infoThis supports protocols such as NIP-57 where the invoice must commit to exact data supplied out of band. The behavior is deliberately per quote: ordinary Cashu deposit descriptions continue to use the BOLT11
dtag, while an opted-in quote uses thehtag.Protocol proposal: cashubtc/nuts#417
The capability is currently enabled for FakeWallet, LND gRPC/REST, LNbits, and Blink. Other backends reject opted-in requests rather than returning an invoice with the wrong commitment.
Request example
{ "amount": 21, "unit": "sat", "description": "<exact out-of-band data>", "description_hash": true }Testing
ddescription and had nohtagdtag and itshtag matched the exact descriptionso@nuts.cashreturned a 42-sat invoice whosehtag matched the exact signed kind-9734 JSON