-
Notifications
You must be signed in to change notification settings - Fork 2
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
[api-v2-bug] Create Address endpoint creates broken Lightning addresses #18
Comments
|
This ticket will likely close since I find their requirement to have my Python and JSON sample code encoded into JPEG to be patently ridiculous. Last correspondence...
I politely refuse to encode the JSON provided earlier into a JPEG on the grounds that the request is flat out ridiculous. |
Last reply seem insistent, and given the oddities of the request, I have to contend with the very real fact that the support mailbox may be triaged by an AI. If so, this issue won't be passed off to a dev until "Collect Data" task is complete. I've rendered the text to PDF (*sigh*) and feed the AI it's meal. Attached |
The Create Address endpoint attempts to support the new BTC-LN addresses, but mixes them with Legacy addresses.
By modifying the parameters to Create Address, an attempt can be made to make a LN-Invoice. The attempt does not generate any error, but neither does it generate a LN-Invoice.
new-ln-address.json
Attempt to create an LN-Invoice
The attempt produces no errors, but the (redacted) response JSON is completely incorrect (note
deposit_uri
)Lightning addresses can be created on the coinbase.com webpage without error. And they can be listed using the List Address endpoint with the following (redacted) data:
The text was updated successfully, but these errors were encountered: