v0.15.0-rc.0

This release brings support for Starknet v0.14.0 and implements the new RPC specification v0.9.0.

⚠️ Important Upgrade Notice ⚠️
Nodes running older versions will stop syncing once the Starknet testnet upgrades to v0.14.0 on July 7th. You must upgrade to stay compatible.

Added

• Support for Starknet v0.14.0
• Implementation of RPC v0.9.0, based on spec v0.9.0-rc.1

Full Changelog: v0.14.7...v0.15.0-rc.0

v0.14.7

This release fixes gas limit handling for simulations and fee estimation, improves Kubernetes readiness integration, and adds Prometheus metric descriptions for compatibility.

Added

• New /live and /ready endpoints for Kubernetes probes:
  • /live: Always returns 200 OK (used in livenessProbe)
  • /ready: Returns 503 if the node is migrating or not yet synced (used in readinessProbe, considers synced if within 6 blocks)
• Added # HELP descriptions to all Prometheus metrics for compatibility with legacy Prometheus libraries

Fixed

• Corrected gas limit behavior for transaction simulations and estimations when SKIP_FEE_CHARGE is set
• --gw-timeouts flag: default value is now 5s (was previously fixed at 5s, which disabled dynamic backoff); it now properly increases after failures

Full Changelog: v0.14.6...v0.14.7

v0.14.6

This release introduces a faster getEvents method via aggregated bloom filter indexing.

⚠️ Breaking Changes ⚠️
This release requires a DB migration. Rolling back to a previous version will not be possible.

Added

• Significant performance boost for getEvents over large block ranges using aggregated bloom filters

Full Changelog: v0.14.5...v0.14.6

v0.14.6-rc.1

This pre-release includes a fix to the getEvents endpoint.

Fixed

• getEvents no longer returns events outside of the requested range. This resolves an issue where additional, unintended events were included in the response.

Full Changelog: v0.14.6-rc.0...v0.14.6-rc.1

v0.14.6-rc.0

This release introduces a faster getEvents method via bloom filter indexing.

⚠️ Breaking Changes ⚠️
This release requires a DB migration. Rolling back to a previous version will not be possible.

Added

• Significant performance boost for getEvents over large block ranges using aggregated bloom filters

Full Changelog: v0.14.5...v0.14.6-rc.0

v0.14.5

This release fixes issues with Braavos account deployment and improves fee estimation compatibility.

Fixed

• Fee estimations for new Braavos DEPLOY_ACCOUNT contracts no longer fail with "out of gas" errors.
• l1_data_gas is now always included in estimateFee responses (RPC 0.8), even when it's 0x0, improving compatibility with the spec.

Full Changelog: v0.14.4...v0.14.5

v0.14.4

This release improves RPC reliability, fee estimation accuracy, and fixes several stability issues.

Changed

• Refined estimateFee logic for better readability and accuracy (#2825)
• Improved error handling for transaction execution, enabling fast-fail on failure (#2760)

Fixed

• Fixed panic in estimateFee when required fields were missing (#2770)
• Corrected handling of nil resource bounds that led to incorrect behavior (#2777)
• Applied a workaround to improve out-of-gas fee estimation accuracy (#2771)
• RPC execution path now respects err_on_revert flag in binary search flow, improving trace consistency (#2766)

Full Changelog: v0.14.3...v0.14.4

v0.14.4-rc1

This release focuses on RPC stability and bug fixes.

Fixed

• Fixed panic in estimateFee RPC when required fields were missing (#2770)
• Corrected handling of nil resource_bounds, which previously led to incorrect struct mappings (#2777)
• Applied temporary workaround for inaccurate out-of-gas fee estimations in RPC (#2771)

Full Changelog: v0.14.4-rc0...v0.14.4-rc1

v0.14.4-rc0

This release includes reliability and performance improvements across the node and RPC layers.

Fixed

• Transaction execution now properly fails fast on error, reducing wasted computation (#2760 by @infrmtcs)
• RPC execution path now respects err_on_revert flag in binary search flow, improving trace consistency (#2766 by @rianhughes)

Full Changelog: v0.14.3...v0.14.4-rc0

v0.14.3

This release focuses on RPC stability, accuracy improvements, and full support for JSON-RPC 0.8.1.

Breaking Changes

⚠️ New Versioned Constants Map

Modified custom versioned constants handling: If you use custom versioned constants, you'll need to update your configuration to match the new structure.

Now, instead of needing to specify a version file directly, specify a .json file which holds each version to override. For example:

{
    "0.13.2": "<path to versioned constant file>",
    "0.13.2.1": "<path to versioned constant file>"
}

The node will use the default versioned constants for unspecified versions.

⚠️ New RPC v0.8.1

Support for JSON-RPC 0.8.1 introduced an incompatible change: WebSocket subscription_ids are now strings instead of integers.

Added

• Flexible Feeder Gateway Timeouts: Introduced a new --gw-timeouts flag to improve resilience when fetching data from the feeder gateway. It allows fine-grained control over timeout behavior in case of retries:
  • Single value (e.g., 5s): Starts with this timeout and increases it with each retry.
  • Comma-separated list (e.g., 5s,10s,20s): Uses each value in order on subsequent retries.
  • Trailing comma (e.g., 5s,): Reuses the same timeout value for every retry without dynamic backoff.
    This makes it easier to tune the node's behavior in high-latency or unstable network conditions.
• Enhanced versioned constants: CUSTOM_VERSIONED_CONSTANTS now stores a map of custom files, fetching from this map first before falling back to blockifier for versions not in the map.
• JSON-RPC 0.8.1 support (spec link)

Fixed

• Event filtering now correctly handles processed events when starting from a pending state
• Storage proof generation properly returns BLOCK_NOT_FOUND in specific edge cases (RPC v0.8.0)
• Empty storage keys in getStorageProof requests no longer cause errors (RPC v0.8.0)
• Improved L1 interaction with more reliable finalized block retrieval
• Fixed a race condition in starknet_getStorageProof where new head blocks ingested during execution could lead to incorrect results
• Corrected pending header setup to prevent inaccurate fee estimates in starknet_estimateFee
• Fixed incorrect gas estimation in starknet_estimateFee when resource_bounds.l2_gas was set (RPC v0.6.0/v0.7.0)

Full Changelog: v0.14.2...v0.14.3