This release contains various RPC fixes (in particular for the new v0.6), performance improvements.
Added
- Added
x-request-idheader 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
tracelevel under thepathfinder_rpcmodule. Additional information can also be obtained fromtower_httpmodule. These can be enabled by appendingpathfinder_rpc=trace,tower_http=tracetoRUST_LOGenvironment variable.- Request payload is now logged before execution begins.
- Logs now include
x-request-idheader 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
datafield.
Fixed
- v0.5
starknet_simulateTransactionsreturns internal error instead ofContractErrorfor reverted transactions. - v0.6
starknet_getTransactionReceiptEXECUTION_RESOURCESfields are hex-strings instead of integerssegment_arena_builtinresource is missing- v3 transaction price unit type is
STRKinstead ofFRI
- v0.6
starknet_estimateFee,starknet_simulateTransactions- v3 transaction hashes are computed incorrectly when using the "query" flag, causing validation errors
unitfield 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
pendingblocks is much better for trivial calls (likebalanceOf).
Changed
- JSON-RPC v0.6 now serves
0.6.0forstarknet_specVersion.