ark parameters are specific to their vision but not mandatory. the basic idea of ark and of timeout tree is that in the happy path you don't need to eventually settle the txns because you can nullify them and sweep the root of the taproot
I remember the website saying they can even pay you on-chain. if it required LNURL I don't understand what the service was... just invoicing for e-commerce?
I can't tell for sure but I think the power of the product was in invoicing for payees that are not constantly online, or don't have a reliable LNURL presence
how would that work in this case?
between phoenix, breez, mutiny and zeus the model of LSP based non-custody mobile LN is becoming pretty robust
the real bottleneck is still L1 throughput, and it's a mistake to call it a UX problem. it's a hard limit of the protocol
covenants are the most promising path
CTV NOW!
it's an arms race. there is no perfect
it was the best UX because it was custodial. the problem is real
if zapplepay works fine on damus, and using small-sums trusted MWC setups with services like alby (which is ok imo) is also fine, the issue with damus zapping is pretty much just an issue of how the UI looks
how can damus create a UI that doesn't look like a payment to the bureaucrats that review apps on the app store?
currently zapplepay supports only a fixed sum, but they can easily make a different sum for each different emoji (i.e: π€=21, β€οΈ=69, π=420), for example
at the end of day it's an arms race, and every tactic is legit, just like every tactic the authority uses is legit in their strategy
ask the users to pay
move to grapheneOS yesterday
have to admit, the cucking of WoS came sooner then i expected. combine this with binance and the picture is clear: U.S regulators started to move
everything bitcoiners anticipated is correct and is happening in real time. now is the time to build the actual alternatives
suddenly mutiny wallet experimenting with PWAs isn't just nerds larping. the work that phoenix, breeze, and fedi are doing is critical. covenants are critical
every single-point-of-failure that can be captured will be captured