-
Notifications
You must be signed in to change notification settings - Fork 478
[Feature] Authorization based execution fee estimation #1115
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8920e00 to
5a8e4bc
Compare
5a8e4bc to
844640c
Compare
79ce6d3 to
18409ca
Compare
18409ca to
753e35a
Compare
753e35a to
26a85af
Compare
26a85af to
1d4979a
Compare
1d4979a to
3d0ff17
Compare
3d0ff17 to
684b6ae
Compare
684b6ae to
40875f9
Compare
40875f9 to
8a47586
Compare
8a47586 to
6226636
Compare
6226636 to
7b73acb
Compare
7b73acb to
847e990
Compare
847e990 to
0e27aa9
Compare
0e27aa9 to
27aa4db
Compare
…rovide them to the function
27aa4db to
0341e35
Compare
c9a390e to
ce9b0fc
Compare
iamalwaysuncomfortable
approved these changes
Oct 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently execution fees are estimated from an execution which is costly, the new
execution_cost_for_authorizationfunction in snarkVM allows estimation from the authorization which is less costly.Changes
Change the existing
estimateExecutionFeefunction to generate the authorization, including generated inputs, and estimate the fee using that authorization with the new snarkVMexecution_cost_for_authorizationfunction.The function now takes fewer arguments as
proving_keyandverifying_keyare no longer needed.Test Plan
A unit test has been introduced comparing the output of the fee estimation of an authorization to the output of the fee estimation of the execution itself.