Accommodate variable length Block<T>.PreEvaluationHash
for Block<T>.Transactions
ordering
#1322
Labels
discussion needed
We need to dicuss about this
Current "reordering" algorithm of
Block<T>.Transactions
depend onBlock<T>.PreEvaluationHash
's bit length to be longer than that of the target reference values, currently XOR aggregatedTransaction<T>.Id
. Pertaining to #1314, allowing a usage of custom hash function with different output length for computingBlock<T>.PreEvaluationHash
is in the works.Block<T>.Transactions
ordering mechanism should reflect/accommodate the upcoming change.The text was updated successfully, but these errors were encountered: