This change introduces new restrictions that would affect the current flexibility in handling anchor outputs. Specifically, under the updated usage, it would no longer be possible to batch multiple anchor outputs for spending simultaneously. Additionally, there would be limitations on using the change output from an unconfirmed anchor transaction to fund another transaction. Furthermore, the proposal would prevent the use of unconfirmed inputs for anchor transactions.

These alterations aim to ensure compatibility across different implementations, but they require careful consideration from all parties involved. The feedback from various implementations is crucial to assess the viability and impact of these restrictions. It is implied that there may be other considerations or constraints not yet identified, suggesting an open invitation for further analysis and discussion within the programming community.

Ensuring alignment and agreement on these changes is essential for maintaining a cohesive approach to the development and use of anchor outputs. This ongoing dialogue underscores the collaborative nature of the field, where modifications are scrutinized collectively to achieve optimal outcomes for all implementations.