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.

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

link to explorer.cardano.org/relays/topology.json #4545

Merged
merged 1 commit into from
Mar 19, 2023
Merged

link to explorer.cardano.org/relays/topology.json #4545

merged 1 commit into from
Mar 19, 2023

Conversation

CarlosLopezDeLara
Copy link
Contributor

@CarlosLopezDeLara CarlosLopezDeLara commented Oct 20, 2022

Link to https://explorer.cardano.org/relays/topology.json as source for peers.

Closes #4193

@CarlosLopezDeLara CarlosLopezDeLara requested a review from a team as a code owner October 20, 2022 03:30
@@ -19,7 +19,7 @@ Tells your node to which nodes in the network it should talk to. A minimal versi

* `valency` tells the node how many connections your node should have. It only has an effect for dns addresses. If a dns address is given, valency governs to how many resolved ip addresses should we maintain active (hot) connection; for ip addresses, valency is used as a Boolean value, where `0` means to ignore the address.

Your __block-producing__ node must __ONLY__ talk to your __relay nodes__, and the relay node should talk to other relay nodes in the network. Go to our telegram channel to find out IP addresses and ports of peers.
Your __block-producing__ node must __ONLY__ talk to your __relay nodes__, and the relay nodes should talk to other relay nodes in the network. Go to https://explorer.cardano.org/relays/topology.json to find out IP addresses and ports of peers.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The link would not show up new relays immediately afaik, last I checked - @disassembler mentioned it was refreshed twice a week, but that's almost a year ago.
So if mentioning the link and above is true, would be good to put a clause around the update window for new folks (as the guide is predominantly targetting those who might not be familiar with the configs or references).

Copy link
Contributor

@newhoggy newhoggy Mar 19, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to include that the link is updated once a week.

@github-actions
Copy link

github-actions bot commented Dec 5, 2022

This PR is stale because it has been open 45 days with no activity.

@newhoggy newhoggy added this pull request to the merge queue Mar 13, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 13, 2023
@newhoggy newhoggy requested a review from rdlrt March 19, 2023 02:29
@newhoggy newhoggy enabled auto-merge March 19, 2023 02:30
@newhoggy newhoggy added this pull request to the merge queue Mar 19, 2023
@newhoggy newhoggy merged commit 4a8b3d0 into master Mar 19, 2023
@iohk-bors iohk-bors bot deleted the peers branch March 19, 2023 03:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Clarify where to get peers from for the node
3 participants