feature: Complete starknet RPC v0.7.0 [issues#39] #73
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
close #39
Mainly completed the adaptation of itachi to Starknet version 0.7 RPC: https://github.com/starkware-libs/starknet-specs/blob/v0.7.0_rc/starknet_vs_ethereum_node_apis.md
Additional Notes:
1.Added a Pebble DB to store stateUpdate data during block generation. The primary key is blockNum. This is mainly used for the RPC method: getStateUpdate. If a block does not have stateDiff, it will not be stored.
2.Modified the format of blockHash during commit to facilitate the conversion between Felt and Hash in Starknet. This ensures that there is no information loss when converting between Felt and uint256. Without this handling, users would lose 4 bits of information when using Starknet RPC for uint252->256 bit conversion.
3.Added some type codes in the cairo/types.go file required for version 0.7 RPC. The code is sourced from the v0.11.9-3-g4e6dcd72 version of Juno.