blixt-wallet
blixt-wallet copied to clipboard
hsjoberg
Bitcoin Lightning Wallet with focus on usability and user experience
The response to an LNbits "Quick Voucher" from http://ub3fenqxnexutnauxkekj2lvagmlpzga7el77jglyevfowuorj26skid.onion:5000/withdraw/CRkLCQKERa6VfjhP77AzTB:  `LNURL1DP68GUP69UHNGDT4DP3KKUEJX44HJVN4W4ENVEMGV3NKZVMTD5EKUDNWW36HVVEHX4NKWMF5WPMRWUR8XACRGDMVWDC8V6T0D9UKGTN0DE5K7M36X5CRQVP0WA5HG6RYWFSHWTMPWP5J7A339AKXUATJDSH4S5TCTPT8W7RRF4T427TCXFM52VMP24XYZ330GGU8YUJPG3VXSCENVYEK6DTD2EN8ZKFH09TQMA00FV` Decodes to: http://45uhcks25ky2uus6ghdga3km3n6ntuv375ggm4pv7pg7p47lspvioiyd.onion:5000/withdraw/api/v1/lnurl/XQxXVwxcMWUyx2wE3aULAF/B8rrADXhc3a3m5mVfqY7yV And Blixt with Tor enabled responds:  The LNURLw works as expected with Simple Bitcoin Wallet
When paying with lnurl-pay or withdrawing with lnurl-withdraw, we should make a GET request to the domain site, parse the HTML and look for a `favicon`, `apple-touch-icon` or a `manifest.json`...
https://twitter.com/roasbeef/status/1422354952186302465
* Should have iOS support * Should be stable Good to have * Should be able to do AJAX requests * Lightning browser
`DecodePayReq` supports reading `f` field (https://github.com/lightningnetwork/lightning-rfc/blob/master/11-payment-encoding.md#rationale-2): https://api.lightning.community/#decodepayreq
Shortly after receiving some on-chain funds, a new channel has been opened without user interaction.  The transaction log looks pretty scary too, there is no indication how the coins...
