PatStiles

Interested in trying to take this on!

I ran a local testnet with 3 operators produced. The aggregator did not experience any errors and and successfully removed added task information from the aggregator after successfully responding.

https://github.com/pkolaczk/latte

Open telemetry has a rust sdk https://github.com/open-telemetry/opentelemetry-rust. It directly integrates into the tokio's [tracing_suscriber](https://docs.rs/tracing-subscriber/latest/tracing_subscriber/) crate. Here is a tutorial integrating it with jaeger https://tokio.rs/tokio/topics/tracing-next-steps. There is also an example here:...

Referencing: https://github.com/yetanotherco/zkRust/pull/20#issuecomment-2389688246 . Risc0 is currently failing due to a toolchain issue. Specifically installing using `cargo risczero` appears to not install `riscv32-unknown-elf-gcc`. I made an issue in there discord https://discord.com/channels/953703904086994974/1291124782049267825.

Ref: ``` client.","server_address":"localhost:4001"} {"level":"error","ts":1730147025.2860858,"caller":"bls_aggregation/blsagg.go:278","msg":"Task goroutine failed to get operators state from avs registry","taskIndex":0,"err":"Failed to get operator state: Failed to get operators state: Post \"http://localhost:8545/\": read tcp 127.0.0.1:62966->127.0.0.1:8545: read: connection reset...

risc0 says version control for its toolchain is a known issue: https://discord.com/channels/953703904086994974/1290498126049841232 After further investigation we found we can work around issues with installing a past toolchain by having users...

This sucessfully caught panics for the merkle tree verification and sp1 verification but failed when I tested with risc0.

The error we saw is likely due to a corruption of anvil state ref: We should discuss still refactor these tests to be integration tests