From 92679e4e57b46d4fadd62c96f963ed7cb30f19a3 Mon Sep 17 00:00:00 2001 From: Aderks Date: Sat, 2 Apr 2022 10:10:23 -0600 Subject: [PATCH] Create README.md --- Maple Nodes/README.md | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 Maple Nodes/README.md diff --git a/Maple Nodes/README.md b/Maple Nodes/README.md new file mode 100644 index 00000000..8924cc9b --- /dev/null +++ b/Maple Nodes/README.md @@ -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.