Structs§
- Account
Token Data - Account
Wrap Mock Data - Accounts
- Additional
Account Data - Additional
Account Token Data - Altered
Account - Base
Execution Result - BaseExecutionResult defines the dto that will hold base information about execution result
- Base
Meta Execution Result - BaseMetaExecutionResult contains a base execution result and additional validator and fee-related fields
- Batch
- Transaction holds all the data needed for a value transfer or SC call
- Block
Data - Body
- Body
Header Pair - BodyHeaderPair holds a body and header hash pair
- Bootstrap
Data - BootstrapData is used to store information that are needed for bootstrap
- Bootstrap
Header Info - BootstrapHeaderInfo is used to store information about a header
- Code
Entry - Collapsed
Bn - Collapsed
En - Collapsed
Ln - Data
Trie Change - Delegated
ScVote Info - Delegated
With Address - Delegation
Config - Delegation
Contract List - Delegation
Contract Status - Delegation
Management - Delegation
Meta Data - Delegator
Data - Economics
- Economics holds the block information for total supply and rewards
- Element
InList - Epoch
ByHash - EpochByHash is used to store information about a hash to know which epoch it belongs to
- Epoch
Start - EpochStart holds the block information for end-of-epoch
- Epoch
Start Shard Data - EpochStartShardData hold the last finalized headers hash and state root hash
- Epoch
Validators With Auction - Esdt
Config - Esdt
Data V1 - Esdt
Data V2 - Esdt
Roles - Event
- Event holds all the data needed for an event structure
- Execution
Result - ExecutionResult defines the dto that will hold information about execution result
- Execution
Result Data - Execution
Result Info - ExecutionResultInfo contains a base execution result and the header round when the results was notarized
- FeeInfo
- Finalized
Block - Fund
- GasAnd
Fees - General
Proposal - Global
Fund Data - Governance
Config - Governance
Config V2 - Header
- Header holds the metadata of a block. This is the part that is being hashed and run through consensus. The header holds the hash of the body and also the link to the previous block header hash
- Header
GasConsumption - Header
Proof - HeaderProof defines a proof for a specific header
- Header
V2 - HeaderV2 extends the Header structure with extra fields for version 2
- Header
V3 - HeaderV3 defines the structure of the header V3
- Heartbeat
V2 - HeartbeatV2 represents the heartbeat message that is sent between peers from the same shard containing current node status
- Log
- Log holds all the data needed for a log structure
- LogData
- Message
- Message defines the data needed by spos to communicate between nodes over network in all subrounds
- Meta
Block - MetaBlock holds the data that will be saved to the metachain each round
- Meta
Block V3 - MetaBlockV3 holds all the fields needed for a meta block v3. This is the part that is being hashed and run through consensus.
- Meta
Execution Result - MetaExecutionResult contains a base meta execution result and extra fields for meta block results
- Meta
Execution Result Info - MetaExecutionResultInfo contains a base meta execution result and the header round when the results was notarized
- Meta
Trigger Registry - Meta
Trigger Registry V3 - Mini
Block - Mini
Block Header - Mini
Block Header Reserved - Mini
Block Reserved - Mini
Blocks InMeta - MiniBlocksInMeta is used to store all mini blocks hashes for a metablock hash
- Miniblock
Metadata - MiniblockMetadata is used to store information about a history transaction
- Nodes
Coordinator Registry With Auction - Nodes
Data - Ongoing
Voted List - Ongoing
Voted List V2 - Outport
Block - Outport
Config - Payload
- Payload represents the DTO used as payload for both HeartbeatV2 and PeerAuthentication messages
- Peer
Account Data - PeerAccountData represents the data that defines the PeerAccount
- Peer
Authentication - PeerAuthentication represents the DTO used to pass peer authentication information such as public key, peer id, signature, payload and the signature. This message is used to link the peerID with the associated public key
- Peer
Change - PeerChange holds a change in one peer to shard assignation
- Peer
Data - PeerData holds information about actions taken by a peer:
- Peer
Shard - PeerShard represents the data regarding a peer’s shard
- Pending
Mini Blocks Info - PendingMiniBlocksInfo is used to store information about the number of pending miniblocks
- Processed
Block Nonce - ProcessedBlock is used to store nonce of the latest processed block
- PubKeys
- Receipt
- Receipt holds all the data needed for a transaction receipt
- Request
Data - RequestData holds the requested data This struct will be serialized and sent to the other peers
- Results
Hashes ByTx Hash - ResultsHashesByTxHash is used to store smart contract results hashes and receipt hash for a transaction hash
- Reward
Computation Data - Reward
Info - Reward
Tx - RewardTx holds the data for a reward transaction
- Round
Info - Round
Num - Rounds
Info - ScResults
Hashes AndEpoch - ScrHashesAndEpoch is used to store smart contract results and epoch
- Scheduled
ScRs - ScrInfo
- Serializable
Validator - Shard
- Shard
Data - ShardData holds the block information sent by the shards to the metachain
- Shard
Data Proposal - ShardDataProposal holds the block information proposed by the shards
- Shard
Trigger Registry - Shard
Trigger Registry V2 - Shard
Trigger Registry V3 - Shard
Validator Info - ShardValidatorInfo represents the data regarding a validator that is stored in the PeerMiniblocks
- Sign
Rate - SignRate is used to keep the number of success and failed signings
- Smart
Contract Result - Staked
Data V10 - Staked
Data V11 - Staked
Data V20 - Staking
Nodes Config - State
Access - State
Accesses - State
Accesses ForBlock - Supply
Esdt - SupplyESDT is used to store information a shard esdt token supply
- Token
Meta Data - Topic
Message - Transaction
- Transaction holds all the data needed for a value transfer or SC call
- Transaction
Pool - Trie
Leaf Data - TxInfo
- Unstaked
Value - User
Account Data - Validator
Config - Validator
Data V1 - Validator
Data V2 - Validator
Info - ValidatorInfo represents the data regarding a validator that is verified by the metaNodes
- Validator
Rating Info - Validator
Statistics - ValidatorStatistics holds information about a validator
- Validators
- Validators
PubKeys - Validators
Rating - Waiting
List - WsMessage
- WsMessage contains all the information needed for a WebSocket message
Enums§
- Action
Type - Mini
Block State - Peer
Action - PeerAction type represents the possible events that a node can trigger for the metachain to notarize
- Processing
Type - Request
Data Type - RequestDataType represents the data type for the requested data
- Type
- Type identifies the type of the block
- Vote
Value Type