-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
chore: update persistent-merkle-tree 0.6.1 #5969
Conversation
Performance Report✔️ no performance regression detected 🚀🚀 Significant benchmark improvement detected
Full benchmark results
|
I deployed to feat1 mainnet node, it does not work as expected (stable mainnet node takes < 58ms consistently). Could that be an issue of |
within lodestar, I think there are 2 persistent-merkle-tree:
we may need to set our hasher for both of them |
a0ed2cb
to
3596ab8
Compare
import {setHasher} from "@chainsafe/persistent-merkle-tree/lib/hasher/index.js"; | ||
|
||
// without setting this first, persistent-merkle-tree will use noble instead | ||
setHasher(hasher); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to set as-sha256
as default in the library? Consumers still have the option to use noble but it is then their responsibility and we don't have to make sure it is set correctly in Lodestar.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's decided to use noble as default implementation, see ChainSafe/ssz#313
🎉 This PR is included in v1.12.0 🎉 |
Motivation
Description
setHasher()
at the beginning to enforceas-sha256
in lodestar