Added
-
Pathfinder now supports syncing from Starknet 0.14.0. Support is still incomplete, execution and compilation of new classes will likely fail for new classes until a further upgrade.
-
Pathfinder now supports storing only the latest state of the blockchain history. This can be configured with the '--storage.blockchain-history' CLI option.
-
Accepted values are:
- "archive" (default) – Full history of the blockchain is stored.
- "N" – An integer specifying the number of historical blocks to store, in addition to the latest block (N + 1 blocks will be stored).
-
Affected JSON-RPC methods are:
starknet_callstarknet_estimateFeestarknet_estimateMessageFeestarknet_getBlockTransactionCountstarknet_getBlockWithTxHashesstarknet_getBlockWithTxsstarknet_getBlockWithReceiptsstarknet_getClassstarknet_getClassAtstarknet_getClassHashAtstarknet_getEventsstarknet_getNoncestarknet_getStateUpdatestarknet_getStorageAtstarknet_getStorageProofstarknet_getTransactionByBlockIdAndIndexstarknet_simulateTransactionsstarknet_traceBlockTransactions
-
With pruning enabled, affected JSON-RPC method requests will only succeed if the requested block is within the last N + 1 blocks.
-
The choice between
archiveandprunedmode is made once, when creating the database. Once chosen, it cannot be changed without creating a new database. -
It is possible to change the number of blocks stored in pruned mode between runs, using the same CLI option with a different value for N.
-
Note that the number of blocks stored is relative to:
a. The latest L1 checkpoint if it exists and the latest L2 block is ahead of it
b. The latest L2 block if it is behind the latest L1 checkpoint or no L1 checkpoints have been received by the node (practically unreachable)
-
-
starknet_getTransactionStatusnow returns RECEIVED even when the gateway cannot find the transaction, provided the transaction was successfully sent by the responding node within the last 5 minutes.
Fixed
starknet_unsubscribedoes not accept subscription IDs as strings.
Changed
--rpc.get-events-max-uncached-event-filters-to-loadCLI option has been replaced withrpc.get-events-event-filter-block-range-limit. The new option serves the same purpose of preventing queries from taking too long, but it should be clearer in its intent.