Stats on compact block reconstructions

The discussion revolves around the handling and behavior of orphan transactions within a blockchain system. Orphan transactions are those that have been separated from their parent block, often due to network delays or disruptions. The inquiry suggests that upon review, most transactions considered were indeed orphans, confirmed through random checks. These transactions remain in what's termed as the "orphanage" until the process of block reconstruction occurs. However, it's noted that these transactions don't contribute to the reconstruction process itself.

There's an observation made about the redundancy of re-requesting transactions already present within the system. This points to a potential inefficiency in how transactions are managed, particularly when they're in the orphan state. The interaction between the orphanage — where orphan transactions are stored — and the extrapool, another component of transaction management, is not fully understood by the person. This gap in understanding opens up an area of interest, suggesting that exploring the relationship between these components could yield improvements in handling transactions. Specifically, there’s a proposal to potentially avoid storing orphans in the extrapool and to also iterate the orphanage during block reconstruction, which could optimize the process.

This summary encapsulates the concerns and suggestions related to improving the efficiency of transaction management in blockchain systems, specifically focusing on the treatment of orphan transactions and the operational dynamics between the orphanage and extrapool.