From 9a39cd45158c2079c7ff103a034571d31cf27e7a Mon Sep 17 00:00:00 2001 From: CHAMI Rachid Date: Tue, 4 Jul 2023 11:44:07 +0100 Subject: [PATCH] Update x/qgb/overview.md Co-authored-by: Rootul P --- x/qgb/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x/qgb/overview.md b/x/qgb/overview.md index 4ba7eb9f05..15dd69377a 100644 --- a/x/qgb/overview.md +++ b/x/qgb/overview.md @@ -40,7 +40,7 @@ An [orchestrator](https://github.com/celestiaorg/orchestrator-relayer/blob/main/ At startup, it [loads](https://github.com/celestiaorg/orchestrator-relayer/blob/main/docs/orchestrator.md#evm-key) the EVM private key corresponding to the address used when creating the validator. Then, it uses it to sign the attestations digests before submitting them to the P2P network. -An attestation digest is a bytes array containing a digest of the attestation relevant information. More on this in the [hashes formats](#hashes-format) section. +An attestation digest is a bytes array containing a digest of the attestation relevant information. More on this in the [hashes format](#hashes-format) section. The orchestrator generally needs access to the validator's RPC/gRPC endpoints. However, it still can use public ones if needed. Its only hard requirement is having access to the specific private key for the target validator. Otherwise, the signatures will be invalid and the validator could get slashed in future versions.