-
Notifications
You must be signed in to change notification settings - Fork 302
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
fees: add per-action block space calculations & representative values #4116
Conversation
d93f3c9
to
e66d183
Compare
e66d183
to
b14147c
Compare
Added some approximate block space estimates based on the proto fields, but for some data types (e.g. bytes, string) of variable size, I'm unsure if the chosen values (64 bytes?) are good approximations - do you have thoughts @hdevalence ? Also, are there any actions for which this draft is currently computing the length of the encoding which should be hard-coded? I chose the set of actions with bespoke associated |
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.
The numbers seem plausible, it would be good to have comments clarifying:
- what is being added up
- why we are not concerned about the exact byte size for the fixed-size actions (e.g., why it's ok to ignore protobuf framing), namely that it makes only a small difference in the action's gas cost and simplifies the accounting
b14147c
to
ff23599
Compare
ff23599
to
b00c0b8
Compare
b00c0b8
to
6b72b7b
Compare
…, fix proto comment on OutputBody size
6b72b7b
to
8a0478b
Compare
Draft example of current best interpretation for #3940 - any Action with a bespoke ActionPlan is currently given a block space value of "64" as a placeholder, but obviously that needs to change, just unsure how based on previous ticket comments.