Cairo-lang

**Starknet**:
* Initial support of Cairo1.0 contracts:
* New declare transaction version for declaring Cairo1.0 contracts
* Only a few syscalls are currently supported.
* Changes to on-chain data format. Include the Cairo1.0 declared classes and changes to the class hash of a given contract instance. See more information [here](https://github.com/starkware-libs/cairo-lang/blob/v0.11.0-pre/src/starkware/starknet/core/os/state.cairo)
* Support for Poseidon hash

**Cairo**:
* New builtins:
* Poseidon hash function (efficient, STARK-friendly hash function)
* Keccak hash function (currently, the keccak builtin cannot be used in Starknet)

**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**:
* 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**:
* 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

**StarkNet**:
* 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

**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`