This release adds new features to our Websocket API:
- The
pathfinder_subscribemethod can now be used to subscribe to new events and transaction status updates. For more information on the new subscription types please check our OpenRPC API specifications. - Starknet JSON-RPC API methods are now accessible via Websocket connections. To support multiple versions of the JSON-RPC API we've added new, versioned Websocket API endpoints.
We've also implemented further improvements to how we store transaction data in our storage implementation, leading to requiring approximately 80 GiB less disk space for an up-to-date mainnet database.
Running this release will perform a few database migration steps upon first startup, which may take a significant amount of time (up to multiple hours for a mainnet database, depending on the hardware you're running on). Reverting to pathfinder 0.12.0 will require a backup of the database before the migration has been completed.
Fixed
starknet_getBlockWithTxHashesandstarknet_getBlockWithTxsreturns the pending block with astatusproperty that's not in the JSON-RPC specification. This has been fixed for the JSON-RPC 0.7 API endpoint.starknet_traceBlockTransactionsandstarknet_traceTransactionnow falls back to fetching the trace from the feeder gateway for all blocks before Starknet 0.13.1.1.
Added
/ready/syncedendpoint to check if the JSON RPC API is ready and also check if the node is synced. Useful for Docker nodes which only want to be available after syncing.- Websocket endpoints now serve all JSON-RPC methods, not just
pathfinder_subscribeandpathfinder_unsubscribe. Version-specific endpoints have been added for the 0.6 and 0.7 JSON-RPC API and the Pathfinder extension API. - Websocket endpoint for subscribing to events and transaction status changes.
Changed
- Improved compactness of transaction and nonce data, resulting in noticeable storage savings.