You can get the latest updates delivered to your inbox by subscribing to the Starknet Devs Newsletter.
​
Starknet v0.14.0 (September 1, '25)
Starknet v0.14.0 is live on Testnet and scheduled to be live on Mainnet on September 1st.This version includes the following changes:
  • Block time is shorten from ~30 seconds to ~6 seconds
  • Decentralized sequencing is introduced, with three sequencers, each with its own mempool, taking turns building blocks and reaching consensus using the Tendermint protocol (the interfaces for submitting transactions to the gateway and syncing from the feeder gateway remain unchanged)
  • v0, v1, v2 and non-RPC v0.8 compatible v3 transactions are no longer supported, and a new meta_tx_v0 syscall is introduced to enable calling old accounts (i.e., ones without __validate__) via v3 transactions
  • RPC v0.9 is introduced, removing the REJECTED transaction status, changing the behavior of the RECEIVED transaction status, adding new CANDIDATE and PRE_CONFIRMED transaction statuses, and introducing the PRE_CONFIRMED block
  • The feeder gateway URL is now feeder.{chain_name}.starknet.io/feeder_gateway (while the gateway URL remains {chain_name}.starknet.io/gateway), adding a new get_preconfirmed_block endpoint, deprecating the get_oldest_transaction_age and get_number_of_transactions_in_backlog endpoints, and changing the behavior of the get_transaction_status endpoint
  • L1 handlers execution resources are bounded and failed L1 handlers are included as REVERTED in blocks
  • A fee market on the l2_gas resource is introduced, following Ethereum’s EIP 1559
  • Sequencers now maintain a mempool, decoupling the transaction order of arrival from the transaction ordering in blocks
  • The Starknet OS (SNOS) has been modified to receive multiple blocks as inputs, amortizing costs over a larger number of blocks
  • Transactions with internal calls to an entry point called __execute__ are now reverted
Additional resources:
​
Starknet v0.13.6 (July 8, '25)
Starknet v0.13.6 is live on Mainnet.This version is a configuration change done to support integration by the S-Two prover, including:
Cairo Native hasn’t yet been enabled on Mainnet, and disabling it only affects Sepolia.
Additional resources:
​
Starknet v0.13.4 and v0.13.5 (March 24, '25)
Starknet v0.13.4 and v0.13.5 are live on Mainnet. All the big improvements came in v0.13.4, and the v0.13.5 upgrade rolled out immediately after, bringing minor adjustments to help the ecosystem gear up for Starknet’s next upgrade.Starknet v0.13.4 includes the following changes:
  • Cairo Native Execution: Contracts compiled with Sierra ≥ 1.7.0 can run faster by being executed natively (without the Cairo VM)
  • L2 Gas Introduced: New fee type for L2-specific resources (computation, calldata, events)
  • Triple Gas Model: Transactions now support (and eventually require) bounds for L1 gas, L2 gas, and blob gas
  • Improved Error Handling: Contract panics no longer abort execution and instead return control to the caller
  • Stateful Compression: Smaller L1 blobs via smart key indexing to reduce data availability costs
  • New Wallet<>Dapp API: Decouples dApps from specific Starknet.js versions using a new WalletAccount class
  • JSON-RPC v0.8.0: Adds WebSocket support, better fee/resource tracking, and new endpoints
  • New Compiler (Cairo v2.10.0): Enables redeposit_gas, reduces worst-case fees, adds new syscalls
  • Updated Pricing: Builtins priced by trace complexity, often cheaper for users
Additional resources:
​
Starknet v0.13.3 (November 20, '24)
Blob gas on Starknet is now 5x cheaper (!) using:
  • Squashing discount factor: Users pay for the expected marginal contribution of their transaction to the blobs sent to L1
  • State diff compression: Starknet submits compressed state diffs to L1. To better lends itself to the new compression scheme as well as allow its construction to be based on the state diff alone, the uncompressed encoding of contract diff headers changes to: new_nonce (if changed) | n_updates | n_updates_len | flag
Where:
  • The semantics of flag is unchanged (i.e., it indicates whether or not the class was replaced)
  • n_updates_len is 0 if the number of updates is less than 256 (and therefore can fit in 8 bits), and 1 otherwise
  • n_updates can spread over 8 or 64 bits, depending on n_updates_len
  • If the nonce of the contract is unchanged, the value of new_nonce is zero (and not the unchanged nonce)
Additional resources:
​
Starknet v0.13.2 (August 28, '24)
New features and enhancements:
  • Optimistic parallelization in the sequencer.
  • Applicative recursion (“blockpacking”): pack a contiguous sequence of blocks into a single L1 state update, instead of just one block. This change also affects the Starknet core contract on L1 and the structure of data availability.
  • New block hash definition: see the reference implementation here.
API changes:
  • Feeder gateway: All objects containing the block hash will use the new block hash computation. Receipts will contain a new property total_gas_consumed, only for transactions after v0.13.2. Three new builtins can appear in the builtin_instance_counter property of execution_resources in the transaction receipts: add_mod, mul_mod and range_check96. End support for the endpoints get_block_traces and get_transaction_trace.
  • JSON RPC: No changes in v0.13.2. The new JSON RPC version v0.8.0 will be released alongside Starknet v0.13.3.
Cairo: A new compiler version will be released for v0.13.2, Cairo v2.7.0. This includes a Sierra upgrade to v1.6.0. The Starknet-related features include sha256 syscall and Circuit builtin.Additional resources:
​
Starknet v0.13.1.1 (April 15, '24)
In response to community feedback, Starknet 0.13.1.1 reduces class declaration fees and increases the calldata limit:Fee reductions:
  • CASM bytecode: 28 gas/felt → 1 gas/felt
  • Sierra bytecode: 28 gas/felt → 1 gas/felt
  • ABI: 0.875 gas/character → 0.032 gas/character
Limit increases:
  • Calldata length: 4,000 felts → 5,000 felts
​
Starknet v0.13.1 (March 13, '24)
New features and enhancements:
  • Cheaper data availability (DA): Starknet uses EIP-4844. State diffs are now blobs, rather than calldata, requiring the addition of data_gas to the Starknet block header.
  • Time-related syscalls when called from an account contract’s __validate__, __validate_deploy__, __validate_declare__, or constructor function: block_timestamp returns the hour, rounded down. block_number returns the block number, rounded down to the nearest multiple of 100.
  • Optimization: Load into memory only the functions in a contract that are actually used when generating the proof.
Block header updates: The block header includes new fields: l1_da_mode, l1_data_gas_price, and l1_gas_price.API: JSON RPC: Starknet 0.13.1 is backward compatible with starknet_api_openrpc.json v0.6.0. A new version 0.7.0 accommodates the changes introduced by Starknet using EIP-4844.Pricing changes:
  • Computation: A Cairo step now costs 0.0025 gas/step, a 50% reduction. All builtins costs are accordingly reduced by 50%.
  • Calldata and signatures: Each felt in the calldata and signature arrays of all transaction types now costs 0.128 gas/felt.
  • Class declaration: Each felt of a sierra_program and bytecode now costs 28 gas/felt. Each character in the ABI costs 0.875 gas.
  • Events: An additional felt to the data array costs 0.128 gas/felt. An additional felt to the keys array costs 0.256 gas/felt.
Additional resources:
​
Starknet v0.13.0 (January 10, '24)
Starknet v0.13.0 is live on Mainnet.Starknet 0.13.0 includes the following changes:
  • v3 transactions, including fee payment in STRK and reserved fields for future features, such as Volition and payment master
  • get_block API: The gas_price field is replaced by the eth_l1_gas_price and strk_l1_gas_price fields. This change applies also to existing blocks. For more information on the new fields, see the JSON RPC API Spec on GitHub
  • Sierra v1.4.0. This new version of Sierra is part of Crate v2.4.0, in the Cairo 2.4.0 package. For more information, see Cairo v2.4.0 is out! on the Community forum.
  • Improved performance of secp256k1_mul and secp256r1_mul syscalls
  • Computation cost is reduced by approximately 50% as a result of reduced Cairo steps and increased use of builtins. L1 data availability cost is reduced by approximately 10%-25%. For an ERC-20 transfer, the DA fee reduction is 25%.
​
Starknet v0.12.3 (November 19, '23)
Starknet v0.12.3 is live on Mainnet.This release partially removes support for the Starknet feeder gateway. For details, see Feeder Gateway Deprecation in Development Proposals on the Starknet community forum.Additionally, this version includes the following changes:
  • Performance optimizations in the gateway, the computation of the Patricia storage root, and block hash
  • Support for secp256r1 syscalls in the Starknet OS.
  • Restriction for __validate__ and the constructor of DeployAccount transactions: Restrict access to sequencer_address in the get_execution_info syscall by returning 0’s for the address. Restrict access to the following syscalls: Cairo contracts: get_block_hash, Cairo 0 contracts: get_sequencer_address
This version is available on both Goerli and Sepolia testnets.
​
Starknet v0.12.2 (September 04, '23)
Starknet v0.12.2 is live on Mainnet.This version includes the following changes:
  • Enabling P2P Authentication: An additional endpoint in the sequencer gateway to provide a signature on the state diff commitment and block hash.
  • Resolving Mismatches in Queries: An extension to the get_state_update endpoint in the sequencer gateway that returns both the pending state diff and the pending block together.
  • Increased maximum Cairo steps per transaction from 1 million to 3 million.
​
Starknet v0.12.1 (August 21, '23)
Starknet v0.12.1 is live on Mainnet.This version includes the following changes:
  • Mempool Validation.
  • Inclusion of Failed Transactions.
  • Keccak builtin.
​
Starknet v0.12.0 (July 12, '23)
Starknet v0.12.0 is live on Mainnet.This version contains the following changes:
  • Use the rust blockifier and LambdaClass’s Cairo VM to accelerate the sequencer’s time to handle transactions.
  • Support version 2.0.0 of the Cairo compiler.
  • Replace the PENDING status of transactions to ACCEPTED_ON_L2 - once a transaction is in that status it means that it will be included in a block, this applies to transactions - blocks still have the PENDING status.
  • Add an experimental get_block_hash syscall.
  • Change HTTP error code from 500 to 400 on API errors.
​
Starknet v0.11.2 (May 31, '23)
Starknet v0.11.2 is live on Mainnet.This version contains the following changes:
  • Upgrade Cairo 1.0 version to v1.0.0-rc0 (Cairo 1.0 activated on Starknet!)
​
Starknet v0.11.1 (May 23, '23)
Starknet v0.11.1 is live on Mainnet.This version contains the following changes:
  • Upgrade Cairo 1.0 version to v1.0.0-rc0.
  • Charged transaction fee is now based on an average Ethereum gas price instead of a single sample (estimation API is unaffected).
  • API changes: Remove the state root in get_state_update for pending blocks to allow faster responses in future versions.
  • Testing framework: Allow declaring (and interacting with) Cairo 1.0 contracts. Split deploy() to two phases declare and deploy: deprecated_declare() (for Cairo 0 contract) or declare() (for Cairo 1.0 contracts) and deploy() (for both).
  • Add current block hash to the Starknet Core Contract (currently not verified by the Starknet OS): Breaking change: The LogStateUpdate event’s data is changed to include blockHash.
​
Starknet v0.11.0 (March 29, '23)
Starknet v0.11.0 is live on Mainnet.In Starknet v0.11.0, you can declare, deploy and run Cairo 1.0 smart contracts. We also introduce a new system call that allows a smooth transitioning of existing contracts to a Cairo 1.0 implementation.Historically, contract classes have been defined in terms of Cairo assembly, or Casm for short (the class definition also included more information needed for execution, e.g., hint data). The novelty of Cairo 1.0 is the introduction of Sierra (Safe Intermediate Representation), an intermediate layer between Cairo 1.0 and Casm.The introduction of Cairo 1.0 and Sierra has several effects on the system. Below we list the effects on each component; of particular note are:
  • A new version of the declare transaction, which allows sending the new class structure
  • The state commitment will now include contract classes
  • Changes to the onchain data format
  • New system call - replace_class
​
Starknet v0.10.3 (December 12, '22)
The deploy transaction is no longer supported on this version.
This version contains the following changes:Starknet
  • Performance - Separate the state commitment computation from the execution of the transactions
  • Add starknet-class-hash command to compute the class hash of a compiled Starknet contract
Cairo:
  • Autoformatter: Automatically break lines inside expressions
​
Starknet v0.10.2 (November 29, '22)
  • This version introduces sequencer parallelization! This is the first step in our roadmap of performance upgrades. Details about the specific mechanism of parallelization and the roadmap in general are described in this medium post.
  • A new endpoint, estimate_fee_bulk, is added to the feeder gateway. This will allow estimating the fee of several transactions at once, where each transaction is executed relative to the resulting state from applying the previous one.
  • Sequencing performance improvements
  • Builtin ratio changes, which affects builtin costs
  • Add estimate_fee_bulk API that computes the fee of multiple transactions that will be executed consecutively
As part of this version, we will also increase the finality of transactions in the pending block, by fixing the timestamp at the time of the block creation. This will solve the issue of transactions moving from pending to rejected on account of too old timestamp
​
Starknet v0.10.1 (October 25, '22)
This version contains the following changes:Starknet:
  • Add DeployAccount transaction (which will replace the Deploy transaction for deploying account contracts). To use it, you should first add enough funds to your account address to pay the transaction fee, and then you can invoke DeployAccount
  • Split the starknet deploy_account CLI command into starknet new_account and starknet deploy_account
  • Account contracts that are expected to be deployed this way should implement the__validate_deploy__() entry point, which should check the signature of the DeployAccount transaction
  • Improve L1 fee computation: the fee is computed according to the diff of the storage state
  • API: Remove entry_point_type field from transaction information
Cairo:
  • Add uint256_mul_div_mod to uint256.cairo
​
Starknet v0.10.0 (September 05, '22)
This version introduces the next step in Starknet’s account abstraction design, specifically the validate/execute separation. See here for more information.This version contains the following changes:Starknet:
  • Contract (breaking changes): @external and @view functions should be imported directly by the main compiled file. Otherwise, they will not be usable as external functions. Forbid using the same storage variable name in two modules
  • New transaction version (version 1) for invoke and declare transactions: Transactions of version 0 are deprecated and will not be supported in Starknet from the next version (v0.11.0). Please update your systems to use the new version
In order to use transactions of version 1 you will need to upgrade your account contracts
  • Add nonce field to the transactions. Nonce validation is now part of the Starknet protocol and is enforced to be executed sequentially
  • Invoke: Split __execute__ to two functions: __validate__ (only validates the transaction) and __execute__ (only executes the transaction). Remove the selector (which is now always __execute__) field, following the above change.
  • Declare: declare transaction should now be sent from an account (and is validated using __validate_declare__ in the account contract)
  • Support fee for sending L1 messages. At this point, it’s not mandatory and messages with no fee will still be handled. Starting from the next version it will become mandatory.
Cairo: Syntax changes in Cairo (to make it more similar to rust and C++): You can use the cairo-migrate script to convert old code to the new syntax. Use the -i flag to apply the changes to the files. End statements with ;. Use { … } for code blocks (instead of : and end). Add () around the condition of if statements. Remove the member keyword in structs. Change comment to use // instead of #. Use ..., ap++ instead of ...; ap++ in low level Cairo code. Support return types that are not tuples. Return statement accepts expressions, rather than only tuples. Support using functions as expressions. Fix a bug in the secp signature verification code. Add Cairo code for the recursive STARK verifier.Technical changes:
  • Move from python3.7 to python3.9
​
Starknet v0.9.1 (July 20, '22)
This version contains the following changes:Starknet:API changes:
  • Add get_block_traces API - returns all the transaction traces of a given block
  • Add a list of declared contracts in get_state_update
  • Add a 0x prefix for class hash in the API
  • Add starknet_version field for blocks (only applies to new blocks)
Starknet CLI:
  • Change the default block number to pending
  • Using a wallet is the default, --no_wallet must be specified explicitly to override this
  • Deploying contracts: Add deploy_contract function to the account contract created by starknet deploy_account. Use this function to deploy contract (unless using --no_wallet). In particular, deploy should be used after declaring the contract (it expects the contract class hash)
  • Support --dry_run to get the transaction information without signing or sending it
  • Support deploy_from_zero in the deploy syscall to deploy a contract to an address that does not depend on the deployer
Cairo:
  • Support and in if statements (if x == y and z == w).
At the moment other boolean combinations are not supported
​
Starknet v0.9.0 (June 06, '22)
This version introduces the contract class/instance paradigm into Starknet. See here for more information.This version contains the following changes:Starknet:
  • Enforce fees - max_fee must not be set to zero, and selector must be __execute__
  • Split the concepts of contract class and contract instance.
  • Add declare transaction type
  • New API and CLI commands: declare - Declares a contract class. get_class_by_hash - Returns the contract class given its hash. get_class_hash_at - Returns the class hash for a given contract instance address
  • Rename delegate_call to library_call, and change the contract address argument to class hash.
  • Add a deploy system call.
  • Rename ContractDefinition to ContractClass
  • Reduce the compiled contract file’s size by removing unnecessary identifiers (this optimization can be disabled using --dont_filter_identifiers)
Cairo:
  • Initial support for the EC-op builtin (scalar multiplication over the STARK curve). Not supported in Starknet yet.
  • Add additional helper methods to blake2s.cairo, including big-endian support
Technical changes:
  • Change function’s return type from a struct to a named tuple. In particular, foo.Return.SIZE is no longer supported.