# Dev Update #5
Hello :wave:,
In my [last update](https://hackmd.io/@lODlsf2CR9uWlyIyEdjjPQ/B1UFETvro), I created a [pull request](https://github.com/ethereum/beacon-APIs/pull/260) for the [`beacon-APIs`](https://github.com/ethereum/beacon-APIs) to fetch data for block proposals and attestations. Since then, I have primarily worked on two things:

1. Created a [**pull request**](https://github.com/ethereum/beacon-APIs/pull/262) with a `sync_committee_rewards` endpoint for the [`beacon-APIs`](https://github.com/ethereum/beacon-APIs).
1. Wrote the [**project proposal**](https://github.com/eth-protocol-fellows/cohort-three/blob/master/projects/consensus_client_reward_APIs.md) for the [consensus client reward APIs](https://github.com/eth-protocol-fellows/cohort-three/blob/master/projects/project-ideas.md#consensus-client-reward-apis).

In the following, I will discuss these two tasks in detail.

## [`Sync committee endpoint`](https://github.com/ethereum/beacon-APIs/pull/262)

The endpoint for sync committee rewards looks like the following:

`/eth/v1/beacon/blocks/{block_id}/sync_committee_rewards`

*Get sync committee rewards*

{
    "data": [
        {
            "validator_index": "0",
            "reward": "-1000",
        },
        {
            "validator_index": "1",
            "reward": "1000",
        },
    ]
}

This is the third, and thus our last, proposed endpoint for the [`beacon-APIs`](https://github.com/ethereum/beacon-APIs). Our next milestones are introduced in the next section.

## [Project proposal](https://github.com/eth-protocol-fellows/cohort-three/blob/master/projects/consensus_client_reward_APIs.md)
The [project proposal](https://github.com/eth-protocol-fellows/cohort-three/blob/master/projects/consensus_client_reward_APIs.md) included a [timeline](https://github.com/eth-protocol-fellows/cohort-three/blob/master/projects/consensus_client_reward_APIs.md#roadmap) I want to focus on in *this* development update. With this timeline, we have a rough estimate to showcase what the coming weeks might look like.


The project can be divided into two sections, [`beacon-APIs`](https://github.com/ethereum/beacon-APIs), and consensus clients. Both sections consist of the same items, familiarizing with the codebase and implementing attestation, block, and sync committee rewards. However, the consensus client items take up more time because of their complexity.

Currently, we are waiting on feedback for our pull requests while simultaneously familiarizing ourselves with the codebase of consensus clients. Once the PRs ([#260](https://github.com/ethereum/beacon-APIs/pull/260) and [#262](https://github.com/ethereum/beacon-APIs/pull/262)) are merged, we move on to the consensus clients. The estimates are somewhat optimistic, and we are well on time.

## After the project?
I started the [EPF](https://github.com/eth-protocol-fellows/cohort-three/blob/master/program-guide/program-details.md) by creating a [dashboard](https://kevinbogner-data-analysis-consensus-clients-app-lz484x.streamlit.app/) that displays data on consensus clients. I realized there needs to be more reward data, leading to this project.

So, once the APIs are implemented in one consensus client, I want to use them to fetch data for my [dashboard](https://kevinbogner-data-analysis-consensus-clients-app-lz484x.streamlit.app/). I plan to take about 1 or 2 additional weeks to finish my dashboard at the end of the [EPF](https://github.com/eth-protocol-fellows/cohort-three/blob/master/program-guide/program-details.md).

## Next steps
Once the PRs ([#260](https://github.com/ethereum/beacon-APIs/pull/260) and [#262](https://github.com/ethereum/beacon-APIs/pull/262)) are merged, we can pat ourselves on the back. It feels like being part of something bigger and doing meaningful work with a purpose.

However, I know that the next weeks could become challenging, yet I'm looking forward to it :blush: Bye :wave: