You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reducing the number of different hash functions being used, reduces the complexity.
Ideally, we only use sha256 since you need this for l2 to l1 communications, but the cost of sha256 is too high and when we implement poseidon we will likely want to use that instead of sha256 due to it being at least two order of magnitude cheaper in a SANRK
The text was updated successfully, but these errors were encountered:
Related to #2859
Opening this up in the case that there are no blockers to removing
blake3
# Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if
the PR is ready to merge.
- [ ] If the pull request requires a cryptography review (e.g.
cryptographic algorithm implementations) I have added the 'crypto' tag.
- [ ] I have reviewed my diff in github, line by line and removed
unexpected formatting changes, testing logs, or commented-out code.
- [ ] Every change is related to the PR description.
- [ ] I have
[linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
this pull request to relevant issues (if any exist).
Observation
Ideally, we only use sha256 since you need this for l2 to l1 communications, but the cost of sha256 is too high and when we implement poseidon we will likely want to use that instead of sha256 due to it being at least two order of magnitude cheaper in a SANRK
The text was updated successfully, but these errors were encountered: