docs: document the importance of running orchestrator

[rach-id]

Overview

Checklist

• New and updated code has appropriate documentation
• New and updated code has new and/or updated testing
• Required CI checks are passing
• Visual proof for any user facing features like CLI or documentation updates
• Linked issues closed with keywords

Summary by CodeRabbit

• Documentation
  • Updated installation instructions for Blobstream with the correct version number.
  • Added important notes for validators on the necessity of running a Blobstream orchestrator in both mocha and mainnet environments.
  • Highlighted the consequences of not running an orchestrator, including social slashing and protocol enforcement.

[coderabbitai]

Walkthrough

The recent updates include a minor correction in the README.md file, adjusting the version number for Go installation. More importantly, there are repeated notes added to the orchestrator documentation, stressing the critical role of the Blobstream orchestrator for validators on mocha and mainnet. Validators are reminded of the necessity to run an orchestrator, with warnings of potential consequences, such as social slashing and protocol enforcement, for non-compliance.

Changes

File	Change Summary
README.md	Corrected Go version number in installation instructions.
docs/orchestrator.md	Added notes on the mandatory nature of running a Blobstream orchestrator for validators, with emphasis on the consequences of non-compliance.

🐇✨
To the rhythm of the code, we hop and leap,
With every commit, the network we keep.
Orchestrators must run, validators take heed,
For a healthy chain, this is what we need. 🌐🔒

---

Tips

Chat with CodeRabbit Bot (@coderabbitai)

• If you reply to a review comment from CodeRabbit, the bot will automatically respond.
• To engage with CodeRabbit bot directly around the specific lines of code in the PR, mention @coderabbitai in your review comment
• Note: Review comments are made on code diffs or files, not on the PR overview.
• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Note: For conversation with the bot, please use the review comments on code diffs or files.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

[rach-id]

@jcstein Does it also make sense to add a note in the validator tutorial stating that blobstream orchestrator is mandatory for mocha and mainnet?

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c229e91) 26.09% compared to head (b63db2b) 26.09%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #626   +/-   ##
=======================================
  Coverage   26.09%   26.09%           
=======================================
  Files          29       29           
  Lines        3023     3023           
=======================================
  Hits          789      789           
  Misses       2139     2139           
  Partials       95       95           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[evan-forbes]

can we also update the name of the PR?