Signed-off-by: Dori Medini <[email protected]>

New cairo-vm version includes performance optimizations.
New cairo version only includes the new vm version.

…4.1-rc.0

Release 0.4.1 rc.0 (starkware-libs#1312)

Co-Authored-By: Gilad Chase <[email protected]>

…e-libs#1249)

This allows one to do:
```
import native_blockifier
native_blockifier.blockifier_version()
```
And get the version the native was compiled with.

Co-Authored-By: Gilad Chase <[email protected]>

…tarkware-libs#1314)

…-main-into-main-contract-segmentation

Merge main into main contract segmentation

Signed-off-by: Dori Medini <[email protected]>

…-to-0.9.1

…de-cairo-vm-to-0.9.1

Dori/upgrade cairo vm to 0.9.1

…-main-v0.13.0-into-main

Elin/merge main v0.13.0 into main

… HEAD (no conflicts).

Signed-off-by: Dori Medini <[email protected]>

…-main-contract-segmentation-into-main

Merge main contract segmentation into main

Signed-off-by: Dori Medini <[email protected]>

…1332)

Signed-off-by: Dori Medini <[email protected]>

The crux of this commit is the change in `block_context.rs`, which
converts `BlockContext` into a wrapper around `BlockInfo` (which used to be
`BlockContext`).

Everything else is just delegating the accessors to the internal block_info, made
by search-and-replace (no other changes).

Motivation:
- This change the groundwork for future refactor and consolidation of
contexts.
- Subsequent commits will extract non block-specific constants from
`BlockInfo` into separate `ChainInfo` and `VersionedConstants` structs,
which will be siblings of `block_info` inside `BlockContext`.

Co-Authored-By: Gilad Chase <[email protected]>

`BlockInfo` should only contain block-level info, whereas chain-level
information should be held at the `BlockContext` level, encapsulated in
a dedicated `ChainInfo` struct.

Changes:
Only extract from `BlockInfo` and store in `BlockContext.chain_info:
ChainInfo`. All other changes are search-replace + moving the
fee_token_address getter into `ChainInfo`.

TODO: extract more stuff from BlockInfo: version-dependant constants should
be extracted into a dedicated VersionedConstants, which will be a member of BlockContext

Co-Authored-By: Gilad Chase <[email protected]>

`PyX` types are intended to represent (a subset) of the real
structure of object in Python.
Currently Python is broken do to PyBlockInfo's FromPyObject expecting
there to be a `PyGasPrices`, which doesn't exist in Ptyhon

Co-Authored-By: Gilad Chase <[email protected]>

`into` implies `owned -> owned` cast, whereas `to` can imply `borrowed
-> owned`.

See this reference for naming convention: https://rust-lang.github.io/api-guidelines/naming.html#ad-hoc-conversions-follow-as_-to_-into_-conventions-c-conv

Co-Authored-By: Gilad Chase <[email protected]>

* add missing internal panic in cairo1

* update `test_stack_trace` and make it work with Cairo1 as well as Cairo0

Signed-off-by: Dori Medini <[email protected]>

Signed-off-by: Dori Medini <[email protected]>

…ibs#1345)

Co-Authored-By: Gilad Chase <[email protected]>

…starkware-libs#1345)" (starkware-libs#1364)

This reverts commit 6b524c9.

Python is fussy about derive_more, will TAL at it again later

Co-Authored-By: Gilad Chase <[email protected]>

