# EPF6 - Week 4 Updates

## tl;dr

- Got some feedbacks and reviews from mentors.
- Resolved some concerns from mentors.

## Details

> [Link](https://discord.com/channels/476244492043812875/1387734369527136297/1392976074144743474) to the message

In this week, I mostly focused on refining the details of [the project proposal](https://hackmd.io/@junsong/HkQ9XBEHel). Nando and I requested to review our project proposals to the mentors, and received valuable feedbacks from them.

One of the key changes is **deleting `GET` method of the endpoint**. Radek fixed my [misunderstanding](https://discord.com/channels/476244492043812875/1387734369527136297/1392437260233867314): Initially most of the endpoints only had `GET` method, but as the limit of query size becomes problematic, they later added `POST` method for each endpoint. [API for fetching validators information](https://ethereum.github.io/beacon-APIs/#/Beacon/getStateValidators) is one of the example. I thought the feedback is valid and right, since querying arbitrary items (or paths) will easily face the limit of the query parameter and `GET` endpoint. Therefore I decided to deal with only `POST` method for the query.

Also, I [wasn't certain about](https://hackmd.io/m0HFq2CLSXCDMAY1zTfEHA?view#Some-Challenges) the schema of `query` object (which will be included in the request body of `POST` method). Bastin [said](https://discord.com/channels/476244492043812875/1387734369527136297/1392102721263374390) it would be much better to focus on the one query format. I thought a `path`-based approach is easier to implementers and users as well, so **I could make a [schema](https://gist.github.com/syjn99/7be7003f4754ff3d09d5f0b6ce074861) for `query` object.**

## What's next

- Finalize our project proposal.
- Start coding: I guess implementing `path` parser will be the first task.

Now, it's time to execute all those plans and ship it! 🚀