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