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

Maple Nodes Pledge #93

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions Maple Nodes/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
# Agoric Validator Pledge
[Maple Nodes Explorer Link](https://main.explorer.agoric.net/validator/agoricvaloper1nttcw852wga4y4gww3hu70djg9d4fu4cw4as8a)
We, Maple Nodes, hereby commit to the following work and support for the benefit of the Agoric Network and Community. If, for any reason, we do not meet these commitments then we understand that we may lose delegation staked to us.

1. The hardware our node will run meets the requirements detailed in the [Agoric Validator Runbooks](https://github.com/Agoric/agoric-sdk/wiki/Runbooks)

2. Our node will have an uptime of at least 95%

3. We will set a reasonable commission rate between 3% to 10%

4. We commit to not exceed 10% voting power

5. We will actively participate in security and upgrade governance proposals found on [Commonwealth.im](https://commonwealth.im/agoric)

6. We will report bugs I discover through the process described in the [Agoric Reporting a Security Bug Runbook](https://github.com/Agoric/agoric-sdk/wiki/Runbook%3A-Reporting-a-Security-Bug)

7. We will follow the guidelines described in the [Agoric Security Coordination - Emergency Bug Response with Chain Validators Runbook](https://github.com/Agoric/agoric-sdk/wiki/Runbook%3A-Security-Coordination---Emergency-Bug-Response-with-Chain-Validators) to maintain the health of the chain

8. We will notify impacted parties in case of node outage.

9. We will strive to capture and share observability metrics to help diagnose and troubleshoot network and node performance issues

10. We commit to network contributions listed below:

Category 1: Infrastructure

* We will build a validator dashboard with corresponding public APIs.

Category 2: Community Growth

* We will contribute to the development of security best practices by creating and sharing technical documentation that includes writing incident response runbooks, configuration guides, or information for a validator wiki.