Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Missing beacon node <-> validator client API #5

Open
ralexstokes opened this issue Feb 4, 2020 · 1 comment
Open

Missing beacon node <-> validator client API #5

ralexstokes opened this issue Feb 4, 2020 · 1 comment

Comments

@ralexstokes
Copy link
Member

We need to solidify the latest validator API exposed by the beacon node (active discussion here: ethereum/beacon-APIs#12) and implement it in the beacon node. There are stubs API methods/functions in the validator client as of ethereum/trinity#1482.
@ralexstokes
Copy link
Member Author

One important thing to do here is to fetch the Fork data from the beacon node so that the validator client can create the proper BLS domain when making a signature.

@ralexstokes ralexstokes transferred this issue from ethereum/trinity Aug 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ralexstokes