Current versions and limits

Sepolia testnet replaces Goerli testnet.

Goerli testnet support is now removed.

For more information, including bridge support for Sepolia, see Starknet Goerli Deprecation in the Starknet Dev News newsletter.

Current versions

Table 1. Current versions supported in each Starknet environment
Environment	Starknet version	Sierra version	Cairo version
Mainnet	0.13.3	1.6.0	2.0.0 - 2.8.2
Sepolia Testnet	0.13.3	1.6.0	2.0.0 - 2.8.2

Current limits

The following limits are subject to revisions and change on a regular basis

Blockifier-related constants and limits are defined, for each Starknet version starting from v0.13.0, in a JSON file called versioned_constants in this directory.

Table 2. Starknet’s current limits
Entity	Description	Sepolia	Mainnet
Block time	The maximum amount of time within which a pending block is closed, if no other limit is met.	30 seconds	30 seconds
Block limit (Cairo steps)	The maximum number of Cairo steps that can be completed within each block to ensure block production times remain consistent and predictable.	40,000,000	40,000,000
Block limit (gas)	Certain Starknet operations, such as sending messages between L1 and L2, consume Ethereum gas. 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.	5,000,000	5,000,000
Max transaction size (Cairo steps)	The maximum number of computational steps, measured in Cairo steps, that a transaction can contain when processed on the Starknet network. This limit is important for ensuring the efficient execution of transactions and preventing potential congestion.	10,000,000	10,000,000
Max number of events per transaction	The maximum number of events that a transaction can emit during its execution.	1,000	1,000
Max number of data felts per event	The maximum number of felts that an event can contain in its `data` array.	300	300
Max number of key felts per event	The maximum number of felts that an event can contain in its `keys` array.	50	50
Max Cairo steps for `validate`	The maximum number of computational steps, measured in Cairo steps, for a `validate` function.	1,000,000	1,000,000
Max contract bytecode size (Number of felts in the program)	The maximum size of the bytecode or program that a smart contract can have on Starknet. Bytecode is the low-level code that comprises smart contracts. Limiting this size helps manage the complexity of contracts and the overall efficiency of the network.	81,290	81,290
Max contract class size	The maximum size for a contract class within Starknet. Contract classes are a fundamental building block for smart contracts, and limiting their size can have implications for the network’s scalability and security.	4,089,446 bytes	4,089,446 bytes
IP address limits (read/write)	In order to reduce network spam, Starknet limits the amount of contract reads and writes that a single IP address can make.	200 per min per IP address	200 per min per IP address
Signature length (felts)		4,000	4,000
Calldata length (felts)		4,000	4,000