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

Node setup multidimensional #216

Merged
merged 52 commits into from
Nov 16, 2022
Merged

Node setup multidimensional #216

merged 52 commits into from
Nov 16, 2022

Conversation

alebanzas
Copy link
Contributor

What

  • includes support for partial views
  • JWT generation
  • setup nethermind (by network, by OS)
  • setup lighthouse (by network, by OS)
  • keys generation
  • validator setup with lighthouse

Refs

PM-related:

@alebanzas alebanzas merged commit 09769d3 into 127-validators Nov 16, 2022
@plato-gno
Copy link
Contributor

@alebanzas - Can I recommend we call this page the "Interactive Guide"? In my mind, this will be the long-term link that we send out to people.

I am also recommending the following docs tree structure: the Interactive Guide partials will then link to more detailed pages with FAQs, that we can add over time.

I think we should design our validator docs tree for "extensibility": there are almost unlimited different problems validators can face, and we should have a place in our docs tree to "hang" more knowledge over time.

I think the winning strategy is an interactive guide that most people can stick to. If they encounter issues for a single process, they can then be linked to a more detailed sub-page that goes into excruciating detail, and validator relations can add FAQs as they encounter them.

image

cc @CVJoint @jbradach

@alebanzas
Copy link
Contributor Author

Sure, great proposal! Will change it in #159 cause I am working there on the integration of this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

5 participants