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
cost model current does not have account data size info to incorporate into transaction cost calculation.
Proposed Solution
We should be incorporating the cost of the account data sizes. We could feed that information back to the cost tracker like we currently do for execution costs. If an account size is not in the cache we could keep a list of account size averages per program.
The text was updated successfully, but these errors were encountered:
This one is pretty old, a lot has changed. It looks to me there are at least two actions related to it:
Leaders to include account data size in block packing decision making; (and some clean up in that area)
Transaction to be charged with additional fee for loading account data (perhaps charge fee for extra Bytes loaded above some limits) @jeffwashington is this what you are thinking?
Problem
cost model current does not have account data size info to incorporate into transaction cost calculation.
Proposed Solution
We should be incorporating the cost of the account data sizes. We could feed that information back to the cost tracker like we currently do for execution costs. If an account size is not in the cache we could keep a list of account size averages per program.
The text was updated successfully, but these errors were encountered: