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

[DOCS] Add guidelines on managing bootnodes for OP Stack Chain Operators #346

Open
sbvegan opened this issue Dec 20, 2023 · 0 comments
Open
Labels
community-request docs updates requested by community or OP collective developer-support-feedback This is feedback from devsup. These docs suggestions stem from solving developer pain. documentation Improvements or additions to documentation

Comments

@sbvegan
Copy link
Collaborator

sbvegan commented Dec 20, 2023

Brief Description of the Docs Request

Add guidelines on managing bootnodes for OP Stack chain operators

Description of the Documentation You'd Like

  • Information about peer scoring
  • How to use the admin rpc or static peering to make sure internal nodes don't accidentally kick them out

Links to Related Pages

Additional Context

  • This is part of a larger initiative to get open source run books and guidelines on chain operation. Might be worth holding off on this addition until we have a plan for building out the Chain Operator section.
  • I've gotten this question from a chain operator
@sbvegan sbvegan added documentation Improvements or additions to documentation community-request docs updates requested by community or OP collective developer-support-feedback This is feedback from devsup. These docs suggestions stem from solving developer pain. labels Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-request docs updates requested by community or OP collective developer-support-feedback This is feedback from devsup. These docs suggestions stem from solving developer pain. documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants