v0.16.5

This is a hotfix release fixing multiple JSON-RPC API issues.

Please upgrade if you're running Pathfinder <= 0.16.4.

Fixed

• starknet_estimateFee is failing for Braavos DEPLOY_ACCOUNT transactions involving a new Sierra 1.7.0 class.
• starknet_unsubscribe does not accept subscription IDs as strings.
• starknet_traceBlockTransactions fails for blocks <= 2687.

v0.17.0-beta.1

Added

• Pathfinder now supports syncing from Starknet 0.14.0. Support is still incomplete, execution and compilation of new classes will likely fail for new classes until a further upgrade.

• Pathfinder now supports storing only the latest state of the blockchain history. This can be configured with the '--storage.blockchain-history' CLI option.

  • Accepted values are:

    • "archive" (default) – Full history of the blockchain is stored.
    • "N" – An integer specifying the number of historical blocks to store, in addition to the latest block (N + 1 blocks will be stored).

  • Affected JSON-RPC methods are:

    • starknet_call
    • starknet_estimateFee
    • starknet_estimateMessageFee
    • starknet_getBlockTransactionCount
    • starknet_getBlockWithTxHashes
    • starknet_getBlockWithTxs
    • starknet_getBlockWithReceipts
    • starknet_getClass
    • starknet_getClassAt
    • starknet_getClassHashAt
    • starknet_getEvents
    • starknet_getNonce
    • starknet_getStateUpdate
    • starknet_getStorageAt
    • starknet_getStorageProof
    • starknet_getTransactionByBlockIdAndIndex
    • starknet_simulateTransactions
    • starknet_traceBlockTransactions

  • With pruning enabled, affected JSON-RPC method requests will only succeed if the requested block is within the last N + 1 blocks.

  • The choice between archive and pruned mode is made once, when creating the database. Once chosen, it cannot be changed without creating a new database.

  • It is possible to change the number of blocks stored in pruned mode between runs, using the same CLI option with a different value for N.

  • Note that the number of blocks stored is relative to:
    a. The latest L1 checkpoint if it exists and the latest L2 block is ahead of it
    b. The latest L2 block if it is behind the latest L1 checkpoint or no L1 checkpoints have been received by the node (practically unreachable)

• starknet_getTransactionStatus now returns RECEIVED even when the gateway cannot find the transaction, provided the transaction was successfully sent by the responding node within the last 5 minutes.

Fixed

• starknet_unsubscribe does not accept subscription IDs as strings.

Changed

• --rpc.get-events-max-uncached-event-filters-to-load CLI option has been replaced with rpc.get-events-event-filter-block-range-limit. The new option serves the same purpose of preventing queries from taking too long, but it should be clearer in its intent.

v0.16.4

This is a hotfix release fixing multiple JSON-RPC API issues.

Please upgrade if you're running Pathfinder <= 0.16.3.

Fixed

• starknet_simulateTransactions returns an error instead of the trace of the reverted transaction if the L2 gas cap is insufficient.
• starknet_traceTransaction and starknet_traceBlockTransactions returns an internal error with no details upon encountering a transaction execution error.
• starknet_getEvents returns an incomplete set of events for some queries over a block range larger than 106k blocks.

v0.16.3

This is a hotfix release fixing a migration issue potentially leading to missing events in starknet_getEvents response, and JSON-RPC API issues. We're now supporting version 0.8.1 of the JSON-RPC specification on our v0_8 routes.

⚠️ Please note that the JSON-RPC 0.8.1 specification contains an incompatible change: Websocket subscription_ids are now represented as strings. ⚠️

Please upgrade if you're running Pathfinder <= 0.16.2.

Thanks to @apoorvsadana for his contribution!

Added

• The JSON-RPC 0.8.0 API can now be accessed under /ws/rpc/v0_8 as well if Websockets are enabled. This is equivalent to the /rpc/v0_8 path and is provided only as a convenience feature.

Fixed

