Transaction data is permanently recorded in files called blocks. They can be thought of as the individual pages of a city recorder's recordbook (where changes to title to real estate are recorded) or a stock transaction ledger. Blocks are organized into a linear sequence over time (also known as the block chain). New transactions are constantly being processed by miners into new blocks which are added to the end of the chain. As blocks are buried deeper and deeper into the blockchain they become harder and harder to change or remove.
Blocks in Jax.Network
According to JaxNet protocol, blocks consist of two parts: block header and block body. This design improves the throughput of information across the network. Typically the block header contains the most important data. It includes the reference to the body of the block and the commitment of previous block headers in the chain.
Beacon сhain blocks
|Beacon Chain Block structure|
|Magic no||value always 0x||4 bytes|
|Blocksize||number of bytes following up to the end of the block||4 bytes|
|Block Header||Encoding size||number of bytes occupied by the Merge-mining Tree encoding||4 bytes|
|Blockheader||consists of 8 items||120-165 bytes|
|Block Body||Transaction counter||positive integer VI = VarInt||1 - 9 bytes|
|transactions||the (non empty) list of transactions||<Transaction counter>-many transactions|
|BitcoinAux||Bitcoin header||header of the associated Bitcoin block-candidate||80 bytes|
|Coinbase Tx||Bitcoin block-candidate coinbase transaction||?|
|Coinbase MP||Merkle Proof of the coinbase transaction||0 - 384 bytes|