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

enabled TIER1 peer discovery in all envs #7759

Merged
merged 4 commits into from Oct 4, 2022

Conversation

pompon0
Copy link
Contributor

@pompon0 pompon0 commented Oct 4, 2022

Validators are already adding their public IPs to the configs (some correctly, some incorrectly) and this PR enables broadcasting this information to the network. It will allow us to monitor whether broadcasting works and check whether validators have correctly configured their public IPs. So far TIER1 peer discovery has been enabled in shardnet (while it still existed) and no regression has been observed.

The TIER1 connections are still not established, the relevant code will be merged in another PR (possibly protected with a separate feature flag, and this flag will be renamed accordingly).

@pompon0 pompon0 requested a review from mm-near October 4, 2022 11:10
@pompon0 pompon0 requested a review from a team as a code owner October 4, 2022 11:10
@near-bulldozer near-bulldozer bot merged commit 43b5930 into master Oct 4, 2022
@near-bulldozer near-bulldozer bot deleted the gprusak-enable-discovery branch October 4, 2022 16:30
nikurt pushed a commit that referenced this pull request Nov 9, 2022
Validators are already adding their public IPs to the configs (some correctly, some incorrectly) and this PR enables broadcasting this information to the network. It will allow us to monitor whether broadcasting works and check whether validators have correctly configured their public IPs. So far TIER1 peer discovery has been enabled in shardnet (while it still existed) and no regression has been observed.

The TIER1 connections are still not established, the relevant code will be merged in another PR (possibly protected with a separate feature flag, and this flag will be renamed accordingly).
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.

None yet

2 participants