From 60c54cf23368cf2e192468686e10f0c0f7a9eaab Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?joshcs=2Eeth=20=E1=B5=8D=E1=B5=90?= Date: Wed, 29 Nov 2023 08:51:51 -0500 Subject: [PATCH 1/5] feat: add note about importance of running orchestrator --- nodes/blobstream-orchestrator.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/nodes/blobstream-orchestrator.md b/nodes/blobstream-orchestrator.md index ed15cfd134b..2819560f113 100644 --- a/nodes/blobstream-orchestrator.md +++ b/nodes/blobstream-orchestrator.md @@ -10,6 +10,9 @@ description: Learn about the Blobstream Orchestrator. The role of the orchestrator is to sign attestations using its corresponding validator EVM private key. These attestations are generated within the Blobstream module of the Celestia-app state machine. To learn more about what attestations are, you can refer to [the Blobstream overview](https://github.com/celestiaorg/celestia-app/tree/main/x/blobstream). +> **_NOTE:_** +> Running a Blobstream orchestrator is an incredibly important aspect of running a validator. The signatures created there will be used to commit to block data in the exact way as the signatures included in the commit. Not running an orchestrator potentially has the same consequences (enforced by social slashing and eventually the protocol itself) as not signing a block. + ## How it works The orchestrator does the following: From c69183986e3a3e1c85d5c4de3aa6fc72450e2cfb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?joshcs=2Eeth=20=E1=B5=8D=E1=B5=90?= Date: Wed, 29 Nov 2023 09:01:44 -0500 Subject: [PATCH 2/5] feat: update note about blobstream now being required --- nodes/consensus-node.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/nodes/consensus-node.md b/nodes/consensus-node.md index 71820f6d65d..feb7d703fff 100644 --- a/nodes/consensus-node.md +++ b/nodes/consensus-node.md @@ -550,10 +550,11 @@ You should now be able to see your validator from ### Run a Blobstream orchestrator -Soon, Blobstream will be enabled for Mocha, all validators -will need to run a Blobstream orchestrator to be able to sign attestations. -When the time comes, to run it, please -[refer to the documentation](https://docs.celestia.org/nodes/blobstream-orchestrator/#how-to-run). +For validators, running a Blobstream orchestrator is **mandatory** for both +Mocha and Mainnet. Blobstream orchestrator enables validators to sign +attestations. +[Refer to the documentation](https://docs.celestia.org/nodes/blobstream-orchestrator/#how-to-run) +to run an orchestrator. ### Submit your validator information From ca42b18971032ce283368709855ad8d8475dee73 Mon Sep 17 00:00:00 2001 From: Josh Stein <46639943+jcstein@users.noreply.github.com> Date: Wed, 29 Nov 2023 09:07:05 -0500 Subject: [PATCH 3/5] Update nodes/consensus-node.md Co-authored-by: CHAMI Rachid --- nodes/consensus-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nodes/consensus-node.md b/nodes/consensus-node.md index feb7d703fff..4f822652876 100644 --- a/nodes/consensus-node.md +++ b/nodes/consensus-node.md @@ -550,7 +550,7 @@ You should now be able to see your validator from ### Run a Blobstream orchestrator -For validators, running a Blobstream orchestrator is **mandatory** for both +For validators, running a Blobstream orchestrator is **incredibly important** for both Mocha and Mainnet. Blobstream orchestrator enables validators to sign attestations. [Refer to the documentation](https://docs.celestia.org/nodes/blobstream-orchestrator/#how-to-run) From ae41ac5e04d3077e32c61f8e19257eb45e54630c Mon Sep 17 00:00:00 2001 From: Josh Stein <46639943+jcstein@users.noreply.github.com> Date: Wed, 29 Nov 2023 09:07:17 -0500 Subject: [PATCH 4/5] Update nodes/consensus-node.md Co-authored-by: CHAMI Rachid --- nodes/consensus-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nodes/consensus-node.md b/nodes/consensus-node.md index 4f822652876..d6f33fbe753 100644 --- a/nodes/consensus-node.md +++ b/nodes/consensus-node.md @@ -551,7 +551,7 @@ You should now be able to see your validator from ### Run a Blobstream orchestrator For validators, running a Blobstream orchestrator is **incredibly important** for both -Mocha and Mainnet. Blobstream orchestrator enables validators to sign +Mocha and Mainnet (when announced). Blobstream orchestrator enables validators to sign attestations. [Refer to the documentation](https://docs.celestia.org/nodes/blobstream-orchestrator/#how-to-run) to run an orchestrator. From f27e10be3136a104c4c827746301263b4dfc42f3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?joshcs=2Eeth=20=E1=B5=8D=E1=B5=90?= Date: Wed, 29 Nov 2023 09:07:47 -0500 Subject: [PATCH 5/5] fix: lint --- nodes/consensus-node.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/nodes/consensus-node.md b/nodes/consensus-node.md index d6f33fbe753..108f457acd6 100644 --- a/nodes/consensus-node.md +++ b/nodes/consensus-node.md @@ -550,9 +550,9 @@ You should now be able to see your validator from ### Run a Blobstream orchestrator -For validators, running a Blobstream orchestrator is **incredibly important** for both -Mocha and Mainnet (when announced). Blobstream orchestrator enables validators to sign -attestations. +For validators, running a Blobstream orchestrator is **incredibly important** +for both Mocha and Mainnet (when announced). Blobstream orchestrator enables +validators to sign attestations. [Refer to the documentation](https://docs.celestia.org/nodes/blobstream-orchestrator/#how-to-run) to run an orchestrator.