Ethereum Beacon Compute Units

Transaction Categories and Compute Units

Different transaction categories are assigned specific Compute Unit values. These CUs reflect the resources needed for each type of transaction.

Name	Value
/v1/beacon/genesis$	S
/v1/beacon/states	L
/v1/beacon/headers	S
/v1/beacon/blocks._	M
/v2/beacon/blocks._	M
/v1/beacon/blinded_blocks$	S
/v1/beacon/pool	S
/v1/config	XS
/v1/node	XS
/v1/beacon/states/*/root	S
/v1/beacon/states/*/fork	S
/v1/beacon/states/*/finality_checkpoints	S
/v1/beacon/states/*/validators$	L
/v1/beacon/states//validators/	M
/v1/beacon/states/*/validator_balances	M
/v1/beacon/states/*/committees	S
/v1/beacon/states/*/sync_committees	S
/v1/beacon/headers$	S
/v1/beacon/headers/*	S
/v1/beacon/blob_sidecars/*	S
/v1/beacon/blocks$	M
/v1/beacon/blinded_blocks	M
/v1/beacon/blocks/*	M
/v1/beacon/blocks/*/root	S
/v1/beacon/blocks/*/attestations	S
/v1/beacon/pool/attestations	S
/v1/beacon/pool/attester_slashings	S
/v1/beacon/pool/proposer_slashings	S
/v1/beacon/pool/sync_committees	S
/v1/beacon/pool/voluntary_exits	S
/v1/beacon/config/fork_schedule	XS
/v1/beacon/config/deposit_contract	XS
/v1/beacon/node/peer_count	XS
/v1/beacon/node/version	XS
/v1/beacon/node/syncing	XS
/v1/beacon/node/health	XS

Updated 3 months ago