0.5.2
This release fixes a few RPC bugs and adds support for bulk fee estimation and transaction simulation (traces) as part of v0.3 RPC specification.
In addition it also adds a pathfinder_getTransactionStatus
endpoint which lets you track a transactions status -- including REJECTED
and RECEIVED
-- in the same fashion as the gateway.
Added
- support
starknet_estimateFee
in the JSON-RPC v0.3 API- supports estimating multiple transactions
- this includes declaring and immediately using a class (not currently possible via the gateway)
- support
starknet_simulateTransaction
for JSON-RPC v0.3- supports simulating multiple transactions
- this includes declaring and immediately using a class (not currently possible via the gateway)
- support
pathfinder_getTransactionStatus
which is exposed on all RPC routes- this enables querying a transactions current status, including whether the gateway has received or rejected it
Fixed
- RPC returns int for entrypoint offsets instead of hex
- RPC rejects Fee values with more than 32 digits
- RPC does not expose
pathfinder_getProof
on v0.3 route
Full Changelog: v0.5.1...v0.5.2