Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: orch update, mark orchestrator as required for validators #1298

Merged
merged 5 commits into from
Nov 29, 2023
Merged

feat: orch update, mark orchestrator as required for validators #1298

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
60c54cf
feat: add note about importance of running orchestrator
jcstein Nov 29, 2023
c691839
feat: update note about blobstream now being required
jcstein Nov 29, 2023
ca42b18
Update nodes/consensus-node.md
jcstein Nov 29, 2023
ae41ac5
Update nodes/consensus-node.md
jcstein Nov 29, 2023
f27e10b
fix: lint
jcstein Nov 29, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions nodes/blobstream-orchestrator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
9 changes: 5 additions & 4 deletions nodes/consensus-node.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 **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.

### Submit your validator information

Expand Down