-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
BLS12 precompiles adjustments #2999
BLS12 precompiles adjustments #2999
Conversation
Make even with master
Make even
Make even
Make even
Make even
Apologies @shamatar, I accidentally hit "Ready for Review". Is this ready? If not feel free to leave a comment and remove it from that state. |
I've run the most current matterlabs EIP2537 code in besu, and I think the proposed parings costing is too low.
As an aside, the G2Add looks crazy high. Do I have a good sample vector? shemnon/besu@8c5185e#diff-deeb9a7636367c0fa3f1d0f88fd6d158R252 |
I'll check the case of G2 addition, but updated prices should be used in conjunction with the improvements in the "tuning" branch of the 1962 code, so you will easily fit into pairing prices. Go implementation used these optimizations from day one cause it is properly specialized. Sams should apply to e.g. BLST or MCL. |
It is ready, but I keep is as draft until there is a decision whether updated prices should go into YoloV2 or later. |
That branch lacks the 196/197 code. Numbers are all below curve, but I'm running on an i7, so we really need some standard "baseline" cpu (like a t3.micro), or some reference function that should consume some tuned amount of gas, that these should be run on.
|
…reum#2999)" This reverts commit 19afcb1.
Hm, "tuning" branch should have 196/197 code as it was branched from master after the addition of eip-196 there. My "reference" machine is i9 with 2.9 GHz and no turbo-boost that gives a constant around 30 MGas/second. So I give it a margin of 15% on top and round up. Looking at G2 addition and trying to understand why price was made so high. My benchmarks also suggest that it should be cheaper. |
Oh, bot has merged it... |
If the PR is authored by one of the EIP authors, or an EIP author approves the PR then it will get automerged. If you want to prevent that, mark the PR as a draft. |
Can someone re-open it? I've initially kept it as a draft for this purpose exactly, but unless I've done it by accident I didn't click any "approve" button. |
Looks like |
Hi, I'm a bot! This change was automatically merged because: - It only modifies existing Draft or Last Call EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing
Hi, I'm a bot! This change was automatically merged because: - It only modifies existing Draft or Last Call EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing
This PR perform the following updates and corrections: