v0.22.0-beta.3

Release highlights

This is a pre-release version of Pathfinder adding JSON-RPC version 0.10.1-rc.3 support.

⚠️ This release is for testing purposes only. Please do not upgrade your node in a production environment. ⚠️

Fixed

• starknet_traceBlockTransactions parameter trace_flags is not optional (as required by the spec).
• Starknet 0.14.2 blocks are now using the correct versioned constants.

Changed

• The --ethereum.url option now requires a WebSocket URL (ws:// or wss://). HTTP/HTTPS URLs are no longer automatically converted to WebSocket and will result in an error.
• The Pathfinder binary now has two subcommands:
  • node - runs the Pathfinder node as before, serving JSON-RPC and syncing with the network.
    This is the default subcommand and will run if no subcommand is passed.
  • compile - compile a Sierra class (passed via stdin) to CASM (output to stdout).

Added

• Forwarding gateway HTTP error 413 when handling starknet_addDeclareTransaction, starknet_addDeployAccountTransaction and starknet_addInvokeTransaction.
• Two new CLI options for the node subcommand:
  • compiler.max-memory-usage-mib - maximum memory usage for the compiler process, in MiB.
  • compiler.max-cpu-time-secs - maximum (active) CPU time for the compiler process, in seconds.
• Pathfinder is now polling for DNS changes for the feeder gateway and gateway host name. By default the host names are resolved every 60s and the HTTP client connection pool is re-created to force reconnecting to the new address. The interval is configurable with the new --gateway.check-for-dns-updates-interval CLI option.
• starknet_getStorageAt now returns the last update block (in addition to storage value) if the INCLUDE_LAST_UPDATE_BLOCK flag was set in its input.
• starknet_getStateUpdate now supports an address filter.

v0.22.0-beta.2

Release highlights

This is a pre-release version of Pathfinder fixing some JSON-RPC version 0.10.1-rc.2 incompatibilities.

⚠️ This release is for testing purposes only. Please do not upgrade your node in a production environment. ⚠️

Fixed

• JSON-RPC serialization of INITIAL_READS is not compliant with the specification. Pathfinder returns storage_key properties for storage reads instead of the key property required by the spec.
• starknet_addInvokeTransaction is not forwarding proof_facts property to the Starknet gateway.

v0.22.0-beta.1

Release highlights

This is a pre-release version of Pathfinder adding preliminary support for JSON-RPC version 0.10.1-rc.2 and client-side proofs.

⚠️ This release is for testing purposes only. Please do not upgrade your node in a production environment. ⚠️

❗ This release includes a database migration. ❗ The migration step is pretty much instantaneous, but will prevent older Pathfinder releases from starting up with the upgraded database. If you expect to roll back to a previous version, consider backing up your database before upgrading.

Added

• Added support for the "return initial reads" feature introduced in JSON-RPC version 0.10.1:

  • Added RETURN_INITIAL_READS flag to starknet_simulateTransactions input simulation flags.
    Only supported if JSON-RPC version is 0.10.0 or higher.
  • Added a trace_flags field to starknet_traceBlockTransactions input. Currently the only available flag is RETURN_INITIAL_READS.
    Only supported if JSON-RPC version is V10 or higher.

• Preliminary support for JSON-RPC 0.10.1 proof_facts and proof transaction properties.

Changed

• starknet_simulateTransactions now has a different response format based on whether or not the RETURN_INITIAL_READS flag was set in the input:

  1. If the flag was not set, the response is identical to previous RPC versions (an array of transaction simulations).
  2. If the flag was set, the response is an object with two fields:
     • "simulated_transactions" - an array of transaction simulations (previous RPC version output).
     • "initial_reads" - an INITIAL_READS object, containing an aggregate of all initial reads for the simulated transactions.

• starknet_traceBlockTransactions now has a different response format based on whether or not the RETURN_INITIAL_READS flag was set in the input:

  1. If the flag was not set, the response is identical to previous RPC versions (an array of transaction traces).
  2. If the flag was set, the response is an object with two fields:
     • "traces" - an array of transaction traces (previous RPC version output).
     • "initial_reads" - an INITIAL_READS object, containing an aggregate of all initial reads for the traced transactions.

• starknet_getEvents and starknet_subscribeEvents now supports having multiple addresses (represented as an array) in the filter.

v0.21.5

Release highlights

This is a hotfix release that fixes a bug in our HTTP client that has been triggered when gzip compression was enabled on the feeder gateway.

Added

• Support for deflate-compressed responses from the feeder gateway.

Fixed

• Pathfinder stops syncing on networks where response compression has been enabled on the feeder gateway.

v0.21.4

Release highlights

This is a hotfix release with some execution fixes (to fix the exact same issue Starknet mainnet was experiencing) and adding support for gzip-compressed HTTP responses to the feeder gateway client.

Added

• Support for gzip-compressed responses from the feeder gateway.
• The new --rpc.native-execution-force-use-for-incompatible-classes CLI option can be used to force use of native execution even for pre-1.7.0 Sierra classes (where fee calculation is known to be inaccurate). Use this flag at your own risk.

Changed

• blockifier has been upgraded to 0.16.0-rc.3.

v0.21.3

Release highlights

This is a hotfix release with some execution fixes, a new JSON-RPC call metric to measure latencies, and JSON-RPC bug fixes.

Added

• The new histogram metric rpc_method_calls_duration_milliseconds has been added to expose JSON-RPC method call latency data.

Changed

• blockifier has been upgraded to 0.16.0-rc.2.
• Pathfinder no longer returns event_commitment and transaction_commitment values for Starknet blocks older than Starknet version 0.13.2.

Fixed

• starknet_traceTransaction times out for some transactions because fetching transaction traces from the feeder gateway fails due to some unknown fields in the response.

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.