Hello After a healthier conversation over the shared cache implemenation between Validator and Consensus client is dropped. Initially my idea was to prevent the situation that users once faced in lighthouse where they didn't set the same address in both CL and VL which caused the earned rewards to lose. But in the discussion we agreed that by restricting users to set only one place will constraint users to run multiples validators on single beacon node. So the idea was dropped. And `blocks/{slot}` is a huge implementation and requires other endpoints to be implemented before that, I've put it on hold and started working on other endpoints which may or may not set into the validator APIs set and made a [PR](https://github.com/ReamLabs/ream/pull/707) on `pool/attester_slashings/` endpoints. ### Resources As part of that, I have used below resources - [Libp2p - rust implementation](https://www.youtube.com/watch?v=Sss2Tl7WRDQ) - [EPF Study Group Lecture](https://www.youtube.com/watch?v=kYJ7Rj0OGv4) - [Ethereum Gitbook](https://ethereum.github.io/consensus-specs/specs/phase0/p2p-interface/#attester_slashing) ### Next Steps I will be working on this [issue](https://github.com/ReamLabs/ream/issues/556) on Gossipsub message publishing which is `p0` issue on the list.