Release v0.10.2 · eqlabs/pathfinder

This release contains various RPC fixes (in particular for the new v0.6), performance improvements.

Added

Added x-request-id header to RPC responses. If the request does not have the header set then an ID is generated. This can be used to identify a specific caller's request/response within the node's logs. Duplicate IDs are possible since they can be set by the caller, so we recommend making your's identifiable with a prefix or using a GUID.
Improved tracing for RPC requests. These are all logged on trace level under the pathfinder_rpc module. Additional information can also be obtained from tower_http module. These can be enabled by appending pathfinder_rpc=trace,tower_http=trace to RUST_LOG environment variable.
- Request payload is now logged before execution begins.
- Logs now include x-request-id header value which can be used to correlate with client requests/responses.
- Batch logs also include the index within a batch.
RPC parsing errors now expose the failure reason as part of the errors data field.

v0.5 starknet_simulateTransactions returns internal error instead of ContractError for reverted transactions.
v0.6 starknet_getTransactionReceipt
- EXECUTION_RESOURCES fields are hex-strings instead of integers
- segment_arena_builtin resource is missing
- v3 transaction price unit type is STRK instead of FRI
v0.6 starknet_estimateFee, starknet_simulateTransactions
- v3 transaction hashes are computed incorrectly when using the "query" flag, causing validation errors
- unit field is missing from fee estimation results
v0.6 starknet_addDeployAccountTransaction
- the gateway doest not properly return address information for v3 transactions, we now compute the address ourselves
starknet_getEvents
- query strategy selection for some events involving a filter on very common keys is slow
Execution performance for calls involving the pending blocks is much better for trivial calls (like balanceOf).