Expand description
§cuprate-types
Shared data types within Cuprate.
This crate is a kitchen-sink for data types that are shared across Cuprate.
§Features flags
Feature flag | Does what |
---|---|
blockchain | Enables the blockchain module, containing the blockchain database request/response types |
serde | Enables serde on types where applicable |
epee | Enables cuprate-epee-encoding on types where applicable |
proptest | Enables proptest::arbitrary::Arbitrary on some types |
json | Enables the json module, containing JSON representations of common Monero types |
hex | Enables the hex module, containing the HexBytes type |
Modules§
- Hexadecimal serde wrappers for arrays.
- This module contains types mappings for other common types to allow for easier JSON (de)serialization.
Structs§
- A block on an alternative chain.
- A block that can contain transactions.
- A unique ID for an alt chain.
- Information on a (maybe alternate) chain.
- Data of summed coinbase transactions.
- Extended header data of a block.
- Estimated fee data.
- Information on a
HardFork
. - Data to create a custom block template.
- A transaction in the txpool.
- A single entry in an output histogram.
- Input required to generate an output histogram.
- An already existing transaction output.
- A pruned transaction with the hash of the missing prunable data
- Data needed to verify a transaction.
- Verified information of a block.
- Verified information of a transaction.
Enums§
- Represents if a transaction has been fully validated and under what conditions the transaction is valid in the future.
- An identifier for a chain.
- An identifier for every hard-fork Monero has had.
- An error working with a
HardFork
. - Transaction blobs within
BlockCompleteEntry
. - An enum representing all valid Monero transaction versions.