Kamil Jankowski

The field `contract_class` instead of `class_hash` in RPC Declare Transaction started out as a bug, since in [RPC 0.15.0 specification](https://github.com/starkware-libs/starknet-specs/blob/606c21e06be92ea1543fd0134b7f98df622c2fbf/api/starknet_api_openrpc.json#L1171) DECLARE_TXN has `contract_class` as a key (instead of `class_hash`). However...

Hey there. If you could make a pr I'd appreciate it ;)

A few questions come up: 1. How should cancelling the cheatcodes be implemented? > restore_caller_address? revert / reset / undo / rollback? > with the proposed approach we'd need also...