New major release! Phoenix Android/iOS/Server now supports BOLT12 \ stacker news ~lightning

pull down to refresh

New major release! Phoenix Android/iOS/Server now supports BOLT12 x.com/PhoenixWallet/status/1808547081214439494

3828 sats \ 24 comments \ @Rsync25 3 Jul lightning

Features

reusable, non-expiring payment requests
contact list (Android for now, iOS soon)
attach messages to payments

This marks a new step forward in Lightning UX. No need to generate a new QR code for every payment. No need for payer/receiver to interact.

Phoenix Android (soon iOS) also supports contacts. Send money with a click, and associate payments to your known contacts.

view all related items

137 sats \ 0 replies \ @nout 3 Jul

Phoenix is solid! And in some ways it's good that it's not in the US AppStore, because it pushes people to :

install it directly from acinq or from alternative store (e.g. https://zap.store/ or https://obtainium.imranr.dev/ )
use more private/open OS like GrapheneOS
travel more outside of US :)

126 sats \ 6 replies \ @tomlaies 4 Jul

I feel like Bolt12 on Phoenix could almost replace BTC Payserver. Just a static QR code for payment then then some kind of REST request to Phoenix if it has been payed?

13 sats \ 5 replies \ @moneyball 6 Jul

refunds? accounting?

4 sats \ 3 replies \ @k00b 6 Jul

If the app can call a webhook on payment, then you could do that in some other system.

13 sats \ 2 replies \ @moneyball 7 Jul

Right, like BTCPay :) (or, Zaprite)

0 sats \ 1 reply \ @k00b 7 Jul

Do BTCPayServer or Zaprite allow your lightning keys to live on your phone? I'm not too familiar with either. That's the main advantage here I guess.

100 sats \ 0 replies \ @moneyball 7 Jul

That's a goal with the BTCPay app project https://github.com/btcpayserver/app

There's been some discussion of a BOLT 12 protocol modification to allow for Zaprite to integrate with merchant LN wallets.

There's of course all the challenges of mobile including availability to sign to receive money. Async payments protocol helps but whether applicable to a merchant depends on the volume and type of merchant.

0 sats \ 0 replies \ @tomlaies 7 Jul

You're right that a static QR code and a webhook into payment history is not quite there to be a fully fledged payment system. That's why I said "could almost" - because it can already do a lot, enough for some usecases, of course not everything.

131 sats \ 3 replies \ @EntropyBearer 3 Jul

So cool, from their GitHub, I was definitely not expecting BOLT12 support so soon. Gonna have to try it ASAP.

I suppose now we can head to https://twelve.cash, create a lightning address and call it a day.

20 sats \ 2 replies \ @itsMoro 3 Jul freebie

ive yet to have twelve.cash successfully receive sats, have you? ive tried with phoenix and with ride the lightning setting up the offer, but i never can pull an invoice when i put in the address

12 sats \ 1 reply \ @EntropyBearer 3 Jul

Sadly I just tried it with Phoenix and it didn't work. 🥲

22 sats \ 0 replies \ @cw 4 Jul

At the moment only Zeus supports bolt12 and bip353

10 sats \ 3 replies \ @BitcoinIsTheFuture 3 Jul

Are we all going back to using Phoenix in the US?

142 sats \ 2 replies \ @Bitcoinisawesome 3 Jul

We never left. It’s nonsensical to stop using Phoenix because of a simple removal from an App Store. That’s the extent of their change… Phoenix never stopped working. This isn’t a follow the mob group of people, I hope. If it works (allows you to make tx) then it works. Do you not them