pathfinder
pathfinder copied to clipboard
eqlabs
A Starknet full node written in Rust
Currently, in our code we call the `get_transaction` endpoint and then only extract the status data from it. To avoid confusion and improve our bandwith, we should be using the...
The semantics of the method are not quite clear, so based on a Slack discussion to clarify the specification here's some extra information: - Any combination of `class_hashes`, `contract_addresses` and...
The `starknet_subscribeTransactionStatus` websocket endpoint accepts a transaction hash (`pathfinder_common::TransactionHash`) and a `block` (`pathfinder_common::BlockId`) to start streaming updates from. It returns a stream of transaction status updates for the given transaction...
Introduces functionality to sync L1 to L2 message logs, improving our ability to track cross-chain interactions. ### Key Changes 1. Added `get_logs` method to the Ethereum client: - Allows fetching...
We should throw the new error over JSON-RPC 0.8.0 _and keep the old one for previous versions_. The message for the error should be the following: `The transaction's resources don't...
After processing all L1 logs and L2 transactions, we find that there's no matching L1 handler Tx (on L2) for some L1->L2 messages we've seen in the Ethereum logs.
TL;DR We should be fine with `test_log` only. ----- We're currently using: `test_log` and/or ``` let _ = env_logger::builder().is_test(true).try_init(); ``` ( :arrow_up: which is redundant with `test_log`) or ``` let...
Using `BlockNumber` struct for L1 blocks as well as L2 blocks can cause confusion. Given it’s just a wrapper around `u64`, It wouldn’t hurt to have an `L1BlockNumber` as well...
Looks like we're keeping a read transaction (in `ExpectedDeclarations::spawn()`) open for the whole duration of the class definitions sync. This causes SQLite to be unable to merge WAL records back...