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

Commit

Permalink
fix: than -> from
Browse files Browse the repository at this point in the history
  • Loading branch information
jcstein committed Nov 20, 2023
1 parent 751b8ea commit a944a58
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/orchestrator.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The orchestrator does the following:
4. Then, the orchestrator pushes its signature to the P2P network it is connected to, via adding it as a DHT value.
5. Listen for new attestations and go back to step 2.

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

The bootstrapper node for the Mocha testnet is:

Expand Down
2 changes: 1 addition & 1 deletion docs/relayer.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ The relayer works as follows:
5. Once the relayer finds more than 2/3s signatures, it submits them to the target Blobstream smart contract where they get validated.
6. Listen for new attestations and go back to step 2.

The relayer connects to a separate P2P network than the consensus or the data availability one. So, we will provide bootstrappers for that one.
The relayer connects to a separate P2P network from the consensus or the data availability one. So, we will provide bootstrappers for that one.

This means that even if the consensus node is already connected to the consensus network, if the relayer 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

0 comments on commit a944a58

Please sign in to comment.