eqlabs/pathfinder v0.18.0

on GitHub

Release Highlights

• JSON-RPC 0.9.0 API bugfixes
• Support for querying the L1 accepted state directly via the Pathfinder JSON-RPC API:
  • The Pathfinder-specific pathfinder_lastL1AcceptedBlockHashAndNumber method can be used to query the block number and hash of the latest L1 accepted block known by the node.
  • The l1_accepted block tag introduced in the JSON-RPC 0.9.0-rc.2 specification can now be used in all JSON-RPC methods that have a block_id parameter.

⚠️ Please note that this release includes a smallish DB migration, that makes it impossible to roll back to Pathfinder 0.17.0 after the upgrade to Pathfinder 0.18.0. Please make sure you create a backup of your Pathfinder database before upgrading. ⚠️

Added

• pathfinder_lastL1AcceptedBlockHashAndNumber, a pathfinder extension analogous to starknet_blockHashAndNumber
• Pathfinder now accepts the l1_accepted BLOCK_TAG on the JSON-RPC interface. This can be used to reference the latest L1 accepted block known by the node.

Fixed

• The default value of L2 gas price for historical blocks has been changed from 0 to 1 (for both WEI and FRI), to agree with the feeder gateway default.
• Trying to enable blockchain pruning on an archive database does indeed enable pruning in the database despite printing an error that pruning cannot be enabled.
• When running on Starknet < 0.14.0 and querying for the "pre_confirmed" block header Pathfinder returns a non-conformant response that has "parent_hash" instead of "block_number".
• Transaction execution errors and contract errors are returning unstructured error information on the JSON-RPC 0.9.0 API.