Module casper_node::types

source ·
Expand description

Common types used across multiple components.

Re-exports§

Modules§

  • The chainspec is a set of configuration options for the network. All validators must apply the same set of options in order to join and act as a peer in a given network.
  • Errors that may be emitted by methods for common types.
  • Types which are serializable to JSON, which map to types defined outside this module.
  • Peers map.

Structs§

  • A struct containing a signature of a deploy hash and the public key of the signer.
  • The cryptographic hash of the bytesrepr-encoded set of approvals for a single deploy.
  • An unbroken, inclusive range of blocks.
  • A proposed block after execution, with the resulting post-state-hash. This is the core component of the Casper linear blockchain.
  • Wrapper around block and its deploys.
  • The body portion of a block.
  • Represents execution results for all deploys in a single block or a chunk of this complete value.
  • ID of the request for block execution results or chunk.
  • Helper struct to on-demand deserialize a trie or chunk ID for display purposes.
  • A cryptographic hash identifying a Block.
  • The header portion of a Block.
  • A storage representation of finality signatures with the associated block hash.
  • Summary information from the chainspec.
  • A deploy; an item containing a smart contract along with the requester’s signature(s).
  • The cryptographic hash of a Deploy.
  • The header portion of a Deploy.
  • Error returned when a Deploy is too large.
  • A validator’s signature of a block, to confirm it is finalized. Clients and joining nodes should wait until the signers’ combined weight exceeds their fault tolerance threshold before accepting the block as finalized.
  • The piece of information that will become the content of a future block after it was finalized and before execution happened yet.
  • Result for “info_get_status” RPC response.
  • A JSON-friendly representation of Block.
  • JSON representation of a block header.
  • Node fast-sync configuration.
  • Data feed for client “info_get_status” endpoint.
  • Represents the ID of a TrieOrChunk - containing the index and the root hash. The root hash is the hash of the trie node as a whole. The index is the index of a chunk if the node’s size is too large and requires chunking. For small nodes, it’s always 0.
  • Helper struct to on-demand deserialize a trie or chunk ID for display purposes.

Enums§

Traits§

  • Implemented for types that are chunked when sending over the wire and/or before storing the trie store.
  • An object-safe RNG trait that requires a cryptographically strong random number generator.
  • Indicates that a type knows how to approximate its memory usage.

Type Aliases§

  • The cryptographically secure RNG used throughout the node.
  • Represents an enum that can contain either a whole trie or a chunk of it.

Derive Macros§

  • Automatically derive the DataSize trait for a type.