From ace4f94d9c5947d3d8595a1a1afee80b71b910a8 Mon Sep 17 00:00:00 2001 From: Jeremy Klein Date: Tue, 5 Dec 2023 12:12:06 -0800 Subject: [PATCH] Rename to to better match a LUD-21 proposal. --- umad-04-lnurlp-response.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/umad-04-lnurlp-response.md b/umad-04-lnurlp-response.md index e2f2d2a..9ef08bc 100644 --- a/umad-04-lnurlp-response.md +++ b/umad-04-lnurlp-response.md @@ -25,11 +25,11 @@ The full structure of the LNURLP response is: // Estimated millisats per "unit" (eg. 1 cent in USD) "multiplier": number, // Number of digits after the decimal point for display on the sender side. For example, - // in USD, by convention, there are 2 digits for cents - $5.95. in this case, `displayDecimals` + // in USD, by convention, there are 2 digits for cents - $5.95. in this case, `decimals` // would be 2. Note that the multiplier is still always in the smallest unit (cents). This field // is only for display purposes. The sender should assume zero if this field is omitted, unless // they know the proper display format of the target currency. - "displayDecimals": number, + "decimals": number, }, { "code": string, // eg. "BTC", @@ -38,7 +38,7 @@ The full structure of the LNURLP response is: "minSendable": number, "maxSendable": number, "multiplier": 1 // estimated millisats per "unit" (eg. 1 cent in USD) - "displayDecimals": number, + "decimals": number, }, ], // Required data about the payer. See LUD-18 for details.