I'm a Coinbase user in good standing granted use of the Lightning feature; Ask Me Anything

As part of the announcement Tuesday, there has been a slow rollout of Lightning across user accounts. Few hours ago my account got included in the rollout. Here's the basics.

1. No notification was given, it was just there when I checked
2. No message at login, it was just there when I checked
3. On BTC-LN receive there was an enablement / acknowledgement message to confirm
4. On BTC send dialog the help text changes to "BTC address or Lightning address"
5. Lightning appears in the APIs like any other BTC address under network lightning
6. LN BOLT-11 invoice format (lnbc1...) work in Allowlist
7. LN-Address format (user@place), and LNURL format (lnurl...) are not supported
8. BOLT-11 invoices MUST include an amount
9. Sending to LN-Address (user@place) will be lost as a send-to-email TXN instead
10. Both BTC and BTC-Vault accounts seem to accept Lightning

Glad they remembered to update the APIs and allowlist functionality. Disappointed they don't support 0-sat BOLT-11 invoices, LNURL invoices, or LN-Address formats. And obviously they bugged the API Create Address functionality here.

API endpoints

List LN Invoices (works)

Show all BTC addresses where the network field is set to lightning

btc_acct_id=6789abcd-ef01-2345-6789-abcdef012345 pyexch \ --url /v2/accounts/${btc_acct_id}/addresses \ | jq '.data[] | select(.network == "lightning")' 

Create LN Invoice (broken; ticket #19237115)

Create new-ln-addr.json5 file to contains the desired parameters

// pyexch --param new-ln-addr.json5 \ // --url /v2/accounts/:btc_acct_id/addresses \ // --method post { // freeform text "name": "New LN Address", // note that this will be BTC-LN address "network": "lightning", } 

Make the API call

btc_acct_id=6789abcd-ef01-2345-6789-abcdef012345 pyexch --param new-ln-addr.json5 \ --url /v2/accounts/${btc_acct_id}/addresses \ --method post