Skip to content

Conversation

@shariqnaiyer
Copy link
Contributor

This is my project proposal for the Ream Validator Client.

My week5 update somehow disappeared from the master branch, it was merged in #226 so I have added that again.

@shariqnaiyer
Copy link
Contributor Author

Hey @taxmeifyoucan, I'm wondering if you've had the chance to take a look at my proposal and have any comments or suggestions on it?

Thank you!

Copy link
Contributor

@taxmeifyoucan taxmeifyoucan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you Shariq! The proposal looks great, the only comments I have are stemming from vague specs part but I understand it's hard since Lean doesn't have proper specs yet


The project can be broken down into the following:

### Core Validator Functionality
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any spec yet or is this just reimplementing Beacon chain validator features? I am missing at least proof verification

Copy link
Contributor Author

@shariqnaiyer shariqnaiyer Aug 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The spec is being drafted as we speak and I have added a link to the repo in the resources.

This PR contains the initial version of the spec. I am actively keeping up with all the calls as well as the relevant repositories and will make a PR to update my proposal as major details are released.

I believe more mature specs for the validator will come after pq-devnet-0 (August 31). I am currently working on components that the validator will eventually use.

As I had earlier implemented BLS signing in the ream-bls crate, I am now working on understanding the hash-sig crate (post quantum hash based signatures) and building the ream post quantum cryptography crate which will include functionality for signing, verification and key generation.

With regards for proof verification, I believe that happens in the Beacon Node so it would be out of scope of the Validator Client. Please correct me if I am mistaken.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, thanks Shariq!

8. Implement propose block logic
9. Implement attestation logic
10. Implement ability to perform voluntary exits and CLI to initiate it

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about studying lighthouse/grandine validators? Seems like they have rust crates for basically everything needed

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did study the Prysm and Lighthouse validators. Those were great resources. I have not checked out grandine yet, I will check that out too. Thank you Mario!

@taxmeifyoucan taxmeifyoucan merged commit f5eb4c6 into eth-protocol-fellows:master Aug 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants