From f5f740770f4a55122d47a4dd6b800bb5b0402e64 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ois=C3=ADn=20Kyne?= Date: Thu, 26 Oct 2023 12:37:10 +0400 Subject: [PATCH 1/2] Add third party relays here for the time being --- docs/int/faq/risks.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/int/faq/risks.md b/docs/int/faq/risks.md index e2af412935..b70e347679 100644 --- a/docs/int/faq/risks.md +++ b/docs/int/faq/risks.md @@ -8,7 +8,16 @@ description: Centralization Risks and mitigation ## Risk: Obol hosting the relay infrastructure **Mitigation**: Self-host a relay -One of the risks associated with Obol hosting the [LibP2P relays](docs/charon/networking.md) infrastructure allowing peer discovery is that if Obol-hosted relays go down, peers won't be able to discover each other and perform the DKG. To mitigate this risk, external organizations and node operators can consider self-hosting a relay. This way, if Obol's relays go down, the clusters can still operate through other relays in the network. +One of the risks associated with Obol hosting the [LibP2P relays](docs/charon/networking.md) infrastructure allowing peer discovery is that if Obol-hosted relays go down, peers won't be able to discover each other and perform the DKG. To mitigate this risk, external organizations and node operators can consider self-hosting a relay. This way, if Obol's relays go down, the clusters can still operate through other relays in the network. Ensure that all nodes in the cluster use the same relays, or they will not be able to find each other if they are connected to different relays. + +The following non-Obol entities run relays that you can consider adding to your cluster (you can have more than one per cluster, see the `--p2p-relays` flag of [`charon run`](../../charon/charon-cli-reference.md#the-run-subcommand)): + +| Entity | Relay URL | +|-----------|---------------------------------------| +| [DSRV](https://www.dsrvlabs.com/) | https://charon-relay.dsrvlabs.dev | +| [Infstones](https://infstones.com/) | https://obol-relay.infstones.com:3640/ | +| [Hashquark](https://www.hashquark.io/) | https://relay-2.prod-relay.721.land/ | +| [Figment](https://figment.io/) | https://relay-1.obol.figment.io:3640/ | ## Risk: Obol being able to update Charon code **Mitigation**: Pin specific docker versions or compile from source on a trusted commit From 625d106b0396f1d1b293d8ac40b90d9ef30f6d9b Mon Sep 17 00:00:00 2001 From: Luke Hackett Date: Thu, 26 Oct 2023 02:29:16 -0700 Subject: [PATCH 2/2] Update risks.md --- docs/int/faq/risks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/int/faq/risks.md b/docs/int/faq/risks.md index b70e347679..6931cd253f 100644 --- a/docs/int/faq/risks.md +++ b/docs/int/faq/risks.md @@ -17,7 +17,7 @@ The following non-Obol entities run relays that you can consider adding to your | [DSRV](https://www.dsrvlabs.com/) | https://charon-relay.dsrvlabs.dev | | [Infstones](https://infstones.com/) | https://obol-relay.infstones.com:3640/ | | [Hashquark](https://www.hashquark.io/) | https://relay-2.prod-relay.721.land/ | -| [Figment](https://figment.io/) | https://relay-1.obol.figment.io:3640/ | +| [Figment](https://figment.io/) | https://relay-1.obol.figment.io/ | ## Risk: Obol being able to update Charon code **Mitigation**: Pin specific docker versions or compile from source on a trusted commit @@ -37,4 +37,4 @@ To mitigate the risk of launchpad failure, consider using the `create cluster` o The final centralization risk associated with Obol is the possibility of the company going bankrupt or acting maliciously, which would lead to a loss of control over the network and potentially cause damage to the ecosystem. To mitigate this risk, Obol has implemented a key recovery mechanism. This would allow the clusters to continue operating and to retrieve full private keys even if Obol is no longer able to provide support. -A guide to recombine key shares into a single private key can be accessed [here](../quickstart/advanced/quickstart-combine.md). \ No newline at end of file +A guide to recombine key shares into a single private key can be accessed [here](../quickstart/advanced/quickstart-combine.md).