⚠️ v0.4.0 (breaking release) ⚠️
This release contains a breaking change, and also adds support for StarkNet v0.10.2.
The changes themselves are quite simple, but please read through each section as there are some caveats which might impact you when you apply this update.
Default RPC version change
This release changes the version of the RPC that is served at the root route, from v0.1 to v0.2 of the RPC specification. Version v0.1 is still available at the /rpc/v0.1/ endpoint. This is the only breaking change in this release.
Here is a summary of what routes are currently available, and what's changed:
/ <---- serves v0.2 (changed from v0.1)
/rpc/v0.1 <---- serves v0.1 (no change)
/rpc/v0.2 <---- serves v0.2 (no change)
If possible, we recommend that you use the version specific routes as this will prevent such breaking changes from impacting you.
Starknet v0.10.2 support
This release includes an update to the cairo-vm embedded in pathfinder in order to support the upcoming v0.10.2 StarkNet release. This bundled vm is a pre-release and may therefore contain differences to the final version used once StarkNet updates testnet and mainnet. We will of course issue a new release if / when there is a new vm.
⚠️ Please take note of the following ⚠️
Since these changes are not yet live on testnet nor mainnet, this means upgrading to this release will cause deviations between what pathfinder outputs and what can be expected on the network. More specifically, starknet_estimateFee will compute different fees until the network has upgraded to StarkNet v0.10.2.
If you don't need the RPC route changes, it may be pertinent to delay updating until closer to the v0.10.2 release dates on testnet and mainnet. The expected timeline for these upgrades is ~17/11 for testnets and ~24/11 for mainnet.
Full Changelog: v0.3.8...v0.4.0