---
# System prepended metadata

title: Ognyan’s CDAP Development Update 7

---

# Ognyan’s CDAP Development Update 7

In my last [update](https://hackmd.io/@ogenev/HJHLG7s4K), the following goals were set:

### Previous goals

- Draft Portal Network JSON-RPC specification.
- Implement the JSON-RPC endpoints with highest priority in Trin.

### Portal Network JSON-RPC Endpoints

#### What has been accomplished

- [Initial draft JSON-RPC specs](https://github.com/ethereum/portal-network-specs/pull/88)

  A draft JSON-RPC specs PR was opened in portal network specs repo. As a starting point, the endpoints from [ddht API](https://ddht.readthedocs.io/en/latest/jsonrpc.html) were defined.
  
- [Draft PR for processing base layer discv5 RPCs](https://github.com/ethereum/trin/pull/143)

  When we started with the actual implementation of base discv5 layer RPCs, we found that discv5 implementation in Rust, does not expose raw PING and FINDNODE RPCs in their public API. An issue has been opened and a [quick discussion](https://github.com/sigp/discv5/issues/90) with the library maintainer raised some questions for us: Do we really need most of the base layer discv5 endpoints? What are our use cases? Do we have to standardize those endpoints now, or it is too early, because we still don't know the full profiles of our end-users?

  The next milestone for Portal Network is bringing a test network to live. All necessary tasks to accomplish this are tracked [here](https://github.com/ethereum/trin/issues/118). Part of this milestone is implementing the json-rpc endpoints with highest priority. We decided, that at this stage it will be more wiser if we just implement what we actually need and stick to the [Yagni principle](https://martinfowler.com/bliki/Yagni.html#:~:text=Yagni%20originally%20is%20an%20acronym,'t%20gonna%20need%20it%22.).
At minimum, the plan is to start with the implementation of the overlay PING, FINDNODES and FINDCONTENT round trip RPCs and first focus on our needs as developers.

#### Some minor updates also has been pushed to match Portal Wire Protocol [specs](https://github.com/ethereum/portal-network-specs/blob/master/portal-wire-protocol.md):

- [Custom payload element to PING/PONG message calls](https://github.com/ethereum/trin/pull/132)
- [Protocol identifiers update to match portal network wire specs](https://github.com/ethereum/trin/pull/162)

### What is next

It seems that this is my last CDAP development update but I'm not going anywhere. I'm very happy to be part of the program and I will continue contributing to Ethereum. If you have any questions about the Core Developer Apprenticeship Program, Portal Network or you want to just say "hi", you can find me in [Ethereum R&D Discord](https://discord.gg/SQuPzPwdGJ) (@ogenev). If you are excited about Portal Network as I'm, don't miss to join our [new server](https://discord.gg/7usbyFHB2g).
