What’s the deal with connector batches in Ark pool transactions?

Hey everyone, I was digging into some research for a project and hit a snag that I can't quite wrap my head around. I figured this forum would be a good place to bring it up and get some clarity. So, transactions have two main outputs related to the protocol, depending on the source or info pool: 1. vTXOs output 2. the output connection From what I understand, a vTXO output is a psbt binary tree, where each leaf stands for a vTXO. But what about the connector? Is the binary tree format the same for that? Or does it break the connector's output into several dust outputs using just one (virtual) psbt?

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 SolutionThe Ark FAQ Ark's official site is now at: https://arkdev.info/. 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. 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.