pull down to refresh
reply
If there’s a way to unilaterally exit but we don’t provide it, and we don’t even store the state to provide it later, then we are to blame if stackers lose funds. If you lose funds using a custodial wallet, it’s not our fault.
Yeah that was my point above.
Ah, mhh, but for me these are two different points:
- Unilateral exit if the wallet is only ever funded via lightning
- How lightning is implemented to stay trustodial
reply
You're right. So it's blocking because you need to know how to protect stackers, but regardless, there is still a single point of failure on every path (even if there are multiple paths, the failure is still singular within each path, and user mitigation is required to overcome it, which is as bad as custodial)
reply
LightningSendRequest. Thetransferproperty ("leaves transfer after lightning payment was sent") might be related, but I haven't looked further into it.