Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accommodate variable length Block<T>.PreEvaluationHash for Block<T>.Transactions ordering #1322

Closed
greymistcube opened this issue Jun 1, 2021 · 0 comments · Fixed by #1326 or #1518
Assignees
Labels
discussion needed We need to dicuss about this

Comments

@greymistcube
Copy link
Contributor

Current "reordering" algorithm of Block<T>.Transactions depend on Block<T>.PreEvaluationHash's bit length to be longer than that of the target reference values, currently XOR aggregated Transaction<T>.Id. Pertaining to #1314, allowing a usage of custom hash function with different output length for computing Block<T>.PreEvaluationHash is in the works. Block<T>.Transactions ordering mechanism should reflect/accommodate the upcoming change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion needed We need to dicuss about this
Projects
None yet
1 participant