Bolt12 lighting offers payment method #259

2025-05-13T08:57:52Z

thesimplekid commented

2025-05-13 08:57:52 +00:00

(Migrated from github.com)

Depends on https://github.com/cashubtc/nuts/pull/258

CDK https://github.com/cashubtc/cdk/pull/874
Nutshell
cashu-ts https://github.com/cashubtc/cashu-ts/pull/342
nutmix

Depends on https://github.com/cashubtc/nuts/pull/258 - [x] CDK https://github.com/cashubtc/cdk/pull/874 - [ ] Nutshell - [x] cashu-ts https://github.com/cashubtc/cashu-ts/pull/342 - [ ] nutmix

callebtc commented

2025-06-01 10:31:44 +00:00

(Migrated from github.com)

@thesimplekid could you rebase this PR to main and add bolt12 in the new "supported methods" lists in NUT-04 and NUT-05?

@thesimplekid could you rebase this PR to `main` and add `bolt12` in the new "supported methods" lists in NUT-04 and NUT-05?

👍 1

gudnuf commented

2025-08-18 17:47:43 +00:00

(Migrated from github.com)

Should we update NUT-17 to define bolt12_mint_quote and bolt12_melt_quote subscription kinds? Or maybe these should be defined more generally. For example: <method>_mint_quote

Should we update NUT-17 to define `bolt12_mint_quote` and `bolt12_melt_quote` [subscription kinds](https://github.com/cashubtc/nuts/blob/main/17.md#command-subscribe)? Or maybe these should be defined more generally. For example: `<method>_mint_quote`

thesimplekid commented

2025-08-18 19:42:39 +00:00

(Migrated from github.com)

Should we update NUT-17 to define bolt12_mint_quote and bolt12_melt_quote subscription kinds? Or maybe these should be defined more generally. For example: _mint_quote

I think we should do this how we do nut04/05 now where nut17 is general and then each payment method (i.e. bolt11/nut23) defines the specific struct.

> Should we update NUT-17 to define bolt12_mint_quote and bolt12_melt_quote [subscription kinds](https://github.com/cashubtc/nuts/blob/main/17.md#command-subscribe)? Or maybe these should be defined more generally. For example: <method>_mint_quote I think we should do this how we do nut04/05 now where nut17 is general and then each payment method (i.e. bolt11/nut23) defines the specific struct.

👍 1

Egge21M (Migrated from github.com) approved these changes

2025-08-27 14:48:25 +00:00

gudnuf (Migrated from github.com) approved these changes

2025-08-27 17:07:43 +00:00

25.md

					
				@ -0,0 +1,279 @@

				# NUT-25: BOLT12

I think saying 'both' is a little weird in the last sentence...

Here, `request` is the bolt12 Offer to be paid and `unit` is the unit the wallet would like to pay with. For amount-less offers, the `options.amountless.amount_msat` field can be used to specify the amount in millisatoshis to pay to the offer. If `options.amountless.amount_msat` is defined and the offer has an amount, they **MUST** be equal.

I think saying 'both' is a little weird in the last sentence... ```suggestion Here, `request` is the bolt12 Offer to be paid and `unit` is the unit the wallet would like to pay with. For amount-less offers, the `options.amountless.amount_msat` field can be used to specify the amount in millisatoshis to pay to the offer. If `options.amountless.amount_msat` is defined and the offer has an amount, they **MUST** be equal. ```

Sign in to join this conversation.

No reviewers

Egge21M

gudnuf