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

Rename displayDecimals -> decimals to better match a LUD-21 proposal. #10

Merged
merged 1 commit into from
Dec 5, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions umad-04-lnurlp-response.md
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand All @@ -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.
Expand Down
Loading