SHRINCS: an efficient hash-based signature scheme for Bitcoin (first draft)

The email from Antoine highlights several key considerations in the realm of cryptocurrency protocol development and document presentation. First, it points out the absence of a signature mode specific to accounting practices in the reviewed document. This omission could imply a need for further inclusion to cover all essential aspects of transaction handling and security.

Antoine also discusses the potential implementation of stateless off-chain second-stage transactions, such as those used in lightning or vault systems. He suggests that replicating these on multiple towers without synchronizing state management would significantly increase operational costs due to the large data requirements (identified as 5777 bytes). This increase in operational cost is roughly estimated at 90 times for maintaining the necessary fee-bumping reserves required by these protocols. Alternatively, Antoine mentions the possibility of using more compact solutions like falcon or applying severe discounts to certain fields. However, he cautions that such approaches might expand the Denial of Service (DoS) attack surface for validating nodes, thereby introducing new risks.

Furthermore, Antoine remarks on the lack of a table of contents in the document, which could affect the navigability and usability of the document for readers. Despite these critiques, he acknowledges the overall value and intrigue of the work presented.

This feedback is crucial for understanding the technical complexities and operational challenges associated with developing and documenting cryptocurrency protocols, especially those aiming to enhance scalability and reduce costs without compromising on security. It also underscores the importance of thorough documentation to aid in the readability and utility of technical documents in the field.