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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
For computing the weight cost of put_code we fetch the schedule from the storage. However, accessing the storage within the validate_transaction path is discouraged. That's why we should consider switching the put_code_per_byte_cost to be a const.
The text was updated successfully, but these errors were encountered:
pepyakin
changed the title
pallet-contracts: avoid hitting the trie when computing weight
seal: avoid hitting the trie when computing weight
Jul 1, 2020
This will be solved for free once the proper weights arrive. The prices for the extrinsics are then read directly from the WeightInfo Trait and not from the schedule.
For computing the weight cost of
put_code
we fetch the schedule from the storage. However, accessing the storage within thevalidate_transaction
path is discouraged. That's why we should consider switching theput_code_per_byte_cost
to be a const.The text was updated successfully, but these errors were encountered: