REFERENCE
Glossary
Short definitions of the terms used in the xOne guides. Each term has one canonical entry on this page.
- Conformance
- Proof, by test, that a client gives the same result as a reference client for the same input. Passing a test range is evidence for that range only. ParityThe state of two clients giving the same block hash, state root and receipts root for the same blocks. Parity is measured over a stated block range., State rootA hash in the block header that commits to the full state after the block. Two clients that disagree on a state root have diverged..
- Epoch
- A fixed span of blocks. At an epoch boundary the XDPoS rules recompute the masternode set, so boundaries are important test points. XDPoSThe consensus rules of XDC Network. A set of masternodes produce and validate blocks. A client must follow these rules to agree with the network., MasternodeA node that the XDPoS rules select to produce and vote on blocks. A follower node does not produce blocks..
- EVM
- The Ethereum Virtual Machine. It runs contract code and changes state as the rules of the chain define. Execution clientSoftware that checks blocks and transactions, runs the EVM and keeps the resulting state. The xOne family has four execution clients for XDC Network., StateThe account balances, contract code and contract storage at one block. History (headers, bodies, receipts) is separate data. See the storage guide..
- Execution client
- Software that checks blocks and transactions, runs the EVM and keeps the resulting state. The xOne family has four execution clients for XDC Network. EVMThe Ethereum Virtual Machine. It runs contract code and changes state as the rules of the chain define., StateThe account balances, contract code and contract storage at one block. History (headers, bodies, receipts) is separate data. See the storage guide., XDPoSThe consensus rules of XDC Network. A set of masternodes produce and validate blocks. A client must follow these rules to agree with the network..
- Follower
- A node that syncs and verifies the chain but does not produce blocks. The run-a-node guide shows a Rust follower on Apothem. Sync modeHow a node gets its starting data: replay every block (full) or fetch a recent state from peers (snap or fast). Each mode has its own limits. Read the client guide before you change it., MasternodeA node that the XDPoS rules select to produce and vote on blocks. A follower node does not produce blocks..
- JSON-RPC
- The request and response protocol that applications use to read from a node, for example eth_blockNumber. Support differs by client, method and transport. RPC namespaceA group of JSON-RPC methods with one prefix, such as eth_ or debug_. Enable only the namespaces that an application needs..
- Masternode
- A node that the XDPoS rules select to produce and vote on blocks. A follower node does not produce blocks. XDPoSThe consensus rules of XDC Network. A set of masternodes produce and validate blocks. A client must follow these rules to agree with the network., EpochA fixed span of blocks. At an epoch boundary the XDPoS rules recompute the masternode set, so boundaries are important test points..
- Parity
- The state of two clients giving the same block hash, state root and receipts root for the same blocks. Parity is measured over a stated block range. ConformanceProof, by test, that a client gives the same result as a reference client for the same input. Passing a test range is evidence for that range only., State rootA hash in the block header that commits to the full state after the block. Two clients that disagree on a state root have diverged..
- Quorum certificate
- In XDPoS v2, a set of enough masternode votes for a block. A client that verifies blocks checks these certificates. XDPoSThe consensus rules of XDC Network. A set of masternodes produce and validate blocks. A client must follow these rules to agree with the network., MasternodeA node that the XDPoS rules select to produce and vote on blocks. A follower node does not produce blocks..
- Retention
- How much history and state a node keeps on disk. Less retention uses less disk but can remove data that historical queries need. StateThe account balances, contract code and contract storage at one block. History (headers, bodies, receipts) is separate data. See the storage guide., Sync modeHow a node gets its starting data: replay every block (full) or fetch a recent state from peers (snap or fast). Each mode has its own limits. Read the client guide before you change it..
- RPC namespace
- A group of JSON-RPC methods with one prefix, such as eth_ or debug_. Enable only the namespaces that an application needs. JSON-RPCThe request and response protocol that applications use to read from a node, for example eth_blockNumber. Support differs by client, method and transport..
- State
- The account balances, contract code and contract storage at one block. History (headers, bodies, receipts) is separate data. See the storage guide. RetentionHow much history and state a node keeps on disk. Less retention uses less disk but can remove data that historical queries need., State rootA hash in the block header that commits to the full state after the block. Two clients that disagree on a state root have diverged..
- State root
- A hash in the block header that commits to the full state after the block. Two clients that disagree on a state root have diverged. StateThe account balances, contract code and contract storage at one block. History (headers, bodies, receipts) is separate data. See the storage guide., ParityThe state of two clients giving the same block hash, state root and receipts root for the same blocks. Parity is measured over a stated block range., ConformanceProof, by test, that a client gives the same result as a reference client for the same input. Passing a test range is evidence for that range only..
- Sync mode
- How a node gets its starting data: replay every block (full) or fetch a recent state from peers (snap or fast). Each mode has its own limits. Read the client guide before you change it. FollowerA node that syncs and verifies the chain but does not produce blocks. The run-a-node guide shows a Rust follower on Apothem., RetentionHow much history and state a node keeps on disk. Less retention uses less disk but can remove data that historical queries need..
- XDPoS
- The consensus rules of XDC Network. A set of masternodes produce and validate blocks. A client must follow these rules to agree with the network. MasternodeA node that the XDPoS rules select to produce and vote on blocks. A follower node does not produce blocks., EpochA fixed span of blocks. At an epoch boundary the XDPoS rules recompute the masternode set, so boundaries are important test points., Quorum certificateIn XDPoS v2, a set of enough masternode votes for a block. A client that verifies blocks checks these certificates..