Current limits and triggers

Starknet alpha currently has a number of limits and triggers in place in order to keep the network stable and optimized for best performance.

These are subject to revisions and change on a regular basis

Table 1. Starknet current limits and triggers
Entity	Goerli	Mainnet
Block time	3 minutes	3 minutes
Block limit (Cairo steps)	8M	8M
Block limit (gas)	3M	3M
Max transaction size (Cairo steps)	3M	3M
Max contract bytecode size (No of felts in the program)	61440	61440
Max contract class size	20MB	20MB
Mempool size limit	No limitation	1000 transactions
IP address limits (read)	100 per min	200 per min
IP address limits (write)	10 per min / per ip address	10 per min / per ip address

Block limit (Cairo steps)

The execution of each transaction involves a certain number of computational steps.

Starknet enforces a limit on the number of steps that can be completed within each block to ensure block production times remain consistent and predictable.

Block limit (gas)

Certain Starknet operations consume Ethereum gas, e.g L1/L2 messages. The current L1 state update mechanism involves an Ethereum transaction for each Starknet block.

The gas limit for Starknet blocks is therefore inherited from the gas limit for Ethereum blocks.

The gas limit for Starknet blocks is inherited from the gas limit for Ethereum blocks.

Mempool size limit

The mempool contains transactions that have undergone a preliminary verification by the sequencer and are candidates for inclusion into a block.

IP address limits (read)

In order to reduce network spam, Starknet limits the amount of contract reads that a single IP address can make.

IP address limits (write)

In order to reduce network spam, Starknet limits the amount of contract writes that a single IP address can make.