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
The opcodes that return the size of code associated with codes needs to be optimised. This is because the code which is loaded from the database needs to be authenticated / constrained via hashing. Instead scroll implements an optimisation in which the code size is stored within the account data structure. My proposal would be to make use of the ExternalContext to store this information. Alternatively we could keep a cache of this information in the database data structure and whenever we load an account from the state trie we populate the code info object with the information.
Design
A proposed design of the cache that would store this data looks as follows:
Overview
The opcodes that return the size of code associated with codes needs to be optimised. This is because the code which is loaded from the database needs to be authenticated / constrained via hashing. Instead scroll implements an optimisation in which the code size is stored within the account data structure. My proposal would be to make use of the
ExternalContext
to store this information. Alternatively we could keep a cache of this information in the database data structure and whenever we load an account from the state trie we populate the code info object with the information.Design
A proposed design of the cache that would store this data looks as follows:
The text was updated successfully, but these errors were encountered: