Jun 6, 2026

Also, the list above refers to "no copy" a couple times. We are collecting huge amount of signatures, and that will increase some once I add threshold. Over 99% of the whole chain, which is about .5TB of data when multisig is flattened for batch. So avoiding copy seems significant. The node is currently implemented such that there is no copy cost to produce the table, and the table itself is structed to be fed directly into the engine. The tables are necessarily structured "horizontally" (each row contains a tuple). However the engine seems to require a "vertical" structure - where there are three (four with keys) columns of data: sig-hashes, public-keys, signatures, correlation-keys. The bridge is copying the entire buffer in order to produce this transformation. So over the course of a single full chain validation we will stream .5TB of signature data, and that will be copied into another .5TB (in chunks) to create this transformation. Can you confirm that this is correct, and whether is absolutely necessary?