Specifically, in such cases, only the first participants up to the maximum cluster size minus one are permitted to spend their outputs before the confirmation of the parent transaction. This condition underscores a nuanced aspect of blockchain transaction management, especially in terms of unconfirmed transactions.

Additionally, the current system already imposes a limit on the number of descendant transactions that can be made from a single transaction's outputs, which is default set at 25. This existing cap plays a crucial role in managing the load and ensuring the integrity of unconfirmed spends within the blockchain network. The discussion further delves into considerations for setting a new cluster size limit, aiming to expand this threshold beyond the current limit for descendant transactions. A draft proposal suggests increasing this limit to 100, indicating an effort to accommodate more extensive transaction capabilities within the blockchain framework. This adjustment aims to enhance the flexibility and scalability of blockchain transactions by allowing a greater number of outputs from a single transaction to be spent prior to confirmation, thus potentially improving the overall efficiency and user experience within the blockchain ecosystem.