Exit Requirements
Arkade’s architecture organizes VTXOs in a virtual tree structure rooted into batch outputs. Each batch output branches into multiple virtual transactions, which can further branch into additional virtual transactions, creating a tree-like structure of spending relationships. Individual VTXOs exist as leaves or intermediate nodes within this virtual tree. To enforce a unilateral exit claim onchain, users must publish a complete transaction path from the relevant batch output down to their specific VTXO. This requires broadcasting multiple sequential Bitcoin transactions that “unroll” the virtual tree structure, with each transaction in the chain consuming outputs from the previous transaction until the user’s VTXO is finally claimed. Example Exit Path:- Batch Output → Virtual Transaction A (first level)
- Virtual Transaction A → Virtual Transaction B (second level)
- Virtual Transaction B → User’s VTXO (final claim)

Exit Costs
Base Costs: Every unilateral exit incurs Bitcoin network fees for each required transaction in the path. A VTXO requiring a 3-transaction exit path costs 3x the base Bitcoin transaction fee, regardless of the VTXO’s value. Chain Length Impact: As users engage in more offchain activity, their VTXOs move deeper into the virtual tree structure, creating longer exit paths. Extended offchain transaction chains compound exit costs:- Direct child of Batch Output: 1 Bitcoin transaction required
- Second-level VTXO: 2 Bitcoin transactions required
- Third-level VTXO: 3 Bitcoin transactions required
- And so on…

In order for a user to unilaterally exit, they must broadcast a combination of presigned transactions containing their VTXO. Possessing these presigned transactions ensures a user can always spend their allocated funds independently, without requiring coordination with other participants or the operator.