feat: Add trace_get

[SozinM]

Motivation

Adds the missing trace_get method in #926

Problems

Currently trace_get returns null if queries with multiple indices (params example: "params":["0x346b152d421c095a2eab383d9c5d0309bb28c31e8c5b84fdc6a4f38e2194558d", ["0x0", "0x1"]]) paradigmxyz/reth#3852

Because of this, i choose to use param index with type u64, to remove footgun.

Solution

Usage example. Replace RETH_ENDPOINT with endpoint

use alloy_primitives::{b256};
use alloy_provider::{ext::TraceApi, ProviderBuilder};

#[tokio::main]
async fn main() {
    let url = String::from("RETH_ENDPOINT");
    let node_url = url::Url::parse(url.as_str()).unwrap();
    let provider = ProviderBuilder::new().on_http(node_url);


    let result = provider
        .trace_get(
            b256!("346b152d421c095a2eab383d9c5d0309bb28c31e8c5b84fdc6a4f38e2194558d"),
            1,
        )
        .await
        .unwrap();
    println!("{:#?}", result);
}

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[SozinM]

Open to discussion about whether to use indices: Vec<u64> or index: u64 param.
The first variant is compatible with documentation (which is misleading).
The second variant helps with correct understanding but is confusing as contradict docs.

[DaniPopes]

you can use tuples for lists in JSON since they're equivalent to avoid allocating on the heap, see above in trace_transaction

[mattsse]

this should also use the Index type of rpc-types-eth, because this should ideally be formatted as hex

https://docs.alchemy.com/reference/trace-get

[mattsse]

since this is an index, I wonder if we should use usize here because I assume most of the time this value is derived from doing some vec.len() +- ops

[SozinM]

That's a good point, put usize in there.
I think it would be less convenient to put Index as type because then all calls to trace_get would require a .into() call from the user. It probably would be less convenient.

[mattsse]

lgtm,
doc nit

[SozinM]

@mattsse could you approve workflows, please?