v0.3.6
Starknet 0.10.1 support
This release enables support for Starknet 0.10.1. Starknet 0.10.1 introduces a new transaction type: DEPLOY_ACCOUNT. The addition of the new transaction type is a backward incompatible change. We strongly urge you to upgrade before Starknet 0.10.1 is released.
Previous versions of pathfinder will no longer be able to sync on blocks from Starknet version 0.10.1 and onwards.
JSON-RPC API
To keep backward compatibility with existing JSON-RPC clients we have decided to expose multiple versions of the JSON-RPC specification. We're keeping our implementation of the 0.1.0 specification while adding support for the upcoming 0.2.1 release.
The path
of the URL used to access the JSON-RPC server determines which version of the API is served:
- the 0.1.0 API is exposed on the
/
and/rpc/v0.1
paths - the 0.2.1-rc1 API is exposed on the
/rpc/v0.2
path
Support for version 0.2.1-rc1 of the Starknet JSON-RPC API
We have added an implementation for this new release of the specification. This is still a work in progress: we continue working on adding missing functionality. Known deviations from the specification are:
starknet_estimateFee
does not support estimating DEPLOY_ACCOUNT transactions.
JSON-RPC API v0.1.0 changes
DEPLOY_ACCOUNT
transactions
To be able to represent DEPLOY_ACCOUNT
transactions we're deviating from 0.1.0 JSON-RPC specification. We represent the DEPLOY_ACCOUNT
transaction type as the DEPLOY_ACCOUNT_TXN
type as defined in version 0.2.1-rc1 of the specification.
starknet_addInvokeTransaction
can now submit version 1 transactions
Version 1 invoke transactions cannot be submitted without a nonce so we have added an optional nonce
parameter to the method. This is a deviation from the 0.1.0 specification but it's a compatible change. See issue #632 for more details.
More metrics
Pathfinder already provided some metrics to get better insight into the performance of the JSON-RPC interface. This release adds metrics that provide information about the communication with the Starknet gateway. Please check our documentation for more information.
Full Changelog: v0.3.5...v0.3.6