Mining: Genesis Block
Explore the unique features of the block.
Multichains vs Blockchains
Overline does not use a traditional blockchain but a "multichain" which means that each block within Overline contains blocks or references to blocks from other blockchains. Multichains include much of the same functionality as their counterpart however transactions and contracts written in a multichain can uniquely interact with the connected blockchains they represent.
Review the raw genesis block which has been formatted to show the messages and signatures of the individuals who participated in Overline's Private and Public Genesis.
This is used for backwards support and contextual validation of the genesis block.
There are three supported types, 0, 1, 2, 3, and 6. "0" is a Before Target (BT) Genesis Block. "1" is a After Target (AT) Genesis Block. "2" and "3" are Before Governance (BG) and After Governance (AG) Genesis Block.
A unique key referencing the given block.
The hash of the previous block.
The hash of the after target block. The hash is concatenated with the merkleRoot of the after target block and signed by the public key referenced in afterTargetMiner.
The block height or number of blocks after which the block referenced afterTargetHash can by used as the next next block.
The public key which must provide the signature of the block which is used once the target parameters have been assigned.
The signature of the new data structure signed by the public key set in the target miner field.
The current height of the blockchain. This height is "0" when type is "0" otherwise it is > 0.
The address which may transfer the Overline reward of the block after 100 blocks.
A numeral value which represents the distance minimum of the block. It is used as an input to determine the distance or difficulty of the next block.
The Overline granted to the block (not including fees).
The UNIX epoch of the creation of the block. The timestamp is "0" for the genesis block or whenever the type changes and a new target block is adopted.
The merkleRoot is a combination of the txList, emblemChainAddress, emblemChainFingerprintRoot, blockchainFingerprintsRoot, minerAddress, nonce, previousHash, and timestamp. It's purpose is to guarantee the data integrity of the block.
The tamper protection again the state of the height of the provided blocks. This is relevant for blockchains or data structures where the block is non-unique or for identifying the hierarchy of super colliders. The chain root optionally contains the afterTargetMiner if the type is a before target block.
The raw nonce which when hashed is used to measure the distance or difficulty of the block.
To be announced.
To be announced.
If a fee is necessary from the miner, this is the minimum fee which can be assigned to the execution of a transaction.
The sum of the distances mined or otherwise included in the block must be below the txDistanceLimit.
The number of transactions contained within the block.
Contains the BEAM transactions of the block including callbacks, promises, and coinable transactions. Transactions in the txList combined with block identifying information to form the merkleRoot of the block.
The weight of the per Emblem balance in relation to the total transaction distance used by the block.
The unique hash referencing the blockchain which is to be used as the settlement layer for Emblem performance mining.
The address or state root referencing the Emblem contract or Emblem colored address origin. It is required for colliders which utilize the Emblem performance mining. This has the same operating functionality of the given block.
The hash of the block from which the Emblem balances state is valid.
An integer indicating the number of blockchains to expect in the fingerprints set.
A merkle root assembled from the fingerprints which ensures the fingerprint hashes and metadata are not tampered with.
Validation Only Contains the fingerprints of each blockchain which uniquely identifies the blockchain sequence of blocks to be used and the marked address for monitoring marked token transactions. View the raw data used in the actually genesis block.
A vector containing the header blocks of chains which are being absorbed into the collider.
Validation Only The balances if any of Emblem addresses. This is optional if emblemChainBlockHash is provided.
Updated 29 days ago
View the serialized human readable raw genesis block.