…fee test for empty transaction (starkware-libs#1339)

…ains (starkware-libs#1367)

…ltion (starkware-libs#1361)

…gas (starkware-libs#1356)

…as_and_blob_gas_usage (starkware-libs#1357)

…gas_and_blob_gas_usage (starkware-libs#1370)

…actCache new (starkware-libs#1368)

…libs#1374)

Signed-off-by: Dori Medini <[email protected]>

…arkware-libs#1371)

…ibs#1334)

…bs#1378)

Signed-off-by: Dori Medini <[email protected]>

…f as (starkware-libs#1383)

Signed-off-by: Dori Medini <[email protected]>

Signed-off-by: Dori Medini <[email protected]>

…-main-v0.13.1-into-main

Elin/merge main v0.13.1 into main

…e-libs#1347)

…s#1360)

…er(anyhow::Error) (starkware-libs#1397)

…r pre_process_block changes (starkware-libs#1385)

…e-libs#1400)

…counted_gas_from_gas_vector (starkware-libs#1401)

…ap_or(0) to expect) (starkware-libs#1402)

Signed-off-by: Dori Medini <[email protected]>

- Currently only covers the constants previously contained in `BlockInfo`.
TODO: Add check if this covers all chain ids, which might have different
contstants
- Remove `BlockContextArgs`: no longer needed now that BlockContext can
  be initialized by 3 args of public types.

Signed-off-by: Dori Medini <[email protected]>

…e-libs#1403)

…blockifier-config

feat: add VersionedConstants (starkware-libs#1348)

Co-Authored-By: Gilad Chase <[email protected]>

Changes:
1. Implemented get_da_gas_cost, which returns a GasVector (depending on
   use_kzg_da flag).
2. Deleted calculate_tx_gas_usage_vector, because
   calculate_tx_l1_gas_usage does the same thing.
3. Derived derive_more::Add for GasVector to easily sum up gas costs.

Signed-off-by: Dori Medini <[email protected]>

…kware-libs#1409)

Signed-off-by: Dori Medini <[email protected]>

- Rename block_context.rs -> context.rs. This will hold all context
  types.
- Rename block_execution.rs -> block.rs and move `BlockInfo` and
  `GasPrices` there (`GasPrices` is only used inside `BlockInfo`).

No other changes.

…me-modules

refactor: rename context modules (starkware-libs#1350)

Co-Authored-By: Gilad Chase <[email protected]>

* chore(fee): use GasVector as a return type for gas computations

Signed-off-by: Dori Medini <[email protected]>

* chore(fee): integer VM gas usage

Signed-off-by: Dori Medini <[email protected]>

…arkware-libs#1315)

…bs#1362)

- Rename `AccountTransactionContext` into `TransactionInfo`: i want to
  use `Context` for something else, and `Account` is a misnomer, since
  L1Transactions also generate this instance.
- Create a new `AccountTransactionContext`, which holds `BlockContext`
  and `TransactionInfo`: This mirrors `BlockContext`, which holds
  `BlockInfo` as well as higher level contexts.
- Remove all unnecessary `get_account_tx` calls.
- Replace all functions that take both `block_context` and `tx_info` with
a single `TransactionContext`.
- Make `EntryPointExecutionContext` hold an `Arc<TransactionContext>`
  instead of both a block_context and `tx_info`: previously every entry
  point cloned the blockContext and generated a new tx_info, now they
  all share the same (identical) one.

- Add gateway constants, these are only for transparency, and aren't
  used directly by the Blockifier whatsoever.
- Pass `validate_max_n_steps` into the blockifier via native_blockifier,
  to override versioned constants defaults.
- Sort json

The module has already taken out of lib.rs in
`8ba2662f93999b526ef7fd0a7fc49d1314657184` (making this module
dead-code), but the file wasn't actually deleted there.

Co-Authored-By: Gilad Chase <[email protected]>

…unt-tx-info

refactor: make `AccountTransactionContext` hold BlockContext (starkware-libs#1365)

Co-Authored-By: Gilad Chase <[email protected]>

Was already removed from lib.rs.

Co-Authored-By: Gilad Chase <[email protected]>

…constants-to-config

feat: add more constants to`VersionedConstants` (starkware-libs#1369)

Co-Authored-By: Gilad Chase <[email protected]>

Signed-off-by: Dori Medini <[email protected]>

…ate transaction (starkware-libs#1387)

…bs#1394)

1. Currently not using the new consts, just adding
the deserialization logic and tests.
In upcoming commits this will replace the gas costs in `constants.rs`.

The idea is that values inside `cairo_constants` that are json objects,
that is, have the form:
```json
"step_gas_cost": {
  foo_cost: x,
  bar_cost: y,
  ...
}
```
should be parsed as:
```
step_gas_cost = foo_cost*x + bar_cost*y + ...,
```
where {x,y} must be unsigned integers (otherwise an error is thrown),
and where {foo_cost, bar_cost,...} must correspond to keys that
have already* been parsed in the JSON.

Note: JSON standard doesn't enforce order on the keys, but our
implementation does; we should consider using a format that ensures
order, rather than relying on serde's implementation and `IndexMap`.

2. validate the os costs on creation (except for in tests): under
this assumption `get_gas_cost` will _panic_ if given a non-whitelisted
gas cost name.

3. hide the two hashmaps inside `VersionedConstants`, they have
invariants, set accessors accordingly.

…cairo-constants

feat: add Cairo constants to `VersionedConstants` - unused

Signed-off-by: Dori Medini <[email protected]>