Add sierra for predeployed contracts

[franciszekjob]

Closes #3433

Introduced changes

This PR adds sierra of predeployed contracts, allowing to properly display these contracts, when used with debugging features (backtrace and traces).

Backtrace

Before
Shown as forked contract

[FAIL] backtrace_panic::Test::test_predeployed_contract_panics

Failure data:
    0x753235365f737562204f766572666c6f77 ('u256_sub Overflow')

error occurred in forked contract with class hash: 0x4ad3c1dc8413453db314497945b6903e1c766495a1e60492d44da9c2a986e4b

After
Properly displayed

[FAIL] backtrace_panic::Test::test_predeployed_contract_panics

Failure data:
    (0x45524332303a20696e73756666696369656e742062616c616e6365 ('ERC20: insufficient balance'), 0x454e545259504f494e545f4641494c4544 ('ENTRYPOINT_FAILED'))

error occurred in contract 'STRK'
stack backtrace:
   0: core::panic_with_const_felt252
       at /Users/franciszekjob/Library/Caches/com.swmansion.scarb/registry/std/v2.15.0/core/src/lib.cairo:364:5
   1: core::panic_with_const_felt252
       at /Users/franciszekjob/Library/Caches/com.swmansion.scarb/registry/std/v2.15.0/core/src/lib.cairo:364:5
   2: (inlined) core::integer::U128PartialOrd::lt
       at /Users/franciszekjob/Library/Caches/com.swmansion.scarb/registry/std/v2.15.0/core/src/integer.cairo:266:9
   3: (inlined) core::integer::U256PartialOrd::lt
       at /Users/franciszekjob/Library/Caches/com.swmansion.scarb/registry/std/v2.15.0/core/src/integer.cairo:1085:12
   4: openzeppelin_token::erc20::erc20::ERC20Component::InternalImpl::update
       at /Users/franciszekjob/Library/Caches/com.swmansion.scarb/registry/std/v2.15.0/core/src/traits.cairo:663:10
   5: (inlined) openzeppelin_token::erc20::erc20::ERC20Component::InternalImpl::_transfer
       at /Users/franciszekjob/Library/Caches/com.swmansion.scarb/registry/src/scarbs.xyz-9djtpev4jug5q/openzeppelin_token-3.0.0/src/erc20/erc20.cairo:522:13
   6: (inlined) openzeppelin_token::erc20::erc20::ERC20Component::ERC20::transfer
       at /Users/franciszekjob/Library/Caches/com.swmansion.scarb/registry/src/scarbs.xyz-9djtpev4jug5q/openzeppelin_token-3.0.0/src/erc20/erc20.cairo:154:13
   7: (inlined) openzeppelin_token::erc20::erc20::ERC20Component::ERC20Impl::transfer
       at /Users/franciszekjob/Library/Caches/com.swmansion.scarb/registry/src/scarbs.xyz-9djtpev4jug5q/openzeppelin_token-3.0.0/src/erc20/erc20.cairo:118:5
   8: openzeppelin_token::erc20::erc20::ERC20Component::__wrapper__ERC20Impl__transfer
       at /Users/franciszekjob/Library/Caches/com.swmansion.scarb/registry/src/scarbs.xyz-9djtpev4jug5q/openzeppelin_token-3.0.0/src/erc20/erc20.cairo:118:5

Traces

Before
It was not even possible to display trace

Collected 1 test(s) from debugging_predeployed_contract package
Running 1 test(s) from tests/

thread 'tokio-runtime-worker' (28504627) panicked at crates/debugging/src/trace/collect.rs:100:14:
`ABI` should be present
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[ERROR] task 13 panicked with message "`ABI` should be present"

After

Collected 1 test(s) from debugging_predeployed_contract package
Running 0 test(s) from src/
Running 1 test(s) from tests/
[PASS] debugging_predeployed_contract_integrationtest::test_trace::test_decimals (l1_gas: ~0, l1_data_gas: ~0, l2_gas: ~129890)
[test name] debugging_predeployed_contract_integrationtest::test_trace::test_decimals
└─ [selector] decimals
   └─ [contract name] STRK

Tests: 1 passed, 0 failed, 0 ignored, 0 filtered out

Checklist

• Linked relevant issue
• Updated relevant documentation
• Added relevant tests
• Performed self-review of the code
• Added changes to CHANGELOG.md

[franciszekjob]

This change is part of the following stack:

• Update CASM of predeployed contracts #4274
  • Add sierra for predeployed contracts #4275 ◀

_{Change managed by git-spice.}

[franciszekjob]

note: Intentional, because files are already stored as *.json.gz.

[franciszekjob]

https://github.com/foundry-rs/starknet-foundry/actions/runs/25000645750

[DelevoXDG]

Can you provide some context this?

It could be reasonable to add a comment explaining this

[franciszekjob]

This is here so Cargo reruns the build script when the validation logic in build.rs changes, even if the generated artifacts themselves did not. I added a short comment to make that intent explicit.

[DelevoXDG]

Good, makes sense.

I wonder though if we should also track the build script that emits the artifacts.

Since this does not currently catch the case where artifacts may become stale relative to the updated script logic (e.g. swapped ref)

[franciszekjob]

I agree, but the thing is that tracking the generator script here would only rerun this validation, but it still would not detect stale artifacts because the build script currently checks only for file presence. To actually cover cases like a swapped ref, we would need to persist some metadata/stamp from the generation step and validate it here as well.

[DelevoXDG]

Hmmm, should we then perhaps make build.rs actually run the script itself?

[DelevoXDG]

If this is tricky to set up though - it's fine as is, considering we don't envision often bumps

[DelevoXDG]

Good, makes sense.

I wonder though if we should also track the build script that emits the artifacts.

Since this does not currently catch the case where artifacts may become stale relative to the updated script logic (e.g. swapped ref)