How are the connector batches in the transaction for Ark pool?

[Egii Nna]

Hello, I was conducting research for a project when, as usual, I reached a point that I didn't understand. Since I knew this forum would help me grasp it better and learn more, I decided to bring it up.

Transactions include two primary outputs associated with the protocol, depending on the source or the information pool:

1. vTXOs output
2. the output connection

I am aware that the output of a vTXO is a psbt binary tree, where each leaf represents a vTXO.
Is the connector (binary tree) format the same? Or does it split the connector's output into X dust outputs using a single (virtual) psbt?

[BlackHatCoiner]

I know that I'm replying to an old topic, but I noticed nobody did a year ago. Better late than never. Note that the theoretical background has changed quite a bit since October 2023.

If you have any other questions, don't hesitate to make them in one of the following two topics:

• Ark: An Alternative Privacy-preserving Second Layer Solution
• The Ark FAQ

Ark's official site is now at: https://arkdev.info/.

I am aware that the output of a vTXO is a psbt binary tree, where each leaf represents a vTXO.

That's not accurate. A VTXO is a leaf of the VTXO tree. This tree is created, not by the output of a VTXO, but by a shared output. Think of a shared output as a locking tapscript, which can be unlocked either by the user by unrolling the tree anytime, or by the ASP after a specified timeout.

Is the connector (binary tree) format the same? Or does it split the connector's output into X dust outputs using a single (virtual) psbt?

The connectors follow the same approach, as with VTXO. There is a connector tree. When a new round transaction is initiated, for every VTXO the ASP creates, there is a connector output from the next round.

Read more in here: https://arkdev.info/docs/learn/concepts.