v0.11.4

This release adds support for the class declaration cost changes introduced in Starknet v0.13.1.1.

If you do not upgrade, you should expect incorrect fee estimations and traces once Starknet v0.13.1.1 releases. Other RPC queries and sync will still work as expected.

Added

• Support for fee changes in Starknet v0.13.1.1.

Fixed

• starknet_estimateFee and starknet_simulateTransactions can return fee estimates below the minimum fee expected by the sequencer for trivial transactions.

v0.11.3

This release fixes a race condition in starknet_estimateFee and starknet_simulateTransactions sometimes using CALLDATA L1 DA mode instead of BLOB.

Fixed

• starknet_estimateFee and starknet_simulateTransactions always uses CALLDATA L1 DA mode if there is no pending block.
• starknet_getTransactionStatus reports gateway errors as TxnNotFound. These are now reported as internal errors.
• starknet_addXXX requests to the gateway use the configured gateway timeout, often causing these to timeout while waiting for
  a gateway response. These instead now use a much longer timeout.

v0.11.2

Important bugfix for starknet_getEvents. No other changes.

Fixed

• starknet_getEvents does not return a continuation token if not all events from the last block fit into the result page.

v0.11.1

Contains a single, important bugfix. You should upgrade asap if you're using v0.11.0.

Fixes

• starknet_estimateFee and starknet_simulateTransaction calls fail when SKIP_VALIDATE is not set.

v0.11.0

This release adds support for Starknet v0.13.1 and RPC v0.7.0-rc2.

The default RPC version has been changed to v0.6. A reminder that this is configurable.

---

⚠️ We will be removing support for RPC v0.4 and v0.5 soon. Please update to RPC v0.6 or v0.7.

---

This release includes a rework of how we store event data on disk, resulting in a 20% smaller database. Note that the database won't release this extra space, so you won't see an immediete saving after upgrading. Rather the database will reuse this extra space over time.

If you need the extra disk space you will need to resync or use one of our snapshots.

---

Changed

• starknet_getEvents implementation is now using a much simpler implementation that no longer relies on SQLite queries. In general this leads to more consistent query times and a roughly 20% smaller database.
• The migration step involves computing Bloom filters for all blocks and dropping database tables no longer needed. This takes more than one hour for a mainnet database.
• The new storage.event-bloom-filter-cache-size, rpc.get-events-max-blocks-to-scan and rpc.get-events-max-bloom-filters-to-load arguments control some aspects of the algorithm.
• The memory allocator used by pathfinder has been changed to jemalloc, leading to improved JSON-RPC performance.
• Improved poseidon hash performance.
• Default RPC version changed to v0.6.

Added

• Support for Starknet v0.13.1.
• Support for RPC v0.7.
• The request timeout for gateway and feeder-gateway queries is now configurable using gateway.request-timeout ("PATHFINDER_GATEWAY_REQUEST_TIMEOUT").

Fixed

• Websocket control frames aren't handled.

v0.11.0-rc0

This pre-release reworks event storage, resulting in a ~25% smaller database. This rework is destructive and one cannot roll-back to a previous pathfinder version. We consider the event storage rework fairly robust and it should give consistent performance for starknet_getEvents queries.

An additional breaking change is the removal of RPC v0.4 support; however at this stage no-one should be using this.

Changed

• starknet_getEvents implementation is now using a much simpler implementation that no longer relies on SQLite queries. In general this leads to more consistent query times and a roughly 20% smaller database.
  • The migration step involves computing Bloom filters for all blocks and dropping database tables no longer needed. This takes more than one hour for a mainnet database.
  • The new storage.event-bloom-filter-cache-size, rpc.get-events-max-blocks-to-scan and rpc.get-events-max-bloom-filters-to-load arguments control some aspects of the algorithm.

Fixed

• UNEXPECTED_ERROR's data format now matches other node implementations

Removed

• Support for RPC v0.4

v0.10.6

⚠️ The previous release (v0.10.5) has been yanked.

---

This release focusses on sync performance improvements. The node should be more consistent about remaining in sync especially when the gateway is performing poorly or under duress.

v0.10.4

Fixes

• starknet_getEvents incorrectly evaluates empty sub-lists in key filters for pending events.
• The RPC error UNEXPECTED_ERROR is an object not a string

v0.10.3

⚠️ Incompatible with starknet v0.12.3 ⚠️

This release is intended for use with starknet v0.13.

This release builds on-top of pathfinder v0.10.3-rc1 so for a full a changelog from v0.10.2 you should also see the release notes from v0.10.3-rc0 and v0.10.3-rc1.

---

Added

• RPC request parsing failures now include the error reason when its an invalid JSON-RPC request (invalid request params already include the error reason).

---

Can I roll this version back?

I upgraded by accident, can I undo? Yes, you can safely rollback to pathfinder v0.10.2.

v0.10.2-apikey

This release adds a new configuration option gateway-api-key to v0.10.2.

The unusual release tag is caused by v0.10.3 still being a release candidate.

Added

• gateway-api-key API_KEY configuration option. If enabled, each time a request is sent to the Starknet gateway or the feeder gateway a X-Throttling-Bypass: API_KEY header will be set.