From 2a4ca51028c8dea2e27ef867a3eca5a167750341 Mon Sep 17 00:00:00 2001 From: Leo Date: Mon, 7 Dec 2020 09:20:40 +0100 Subject: [PATCH] Clean up operations.md --- docs/operations.md | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/docs/operations.md b/docs/operations.md index 01235a5cb..7e756f6f2 100644 --- a/docs/operations.md +++ b/docs/operations.md @@ -223,17 +223,3 @@ is why it requires extra capabilities. Yes, other chains might want to do this t Storing keys on an HSM or using remote signers only partially mitigates the risk of server compromise - it means the key can't get stolen, but an attacker could still cause the HSM to sign malicious payloads. Future iterations of Wormhole may include support for remote signing using a signer like [SignOS](https://certus.one/sign-os/). - -## High Availability - -Multiple nodes with different node keys can share the same guardian keys. The node which first submits a signature -"wins" and the duplicate signature will be ignored by the network. Wormhole has no need for slashing, and therefore, -there's no risk of equivocation. - -⚠️ _This is not yet tested - see https://github.com/certusone/wormhole/issues/73_ - -## Monitoring - -The node exposes a Prometheus endpoint for monitoring. - -⚠ TODO:️ _Actually build and document this: https://github.com/certusone/wormhole/issues/11_