# EPF Week1 Update

> What I'm going to do in this EPF

I have chosen the JSONRPC section(proposed by @s1na), specifically the implementation of the `trace_` RPC in GETH. More details in https://github.com/eth-protocol-fellows/cohort-five/blob/main/projects/project-ideas.md#json-rpc-in-geth

> updates

During this week, I have started diving into the project tasks and gathering all the necessary information. The first task on my list is the implementation of the `trace_` RPC for GETH. To accomplish this, I have been learning about the following:

1. `trace_` RPC in OpenEthereum: https://openethereum.github.io/JSONRPC-trace-module
2. trace_block/trace_filter in erigon's implementaion: https://github.com/ledgerwatch/erigon/blob/b4c9f22923cd7156cd26be91a8a83b131eb3cc73/turbo/jsonrpc/trace_filtering.go#L163, https://github.com/ledgerwatch/erigon/blob/b4c9f22923cd7156cd26be91a8a83b131eb3cc73/turbo/jsonrpc/trace_filtering.go#L286
3. trace_block/trace_filter in reth's implementation: https://github.com/paradigmxyz/reth/blob/bc15e6c03a9e678d1a2320b4f550537011e42835/crates/rpc/rpc/src/trace.rs#L342, https://github.com/paradigmxyz/reth/blob/bc15e6c03a9e678d1a2320b4f550537011e42835/crates/rpc/rpc/src/trace.rs#L237
4. live tracing: https://github.com/ethereum/go-ethereum/blob/master/core/tracing/hooks.go
5. tracing persistence: https://github.com/ethereum/go-ethereum/issues/28643

While studying Reth's code, I discovered a bug in the calculation of uncle rewards within the trace_block function. I addressed this issue by submitting a pull request, which was successfully merged. You can find the details of the fix in this pull request: [Bug fix for incorrect uncle reward calculation](https://github.com/paradigmxyz/reth/pull/8767)

> plans in the next week

I plan to summarize the current implementation of trace_ in both Erigon and Reth. Based on this analysis, I will create a design document proposal for GETH’s trace_ implementation. The document will primarily focus on the RPC design. Additionally, I will schedule a meeting with @s1na and @gary to discuss the project’s details in-depth.