Types used in the public API
This crate stores Tetsy Vapory specific types that are COMMONLY used across different separate modules of the codebase. It should only focus on data structures, not any logic that relates to them.
The interaction between modules should be possible by implementing a required trait that potentially uses some of the data structures from that crate.
NOTE If you can specify your data type in the same crate as your trait, please do that.
Don’t treat this crate as a bag for any types that we use in Tetsy Vapory.
This one is reserved for types that are shared heavily (like transactions),
historically this contains types extracted from
vapcore crate, if possible
we should try to dissolve that crate in favour of more fine-grained crates,
by moving the types closer to where they are actually required.
Diff between two accounts.
Actions on ancestry blocks when working on a new block.
Basic account type – the decoded RLP from the state trie.
Base data structure of this module is
General block status
Blockhain info type definition
Call analytics related types
Types pertaining to sending messages and finding routes through the chain. Used mostly by the ChainNotify trait.
Client related types.
Data format for importing/exporting blocks from disk
Lazily-decoded owning views of RLP-encoded blockchain objects. These views are meant to contain trusted data – without encoding errors or inconsistencies.
General error types for use in tetsy-vapory.
Calculate import route for newly inserted blocks.
Log entry type definition.
Information about portions of the state and chain which the client may serve.
Indication of how secure the chain is.
Snapshot type definitions
State diff module.
Trace filter related types
Tree route info type definition
Block oriented views onto rlp.
Create a view into RLP-data
Type for block number.