Ark: An Alternative Privacy-preserving Second Layer Solution



Summary:

The person has two questions regarding the Ark write-up. Firstly, they ask what happens every 5 seconds when pool transactions are created by ASPs. They question if the ASP signs a new transaction which spends the same ASP funding inputs as the previous pool transaction or if it spends the outputs from the previous PoolTx. They also ask what the ASP does with the pool transaction once it is created, whether they broadcast it to the gossip network or share it with other pool participants. They discuss three possible methods and their respective issues with each method.Secondly, they question what prevents the ASP from taking all the money. They state that before even getting to vTXOs and connector outputs, there are only ASP inputs funding the pool transaction. If the pool transaction is confirmed, the vTXOs are locked in place, since the vTXO output cannot be changed and commits to all "constrained outs" via OP_CTV. If the pool transaction is unconfirmed, the ASP can create & sign a transaction spending all ASP funding inputs sending the money back to the ASP, or anywhere else. In this case, users don't have any assurance that their vTXO can ever turn into a real UTXO.


Updated on: 2023-06-16T18:33:11.548160+00:00