• starknet_subscribeEvents subscriptions stop sending notifications.
• Broken aggregate bloom filter migration has been updated to work properly. If you migrated from a database running in archived mode, please re-download our latest snapshot and re-run the migrations.
• starknet_getStateUpdate has new_root and old_root swapped.

Changed

• JSON-RPC 0.8 subscription_id is now a string.
• Pathfinder now supports the JSON-RPC 0.8.1 specification. In this new version, the Websocket subscription_id type has been changed to string.

v0.16.2

This is a hotfix release, adding support for the upcoming Starknet 0.13.5 version plus fixing JSON-RPC API issues and L1 sync problems. Please upgrade if you're running Pathfinder 0.16.0 or 0.16.1.

Thanks to @varun-doshi for his first contribution.

Added

• Support for custom versioned constants for multiple Starknet versions.
• Support for Starknet 0.13.5.

Fixed

• starknet_estimateFee returns an internal error for v3 transactions with L2 gas max_price_per_unit set to zero.
• starknet_getCompiledCasm returns CASM wrapped in a casm property.
• starknet_traceBlockTransactions fails on Starknet 0.13.4 when a fallback to fetching from the feeder gateway is required.
• Websocket subscriptions to the latest block do not send notifications for the current latest block.
• starknet_subscribeEvents subscriptions send matching events only from the latest block, not as soon as those show up in pending.
• Pathfinder stops receiving L1 state updates.

v0.16.1

This is a hotfix release. Please upgrade if you're running Pathfinder 0.16.0.

Fixed

• Pathfinder does not return transaction_hash in starknet_getBlockWithTxns response.
• Custom networks cannot be configured for pre-0.13.4 Starknet versions,

v0.16.0

This is a major release of Pathfinder with significant changes -- the most prominent being adding support for Starknet 0.13.4 and JSON-RPC 0.8.0-rc3.

Our documentation has moved from the README to https://eqlabs.github.io/pathfinder.

⚠️ Upgrading to 0.16.0 from a previous release will perform a database migration that might take a few minutes. Reverting to Pathfinder < 0.16.0 will require a backup of the database before the migration has been completed. ⚠️

Huge thanks to @TropicolX for contributing our new documentation site.

Added

• Support for Starknet 0.13.4.
• Support for the JSON-RPC 0.8.0-rc3 API, including Websocket subscriptions.
• Graceful shutdown upon SIGINT and SIGTERM with a default grace period of 10 seconds, configurable via --shutdown.grace-period.

Removed

• storage_commitment and class_commitment fields from the pathfinder_subscribe_newHeads method response.

Fixed

• pathfinder_getProof, pathfinder_getClassProof return ProofMissing (10001) when Pathfinder is in archive mode and queried block's tries are empty.
• starknet_syncing returns u64::MAX as the starting block number when starting from scratch.

Changed

• Use aggregate Bloom filters for starknet_getEvents to improve performance.

v0.15.3

This is a minor bugfix release. We suggest upgrading if you're running Pathfinder <= 0.15.2.

Changed

• Cairo 0 class definition size is now capped at 4 MiB.

v0.15.2

This is a hotfix release that fixes a serious issue in how Pathfinder 0.15.1 handles L2 reorgs. Please upgrade if you're running Pathfinder 0.15.1. Pathfinder v0.14.x are not affected by the reorg issue.

Fixed

• Pathfinder fails to properly do a reorg due to a SQL statement referring a table that does not exist.
• --rpc.get-events-max-uncached-bloom-filters-to-load setting is ineffective.

v0.15.1

This is a hotfix release. Please upgrade if you're running Pathfinder 0.15.0.

Huge thanks to @xJonathanLEI for fixing the JSON-RPC 0.7 issue introduced in 0.15.0.

Fixed

• starknet_getBlockWithReceipts returns transaction_hash within the transaction object making the response not strictly spec compliant. Fixed on the JSON-RPC 0.8 interface.
• JSON-RPC 0.7 methods returning block headers are including the l2_gas property.

Changed

• Pathfinder is now compiled with arithmetic overflow checks enabled in release mode to mitigate potential issues.