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.

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

Add Beacon Node proxy for Proof of Stake #107

Open
mohamedmansour opened this issue Feb 21, 2022 · 0 comments
Open

Add Beacon Node proxy for Proof of Stake #107

mohamedmansour opened this issue Feb 21, 2022 · 0 comments

Comments

@mohamedmansour
Copy link
Owner

mohamedmansour commented Feb 21, 2022

Right now we listen on each node from the execution client for Proof of Work to get the metadata, and we do some stats to get the data you see today. Since Proof of Stake will come soon, we need to get ready and listen on the beacon node to get the data as well. We need a plan to implement that.

Perhaps the tasks would be broken up by:

  • Create a few Docker images that host an PoS Executor Node, and Beacon Node, on Kitsugi testnet. We need this to upgrade to more beefier system.
  • Implement a Golang client that connects to either Prysm Beacon or Lighthouse Beacon.
  • Create interface wrappers around the current PoW and PoS to gather similar metrics.
  • Update the stats.go and hub.go to use the new wrappers.
  • Update the React frontend to allow us to switch to testnet (we had previous code that does that)
  • Bring back the old countdown for testnet!
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

No branches or pull requests

1 participant