Abel E
Abel E
Install (from source) docs [specify](https://github.com/eqlabs/pathfinder/blob/main/doc/install-from-source.md#install-rust) 1.64 as the minimum required version, however the [project requires](https://github.com/eqlabs/pathfinder/blob/main/Cargo.toml#L44C1) 1.80.
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...
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.
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...
We're still serving the `0.6` RPC API at the root path `/`. We should default to `0.7`. **Additional notes:** - Currently, to serve `0.7` it must be set on startup...
First take at implementing the consensus P2P layer. This is (are) the first necessary building block(s) for node-to-node communication in our consensus network, _hopefully_ compatible with the Starknet Apollo sequencer...
Under normal operation, finalized heights remain in memory until pruned based on `history_depth`. During recovery, however, finalized heights are skipped and not restored to the internal map. **Problem:** After restart,...
In the validator execution, [we're ignoring certain metadata](https://github.com/eqlabs/pathfinder/pull/3041/files#diff-330c746176682dd9672ab5d48944aac2ae5006e8fc2444a86495464e3dbf754dR408-R410): - class info - paid fee on L1 - deployed contract address This is fine now because: - We're only using `L1Handler`...
We're assuming no classes have been declared as deprecated during execution. We should somehow track which classes were deprecated during the execution of each batch. [ref](https://github.com/eqlabs/pathfinder/pull/3041/files#diff-330c746176682dd9672ab5d48944aac2ae5006e8fc2444a86495464e3dbf754dR350-R352)
Apparently the `JSON extensions` link in [this section of our docs](https://eqlabs.github.io/pathfinder/interacting-with-pathfinder/websocket-api/#pathfinder-websocket-extensions) is broken. Initially reported in [this PR](https://github.com/eqlabs/pathfinder/pull/2827), but the solution doesn't seem in-line with the rest of our docs