pub(crate) fn transaction_hashes<T: NodeType>(
payload: &PayloadWithMetadata<T>,
pooled_hashes: &[Commitment<T::Transaction>],
) -> Vec<Commitment<T::Transaction>>Expand description
The payload’s transaction hashes, in any order: every consumer uses them as a set.
Building a payload can drop transactions but never changes, repeats or adds one, so a payload that kept as many transactions as the pool gave it holds exactly the pooled ones, and the pool’s hashes save hashing them again. Debug builds check this.