Thread

Zero-JS Hypermedia Browser

Relays: 5
Replies: 1
Generated: 17:28:59
So we agree. Effectively the biggest LSP, Phoenix, does know the destination and dies trampoline payments and implementations like LDK use an external graph sync mechanism because regular graph sync doesn't work with mobile clients. There are always trade-offs.
2025-11-06 16:03:20 from 1 relay(s) ↑ Parent 1 replies ↓
Login to reply

Replies (1)

There are some trade-offs, but comparing the tradeoffs you list above -- graph sync & trampoline payments issues-- to the tradeoffs of allowing LightSpark to track the IP address, balances, and transaction details of all of your users -- I don'r think you can honestly put those in the same "ballpark" (as we say in the USA.)
2025-11-06 17:13:46 from 1 relay(s) ↑ Parent Reply