v0.21.2

Release Highlights

This is a hotfix release adding support for the final JSON-RPC 0.10.0 specification.

Changed

• Pathfinder now serves the JSON-RPC 0.10.0 API on the v0_10 routes.
• The size of the block trace cache is now configurable by the new --rpc.block-trace-cache-size CLI argument.

v0.21.1

Release Highlights

This is a hotfix release fixing some issues that have been reported to us. In particular, it fixes trace generation for blocks with DECLARE transactions on Starknet 0.14.1 blocks.

Fixed

• Pathfinder exits after receiving an internal server error from the feeder gateway.
• starknet_estimateFee and starknet_simulateTransactions fails if one of the transactions is using a class that has been declared by a simulated DECLARE transaction in the batch.
• Cairo Native is not working correctly with Docker images published on Docker Hub due to a linker error.

v0.21.0

Release Highlights

This release fixes some pre-confirmed block inconsistencies and adds support for the upcoming Starknet 0.14.1 version (including JSON-RPC 0.10.0-rc.1 support).

⚠️ Please note that this release involves a database migration step. Please make sure that you create a backup of your database before upgrading because otherwise rolling back to the previous release won't be possible.

Added

• Support for Starknet 0.14.1 networks.
• Support for JSON-RPC 0.10.0-rc.1.

Fixed

• Inconsistent state updates when using "pre_confirmed" block identifier with starknet_call, starknet_estimateFee and starknet_simulateTransactions JSON-RPC methods.

v0.20.5

Release Highlights

This is a hotfix release fixing some issues that have been reported to us.

Fixed

• starknet_estimateFee fails if the validate entry point runs ouf of gas during L2 fee binary search.
• Pathfinder stops syncing for a minute after logging an "L2 sync process terminated with: Download block from sequencer" error.
• starknet_simulateTransactions sometimes fails for DEPLOY_ACCOUNT transactions if the SKIP_FEE_CHARGE simulation flag is not set. This happens even though the account address has the sufficient funds to execute the transaction.

v0.20.4

Fixed

• Pathfinder panics with "Block number Z is not in the range X..=Y" after starting up from an old Sepolia testnet database snapshot.
• Pathfinder returns internal errors for some starknet_getTransactionStatus / starknet_getTransactionReceipt queries for transactions in the pre-confirmed block.
• L2 sync stalls for a while after logging an "L2 sync process terminated with: Fetch signature for BlockNumber(XXX) from sequencer" error.

v0.20.3

Release Highlights

This is a small feature release adding polling of pre-latest data. The aim here is to reduce transaction latency as observed via the JSON-RPC API via implementing a more elaborate pre-latest/pre-confirmed data polling method that avoids some pitfalls of our previous implementation.

Changed

• Polling of pre-confirmed data has been improved to reduce end-to-end latency. Pathfinder now polls both the pre-latest and pre-confirmed data from the feeder gateway.

v0.20.2

Release Highlights

This is a hotfix release fixing multiple issues after the Starknet 0.14.0 upgrade on Starknet Mainnet. Please upgrade urgently to avoid stability issues.

Added

• reorg notifications for starknet_subscribeNewTransactions and starknet_subscribeNewTransactionReceipts

Changed

• blockifier has been upgraded to version 0.15.0-rc.4.

Fixed

• starknet_subscribeNewTransactions doesn't accept the RECEIVED finality status filter.
• Pathfinder gets stuck in a loop and prints "State root mismatch" errors after starting up from a database with current state that has been re-orged.
• starknet_traceTransaction and starknet_traceBlockTransactions falls back to fetching transaction traces for Starknet mainnet block range 1943704-1952704 (inclusive). Local re-execution would lead to a different result due to a sequencer issue that was present when these blocks were produced.
• Pathfinder gets stuck syncing and stops responding to JSON-RPC requests.

v0.20.1

Release Highlights

• Fix for not being able to perform the recent L2 reorg on Starknet mainnet. ⚠️ Please upgrade immediately if you are experiencing issues with catching up with the tip of the chain on Starknet mainnet. ⚠️

Added

• --rpc.disable-batch-requests CLI option, for instances not wishing to support batch requests.

Fixed

• Pathfinder cannot recover after a reorg involving more than 1000 blocks. L2 reorg fails with error "Reorg exceeded local blockchain cache".

v0.20.0

Release Highlights

• Fix for getEvents query no longer returning correct result after Sepolia reorg. Includes DB migration that will repair any database instances affected by the bug.
• ⚠️ Breaking: starknet_getClassAt now returns DEPRECATED_CAIRO_ENTRY_POINT.offset as a hex string instead of an integer. This change aligns the response format with the specification, which expects NUM_AS_HEX for this field.

Changed

• blockifier has been upgraded to version 0.15.0-rc.3.

Fixed

• JSON-RPC response reflects an inconsistent state after receiving a notification over a Websocket subscription.
• starknet_getClassAt now returns DEPRECATED_CAIRO_ENTRY_POINT.offset as a hex string instead of an integer. This change aligns the response format with the specification, which expects NUM_AS_HEX for this field.

v0.19.0

Release Highlights

• Support for the final JSON-RPC 0.9.0 API.
• Fix for transaction status and transaction nonce inconsistencies in typical user workflows.
• ⚠️ Breaking: The default version of the JSON-RPC API served on the / path has changed to 0.8.0.

Changed

• Pathfinder now implements the final JSON-RPC 0.9.0 specification.
• blockifier has been upgraded to version 0.15.0-rc.2.
• The default JSON-RPC listen address has been changed to the IPv6 wildcard address in our Docker images. This avoids problems on IPv6-enabled hosts where localhost resolves to ::1.
• The default JSON-RPC version (served on the '/' route) has been changed to v08.
• JSON-RPC starknet_estimateFee and starknet_simulateTransactions now use non-strict nonce checking when using the SKIP_VALIDATE flag. That is, the nonce value needs to be larger than the last used value but no exact match is required.
• starknet_getTransactionStatus now returns ACCEPTED_* only when that status is known locally, not when it's received from the gateway for an otherwise-unknown transaction.
• Value of the --sync.poll-interval command-line option can now specify fractional seconds

Fixed

• starknet_getEvents returns an incomplete result set if the block range includes empty blocks.