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

In the email, Johan suggests that OP_CHECKCONTRACTVERIFY may be able to achieve what Antoine is looking for. He provides a link to a discussion on the Bitcoin-dev mailing list for more information (https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-May/021719.html).Johan explains that by committing the participants' public keys and balances in the dynamic data instead of the taptree, it is possible to have a subset of online users agree to pool their aggregated balances in a new output. Meanwhile, the funds of offline users would remain inaccessible to them in a second output.To implement this, the coinpool UTXO would be spent with a transaction that has two outputs. The first output would be the "remainder" of the previous coinpool, representing the offline users. The second output would be the new coinpool among the online users. If an offline user comes back online and tries to double spend the UTXO, Eltoo can be used to handle the situation.This approach allows for a flexible management of funds between online and offline users, ensuring that the offline users' funds are secure and accessible when they come back online.Please note that the farewell part of the email has been ignored, as per the given rules.