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
Currently all function calls to a contract happen within the scope of a single transaction, however when we time travel to the future using boa.env.time_travel, a new block(or transaction) should be created. I am specifically requesting this because we use transient storage to cache values that are expensive to generate and would be valid through the transaction (the block even), however in the future these values wont be valid specifically because time is a component of these computations(things like amount of yield being generated).
The text was updated successfully, but these errors were encountered:
Based on #216 I understand the real issue is that we want to clear transient storage when time travelling.
Is that correct? Or is there more data that would need to change?
i think we should have a function called reset_transaction_context which does whatever we need for resetting transaction context. this includes clearing transient storage and resetting access acounters i think.
Currently all function calls to a contract happen within the scope of a single transaction, however when we time travel to the future using
boa.env.time_travel
, a new block(or transaction) should be created. I am specifically requesting this because we use transient storage to cache values that are expensive to generate and would be valid through the transaction (the block even), however in the future these values wont be valid specifically because time is a component of these computations(things like amount of yield being generated).The text was updated successfully, but these errors were encountered: