Solving CoinPool high-interactivity issue with cut-through update of Taproot leaves

The email discusses the issue of disaggregating participant's pubkeys and balances from a partial subset push on the stack and verifying the validity of corresponding signatures. The author mentions that one requirement for a cut-through update of taproot leaves is to verify the authentication of the fan-out balances and pubkeys towards the "online" partition. However, this subset is not known at pool setup, even though the contract or tree construct can be equilibrated with some expectation. The author suggests that OP_CHECKCONTRACTVERIFY could be used to architect the proposed design of coinpool and its cut-through mechanism. One challenging aspect mentioned is the efficient traversal, inspection, and modification of the contract.