Skip to content
This repository has been archived by the owner on Apr 15, 2024. It is now read-only.

chore: add placeholder for mocha bootstrapper #604

Merged
merged 2 commits into from
Nov 20, 2023
Merged

chore: add placeholder for mocha bootstrapper #604

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
34b218b
chore: add placeholder for mocha bootstrapper
jcstein Nov 20, 2023
a5719a2
chore: update domain and node id
jcstein Nov 20, 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
4 changes: 4 additions & 0 deletions docs/orchestrator.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,10 @@ The orchestrator does the following:

The orchestrator connects to a separate P2P network than the consensus or the data availability networks.

The bootstrapper node for the Mocha testnet is:

- `/dns/bootstr-0-mocha-blobstream.celestia-mocha.com/tcp/30000/p2p/12D3KooWLrw6EQgDwvgqrqT8wLNJoQYN3SDAzaAxJgyiTa2xowyF`

Make sure to specify the bootstrapper using the `--p2p.bootstrappers` flag when running the orchestrator or set it in the `<orchestrator_home>/config/config.toml` config file.

This means that even if the consensus node is already connected to the consensus network, if the orchestrator doesn't start with a list of bootstrapper to its specific network, then, it will not work and will output the following logs:
Expand Down
Loading