This release upgrades our internal starknet-vm from 0.9.1 to 0.10. It should now be possible to use starknet_call
and starknet_estimateFee
on the new transaction types
In addition, this release also performs a database migration to remove some extra bogus events that slipped in with the StarkNet 0.10 update on testnet. This migration may take a while to perform, and depends on how many blocks you sync'd during the affected period. The migration will log progress and an ETA.
Changed
- internal starknet-vm upgrade to latest 0.10 version
entry_point_selector
is now an optional parameter forstarknet_estimateFee
in order to allow for the new StarkNet 0.10 invoke transaction type.
Fixed
starknet_estimateFee
does not acceptnonce
parameter- V1 invoke transactions returned
0
fornonce
andversion
fields - Some
starknet_call
andstarknet_estimateFee
queries return internal error involving'compiler_version': ['Unknown field.']
- This was less a bug, and more a result of upgrading our internal-vm
- add a work-around for StarkNet gateway bug where the
nonce
field is missing for historicL1_HANDLER
transactions - blocks with a hash mismatch are accepted
Full Changelog: v0.3.3...v0.3.4