feat(l1): add txpool_contentFrom and txpool_inspect to the rpc namespace

[bomanaps]

Motivation

Description

This PR implements txpool_contentFrom and txpool_inspect RPC methods in ethrex, the only two txpool namespace methods missing from the client. The goal is to evaluate full compatibility with ethereum/execution-apis#758, which standardizes the txpool namespace across Ethereum execution clients.

Checklist

• Updated STORE_SCHEMA_VERSION (crates/storage/lib.rs) if the PR includes breaking changes to the Store requiring a re-sync.

Closes #issue_number

[greptile-apps]

Greptile Summary

This PR adds the two remaining txpool namespace RPC methods — txpool_contentFrom and txpool_inspect — following the same patterns already established for txpool_content and txpool_status. Both new handlers correctly note that the codebase has no concept of queued transactions and leave queued empty accordingly.

One minor style nit: the gas-price expression in inspect is functionally equivalent to tx.gas_price() and can be simplified.

Confidence Score: 5/5

Safe to merge; only a redundant expression remains, no correctness issues.

All findings are P2. The single comment points to dead-weight code that produces the same result as a simpler call — not a bug. Both new methods follow established codebase patterns and correctly delegate to mempool.content().

No files require special attention.

Important Files Changed

Filename	Overview
crates/networking/rpc/mempool.rs	Adds content_from and inspect handlers; logic is consistent with existing mempool RPC helpers, one redundant gas_price expression (P2).
crates/networking/rpc/rpc.rs	Routes txpool_contentFrom and txpool_inspect to their new handlers; straightforward two-line addition.

Sequence Diagram

sequenceDiagram
    participant Client
    participant RPC as rpc.rs (map_mempool_requests)
    participant Mempool as mempool.rs
    participant Store as blockchain.mempool

    Client->>RPC: txpool_contentFrom(address)
    RPC->>Mempool: content_from(&params, ctx)
    Mempool->>Store: mempool.content()
    Store-->>Mempool: Vec<Transaction>
    Mempool->>Mempool: filter by sender == address
    Mempool->>Mempool: index by nonce → RpcTransaction
    Mempool-->>RPC: MempoolContentFrom { pending, queued: {} }
    RPC-->>Client: JSON response

    Client->>RPC: txpool_inspect()
    RPC->>Mempool: inspect(ctx)
    Mempool->>Store: mempool.content()
    Store-->>Mempool: Vec<Transaction>
    Mempool->>Mempool: group by sender → nonce → summary string
    Mempool-->>RPC: MempoolInspect { pending, queued: {} }
    RPC-->>Client: JSON response

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: crates/networking/rpc/mempool.rs
Line: 108-111

Comment:
**Redundant gas price computation**

The `max_fee_per_gas().map(U256::from).unwrap_or_else(|| tx.gas_price())` chain produces the exact same result as `tx.gas_price()` alone. `gas_price()` already dispatches: Legacy/EIP-2930 → `tx.gas_price`, EIP-1559/4844/7702 → `U256::from(tx.max_fee_per_gas)`. The elaborate fallback adds no value and implies a distinction that does not exist.

```suggestion
        let gas_price = tx.gas_price();
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "feat(l1): add txpool_contentFrom and txp..." | Re-trigger Greptile}

[greptile-apps]

Redundant gas price computation

The max_fee_per_gas().map(U256::from).unwrap_or_else(|| tx.gas_price()) chain produces the exact same result as tx.gas_price() alone. gas_price() already dispatches: Legacy/EIP-2930 → tx.gas_price, EIP-1559/4844/7702 → U256::from(tx.max_fee_per_gas). The elaborate fallback adds no value and implies a distinction that does not exist.

Suggested change

	let gas_price = tx
	.max_fee_per_gas()
	.map(U256::from)
	.unwrap_or_else(|| tx.gas_price());
	let gas_price = tx.gas_price();

Prompt To Fix With AI

This is a comment left during a code review.
Path: crates/networking/rpc/mempool.rs
Line: 108-111

Comment:
**Redundant gas price computation**

The `max_fee_per_gas().map(U256::from).unwrap_or_else(|| tx.gas_price())` chain produces the exact same result as `tx.gas_price()` alone. `gas_price()` already dispatches: Legacy/EIP-2930 → `tx.gas_price`, EIP-1559/4844/7702 → `U256::from(tx.max_fee_per_gas)`. The elaborate fallback adds no value and implies a distinction that does not exist.

```suggestion
        let gas_price = tx.gas_price();
```

How can I resolve this? If you propose a fix, please make it concise.

[iovoid]

The commits must be signed before the PR can be merged.

I approved the CI workflows and a lint failed.

[ElFantasma]

Clean implementation, I think greptile may have a point on the tx.gas_price() comment, though

[iovoid]

All the commits need to be signed.

[bomanaps]

All the commits need to be signed.

Done please take a look