Crate near_chain

Re-exports

pub use chain::collect_receipts;

pub use chain::Chain;

pub use chain::MAX_ORPHAN_SIZE;

pub use near_chain_primitives;

pub use store_validator::ErrorMessage;

pub use store_validator::StoreValidator;

pub use types::BlockStatus;

pub use types::ChainGenesis;

pub use types::Provenance;

pub use types::RuntimeAdapter;

Modules

chain

migrations

missing_chunks

store_validator

test_utils

types

validate

Macros

byzantine_assert

Structs

ChainStore

All chain-related database operations.

Doomslug

Contains all the logic for Doomslug, but no integration with chain or storage. The integration happens via PersistentDoomslug struct. The split is to simplify testing of the logic separate from the chain.

Error

Enums

Block

Versioned Block data structure. For each next version, document what are the changes between versions.

BlockHeader

Versioned BlockHeader data structure. For each next version, document what are the changes between versions.

DoomslugBlockProductionReadiness

The result of processing an approval.

DoomslugThresholdMode

The threshold for doomslug to create a block. TwoThirds means the block can only be produced if at least 2/3 of the stake is approving it, and is what should be used in production (and what guarantees finality) NoApprovals means the block production is not blocked on approvals. This is used in many tests (e.g. cross_shard_tx) to create lots of forkfulness.

ErrorKind

Traits

ChainStoreAccess

Accesses the chain store. Used to create atomic editable views that can be reverted.

Functions

create_light_client_block_view

Creates the LightClientBlock from the information in the chain store for a given block.

get_epoch_block_producers_view

Type Definitions

ChainStoreUpdate

Provides layer to update chain without touching the underlying database. This serves few purposes, main one is that even if executable exists/fails during update the database is in consistent state.

ReceiptResult

Map of shard to list of receipts to send to it.