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
You start a process using a locally connected node and Ape... it deploys a contract.
In another shell, you connect to the same node. You have access to the contract type but the instance is not cached to disk and not in your new process's memory and so you have to either copy it in yourself and dig through account history and make assumptions.
Specification
create a local cache for contract instances, much like live networks, except have it get cleaned up in the end.
the best to clean it up actually is during the starting of the process.
if ape is not starting any process, it wont clean.
if you end a proces and re start, it will have a fresh cleaned env
Dependencies
Include links to any open issues that must be resolved before this feature can be implemented.
The text was updated successfully, but these errors were encountered:
Overview
Imagine this:
You start a process using a locally connected node and Ape... it deploys a contract.
In another shell, you connect to the same node. You have access to the contract type but the instance is not cached to disk and not in your new process's memory and so you have to either copy it in yourself and dig through account history and make assumptions.
Specification
create a local cache for contract instances, much like live networks, except have it get cleaned up in the end.
the best to clean it up actually is during the starting of the process.
if ape is not starting any process, it wont clean.
if you end a proces and re start, it will have a fresh cleaned env
Dependencies
Include links to any open issues that must be resolved before this feature can be implemented.
The text was updated successfully, but these errors were encountered: