-
Performing a sequential decode/encode on an LND invoice throws exceptions. The expiry and signature tags specifically. The Enum in tags.py doesn't appear to be in-spec with the bolt11 spec.
-
- In `LUD-03` in the callback the `LN WALLET` send a Bolt11 Lightning payment request (invoice).
- Bolt11 allows that a payment request might contain only a hash of the description (tag `h`)
- B…
-
The current LSPS1 spec states in regards to `refund_onchain_address`:
```
refund_onchain_address Address where the LSP will send the funds if the order fails.
Client MAY omit this field.
…
tnull updated
2 weeks ago
-
I love the addition of BOLT12 in the latest version of the app. The receive screen is getting a little cluttered, IMHO, so I'd like to propose some adjustments to the layout and interaction model, for…
-
A few new fields were added since this crate was initially written and the specs were made stricter and updated with more [test vectors](https://github.com/lightningnetwork/lightning-rfc/pull/736).
-
@thebrandonlucas pointed out that the old BOLT12.org had a useful examples section. While I believe that the majority of these examples are irrelevant (no more recurring payments in current spec, rigt…
-
...using `decodepay` and making sure decoding is possible.
Today, the bolt11 string is validated when calling `ln_pay`, but if it is not valid, lnurl only knows `ln_pay` failed but doesn't know it'…
-
User friendly way for users to pay with Bitcoin would be to scan QR code (or use NFC) and not think about on-chain payments, Lightning Network or other protocols under the hood. It seems that there ha…
-
### Describe the bug
Signet Bolt11 Invoices are still not recognized properly. It errors out with `Error loading invoice: Unkown coin bech32 prefix`
### Reproduce
Here is a signet invoice:
![ima…
-
Hi Team,
It seems that phoenixd is generating unpayable invoices. I have tried with WalletOfSatoshi, which scans the QR and then does nothing, and Aqua, which says "unsupported invoice".
My proc…