I rated spark higher than something like aqua due to the unilateral exit path, but I had a huge problem with it still not being permissionless. spark and also ark don't give the user a way to force a state change to occur, so the service provider can block payments. theoretically this could also happen on liquid if the federation decides not to confirm a transaction. on any offchain scaling solution you ideally want the processing to be done permissionlessly. so like anyone can decide that they want to participate in running it and they don't need permission to help process transactions. if this is difficult, then at the very least there needs to be a way for a user to force a state change unilaterally without the service provider's cooperation. outside of self-custody lightning this is very rare. rollups like citrea, arbitrum, and base at least have unilateral state change.

Replies (3)

My issue is actually a lot more basic and grug-brained than this. In order to use Spark, you have to hit Lightspark's GraphQL endpoints. Those endpoints are all servers controlled by one family. It would be trivial for governments to pressure that family into collecting I.P. addresses and doing other various things to de-anonymize the payments. The fact that Lightspark also *specializes* in compliance, KYC, etc., is especially worrying.
> ark don't give the user a way to force a state change to occur This is not true. Ark VTXOs are on-chain signed transactions the users can at any time broadcast to mainnet and have their sats back. You can exit an Ark without the need for server agreement.