**Starknet** * Take fee for reverted transactions. At this phase, the Starknet OS doesn't prove that the transactions failed. This will change once the move to Sierra is complete * Early rejection of transactions that (1) do not pass `validate` (2) have an old nonce or (3) do not pay enough fee * See [here](https://community.starknet.io/t/efficient-utilization-of-sequencer-capacity-in-starknet-v0-12-1/95607) for more information * Support of keccak and Secp256k1 * Fixed a bug where transactions that changed the ETH balance of a user were charged twice for it (once because of reducing the fee and once because of the transaction itself)
0.12.0
**Starknet** * Use the [rust blockifier](https://github.com/starkware-libs/blockifier) and [LambdaClass's Cairo VM](https://github.com/lambdaclass/cairo-vm) to accelerate the sequencer's time to handle transactions * Support version [2.0.0](https://github.com/starkware-libs/cairo/releases/tag/v2.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 (we plan to review how useful this syscall is, so treat it as experimental. We recommend using it *only in upgradable contracts*) * Change HTTP error code from 500 to 400 on API errors
0.12.0a0
**Starknet** * Use the [rust blockifier](https://github.com/starkware-libs/blockifier) and [LambdaClass's Cairo VM](https://github.com/lambdaclass/cairo-vm) to accelerate the sequencer's time to handle transactions * Support version [2.0.0](https://github.com/starkware-libs/cairo/releases/tag/v2.0.0-rc5) 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 (we plan to review how useful this syscall is, so treat it as experimental. We recommend using it *only in upgradable contracts*)
0.11.2
**Starknet**: * Allow the use of Cairo 1.0 on Starknet mainnet * Update Sierra->Casm compiler version to 1.1.0. Note that contracts that were compiled with v1.0.0 cannot be declared in this version. However, if they were already declared, they can still be used, and more instances can be deployed
0.11.2a0
**Starknet**: * Allow the use of Cairo 1.0 on Starknet mainnet * Update Sierra->Casm compiler version to 1.1.0-rc0. Note that contracts that were compiled with v1.0.0 cannot be declared in this version. However, if they were already declared, they can still be used, and more instances can be deployed