Module database 

The ArbiterDB is a wrapper around a CacheDB that is used to provide access to the Environment’s database to multiple Coprocessors. It is also used to be able to write out the Environment database to a file.

Further, it gives the ability to be generated from a fork::Fork so that you can preload an environment::Environment with a specific state.

Modules

fork

This module contains the Fork struct which is used to store the data that will be loaded into an [Environment] and be used in arbiter-core. Fork contains a CacheDB and ContractMetadata so that the [Environment] can be initialized with a forked database and the end-user still has access to the relevant metadata.

inspector

This module contains an extensible Inspector called ArbiterInspector. It is currently configurable in order to allow for users to set configuration to see logs generated in Solidity contracts and or enforce gas payment.

Structs

AccountRecord

AccountRecord describes metadata about an account within the state trie.

AnvilDump

AnvilDump models the schema of an anvil state dump.

ArbiterDB

A ArbiterDB is contains both a CacheDB that is used to provide state for the environment::Environment’s as well as for multiple coprocessor::Coprocessors. The logs field is a HashMap to store ethers::types::Logs that can be queried from at any point.