eqlabs/pathfinder v0.4.1

on GitHub

Highlights

• soft deprecation of some configuration options
• support custom StarkNet gateways
• pathfinder RPC extensions at /rpc/pathfinder/ with pathfinder_version method
• starknet_events optimisations
• fix block timestamp in pending calls

Custom StarkNet gateway support

This release introduces support for custom StarkNets. You can select this network by setting --network custom and specifying the --gateway-url and --feeder-gateway-url options.

Configuration option deprecation

Several configuration options have been soft deprecated. This means using them will continue to work as before (no breaking change), but they will emit a warning when used. They will be removed in a future version, so please migrate to the newer options.

To re-emphasize: your current configuration setup will continue to work as is.

Network selection

--testnet2 and --integration have been deprecated in favor of --network testnet2 and --network integration.

Gateway proxy

--sequencer-url has been deprecated in favor of --network custom along with --gateway-url, --feeder-gateway-url and --chain-id. In addition, you will need to rename your existing database file to custom.sqlite as this will be the expected filename for custom networks.

Configuration file

--config has been deprecated and will not be supported in the future. The utility this provided was valuable. Unfortunately it is starting to severely hinder how fast we can implement configuration changes and we decided to remove it.

We suggest using environment variable along with environment files to configure pathfinder in a similar fashion.

Changed

• The following configuration options are now marked as deprecated: --testnet2, --integration, --config, --sequencer-url
• Optimised starknet_events for queries with both a block range and a from address

Fixed

• block timestamps for pending in starknet_call and starknet_estimateFee were using the latest timestamp instead of the pending one. This meant contracts relying on accurate timestamps could sometimes fail unexpectedly.

Added

• custom StarkNet support (see above for details)
• pathfinder specific RPC extensions hosted at <rpc-url>/rpc/pathfinder/v0.1. Currently this only contains pathfinder_version which returns the pathfinder version of the node. The API specification can be found here

Full Changelog: v0.4.0...v0.4.1