| Implements schema and functions related to Ethereum's block. |
|---|
Note: this README reflects the state of the library from v3.0.0 onwards. See README from the standalone repository for an introduction on the last preceding release.
To obtain the latest version, simply require the project using npm:
npm install @ethereumjs/blockNote: If you want to work with EIP-4844 related functionality, you will have additional manual installation steps for the KZG setup, see related section below.
There are five static factories to instantiate a Block:
Block.fromBlockData(blockData: BlockData = {}, opts?: BlockOptions)Block.fromRLPSerializedBlock(serialized: Buffer, opts?: BlockOptions)Block.fromValuesArray(values: BlockBuffer, opts?: BlockOptions)Block.fromRPC(blockData: JsonRpcBlock, uncles?: any[], opts?: BlockOptions)Block.fromJsonRpcProvider(provider: string | EthersProvider, blockTag: string | bigint, opts: BlockOptions)
For BlockHeader instantiation analog factory methods exists, see API docs linked below.
Instantiation Example:
import { BlockHeader } from '@ethereumjs/block'
const headerData = {
number: 15,
parentHash: '0x6bfee7294bf44572b7266358e627f3c35105e1c3851f3de09e6d646f955725a7',
difficulty: 131072,
gasLimit: 8000000,
timestamp: 1562422144,
}
const header = BlockHeader.fromHeaderData(headerData)Properties of a Block or BlockHeader object are frozen with Object.freeze() which gives you enhanced security and consistency properties when working with the instantiated object. This behavior can be modified using the freeze option in the constructor if needed.
API Usage Example:
try {
await block.validateData()
// Block data validation has passed
} catch (err) {
// handle errors appropriately
}This library supports the creation of EIP-1559 compatible blocks starting with v3.3.0. For this to work a Block needs to be instantiated with a Hardfork greater or equal to London (Hardfork.London).
import { Block } from '@ethereumjs/block'
import { Chain, Common, Hardfork } from '@ethereumjs/common'
const common = new Common({ chain: Chain.Mainnet, hardfork: Hardfork.London })
const block = Block.fromBlockData(
{
header: {
baseFeePerGas: BigInt(10),
gasLimit: BigInt(100),
gasUsed: BigInt(60),
},
},
{ common }
)
// Base fee will increase for next block since the
// gas used is greater than half the gas limit
block.header.calcNextBaseFee().toNumber() // 11
// So for creating a block with a matching base fee in a certain
// chain context you can do:
const blockWithMatchingBaseFee = Block.fromBlockData(
{
header: {
baseFeePerGas: parentHeader.calcNextBaseFee(),
gasLimit: BigInt(100),
gasUsed: BigInt(60),
},
},
{ common }
)EIP-1559 blocks have an extra baseFeePerGas field (default: BigInt(7)) and can encompass FeeMarketEIP1559Transaction txs (type 2) (supported by @ethereumjs/tx v3.2.0 or higher) as well as Transaction legacy txs (internal type 0) and AccessListEIP2930Transaction txs (type 1).
Starting with the v4.1.0 release there is (experimental) support for EIP-4895 beacon chain withdrawals. Withdrawals support can be activated by initializing a respective Common object and then use the withdrawals data option to pass in system-level withdrawal operations together with a matching withdrawalsRoot (mandatory when EIP-4895 is activated) along Block creation, see the following example:
import { Block } from '@ethereumjs/block'
import { Common, Chain } from '@ethereumjs/common'
import { Address } from '@ethereumjs/util'
import type { WithdrawalData } from '@ethereumjs/util'
const common = new Common({ chain: Chain.Mainnet, eips: [4895] })
const withdrawal = <WithdrawalData>{
index: BigInt(0),
validatorIndex: BigInt(0),
address: new Address(Buffer.from('20'.repeat(20), 'hex')),
amount: BigInt(1000),
}
const block = Block.fromBlockData(
{
header: {
withdrawalsRoot: Buffer.from(
'69f28913c562b0d38f8dc81e72eb0d99052444d301bf8158dc1f3f94a4526357',
'hex'
),
},
withdrawals: [withdrawal],
},
{
common,
}
)Validation of the withdrawals trie can be manually triggered with the newly introduced async Block.validateWithdrawalsTrie() method.
This library supports an experimental version of the blob transaction type introduced with EIP-4844 as being specified in the 01d3209 EIP version from February 8, 2023 and deployed along eip4844-devnet-4 (January 2023) starting with v4.2.0.
To create blocks which include blob transactions you have to active EIP-4844 in the associated @ethereumjs/common library:
import { Common, Chain, Hardfork } from '@ethereumjs/common'
const common = new Common({ chain: Chain.Mainnet, hardfork: Hardfork.Shanghai, eips: [4844] })Note: Working with blob transactions needs a manual KZG library installation and global initialization, see KZG Setup for instructions.
The block library supports the creation as well as consensus format validation of PoW ethash and PoA clique blocks (so e.g. do specific extraData checks on Clique/PoA blocks).
Consensus format validation logic is encapsulated in the semi-private BlockHeader._consensusFormatValidation() method called from the constructor. If you want to add your own validation logic you can overwrite this method with your own rules.
Note: Starting with v4 consensus validation itself (e.g. Ethash verification) has moved to the Blockchain package.
An Ethash/PoW block can be instantiated as follows:
import { Block } from '@ethereumjs/block'
import { Chain, Common } from '@ethereumjs/common'
const common = new Common({ chain: Chain.Mainnet })
console.log(common.consensusType()) // 'pow'
console.log(common.consensusAlgorithm()) // 'ethash'
const block = Block.fromBlockData({}, { common })To calculate the difficulty when creating the block pass in the block option calcDifficultyFromHeader with the preceding (parent) BlockHeader.
A clique block can be instantiated as follows:
import { Block } from '@ethereumjs/block'
import { Chain, Common } from '@ethereumjs/common'
const common = new Common({ chain: Chain.Goerli })
console.log(common.consensusType()) // 'poa'
console.log(common.consensusAlgorithm()) // 'clique'
const block = Block.fromBlockData({}, { common })For sealing a block on instantiation you can use the cliqueSigner constructor option:
const cliqueSigner = Buffer.from('PRIVATE_KEY_HEX_STRING', 'hex')
const block = Block.fromHeaderData(headerData, { cliqueSigner })Additionally there are the following utility methods for Clique/PoA related functionality in the BlockHeader class:
BlockHeader.cliqueSigHash()BlockHeader.cliqueIsEpochTransition(): booleanBlockHeader.cliqueExtraVanity(): BufferBlockHeader.cliqueExtraSeal(): BufferBlockHeader.cliqueEpochTransitionSigners(): Address[]BlockHeader.cliqueVerifySignature(signerList: Address[]): booleanBlockHeader.cliqueSigner(): Address
See the API docs for detailed documentation. Note that these methods will throw if called in a non-Clique/PoA context.
Merge-friendly Casper/PoS blocks have been introduced along with the v3.5.0 release. Proof-of-Stake compatible execution blocks come with their own set of header field simplifications and associated validation rules. The difficulty is set to 0 since not relevant anymore, just to name an example. For a full list of changes see EIP-3675.
You can instantiate a Merge/PoS block like this:
import { Block } from '@ethereumjs/block'
import { Chain, Common, Hardfork } from '@ethereumjs/common'
const common = new Common({ chain: Chain.Mainnet, hardfork: Hardfork.Merge })
const block = Block.fromBlockData(
{
// Provide your block data here or use default values
},
{ common }
)Generated TypeDoc API Documentation
Starting with v4 the usage of BN.js for big numbers has been removed from the library and replaced with the usage of the native JS BigInt data type (introduced in ES2020).
Please note that number-related API signatures have changed along with this version update and the minimal build target has been updated to ES2020.
Tests in the tests directory are partly outdated and testing is primarily done by running the BlockchainTests from within the @ethereumjs/vm package.
To avoid bloating this repository with ethereum/tests JSON files, we usually copy specific JSON files and wrap them with some metadata (source, date, commit hash). There's a helper to aid in that process and can be found at wrap-ethereum-test.sh.
See our organizational documentation for an introduction to EthereumJS as well as information on current standards and best practices. If you want to join for work or carry out improvements on the libraries, please review our contribution guidelines first.