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

feat: Inbound / outbound peers & default seeds #541

Merged
merged 9 commits into from
May 5, 2022
Merged

Conversation

faddat
Copy link
Contributor

@faddat faddat commented May 2, 2022

Description

In order to make evmos as easy as possible to set up, and to keep the network from getting choked, I've increased the inbound peers to 240 (this ensures that when new nodes join, there will always be peers for them. Many nodes aren't publicly accessible, hence the 8:1 ratio).

This PR also adds default seeds, which removes a step from setup and provides validators with an opportunity to contribute to network stability and ease of use.


All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

PR review checkboxes:

I have...

  • added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • included the correct type prefix in the PR title
  • targeted the correct branch (see PR Targeting)
  • provided a link in the PR description to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all required CI checks have passed

Code maintenance:

I have...

  • written unit and integration tests
  • added relevant godoc and code comments.
  • updated relevant documentation (docs/) or specification (x/<module>/spec/)

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • confirmed that this PR does not change production code

@faddat faddat changed the title Inbound / outbound peers & default seeds feat: Inbound / outbound peers & default seeds May 2, 2022
Copy link
Contributor

@fedekunze fedekunze left a comment

Choose a reason for hiding this comment

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

Thanks @faddat! Can you run go mod tidy to clean up go.sum?

@fedekunze fedekunze enabled auto-merge (squash) May 3, 2022 06:41
@fedekunze
Copy link
Contributor

@faddat can you fix the conflicts? 🙏

@faddat
Copy link
Contributor Author

faddat commented May 4, 2022

yep, sorry bout the delay :)

auto-merge was automatically disabled May 4, 2022 13:42

Head branch was pushed to by a user without write access

@fedekunze fedekunze enabled auto-merge (squash) May 5, 2022 11:36
@fedekunze fedekunze merged commit c10b74f into evmos:main May 5, 2022
loredanacirstea added a commit to loredanacirstea/evmos that referenced this pull request May 6, 2022
* loredana/ENG-214-add-epoch-types: (40 commits)
  Update evmos v3 -> v4 after latest changes
  Add year and hour epochs
  Update evmos v3 -> v4 after latest changes
  uncomment check
  feat: Inbound / outbound peers & default seeds (evmos#541)
  upgrade: Update Evmos go.mod version `v3` -> `v4` (evmos#557)
  Add change log
  Add migration logic for epoch change
  Fix epochs unit tests
  Revert to ascending order
  Store epoch information by duration and by identifier
  audit(erc20): add types tests and update comments (evmos#550)
  [ENG-219] bump erc20 test coverage (evmos#546)
  audit(erc20): state machine audit (evmos#547)
  audit(erc20): Changes from api audit (evmos#544)
  imp: update default min-gas-prices (evmos#543)
  imp: use constants for epochs IDs (evmos#539)
  fix: upgrade client router key (evmos#537)
  impr(`inflation`): Rename total supply endpoint (evmos#536)
  fix: `buf protoc` was moved to `buf alpha protoc` (evmos#462)
  ...
@fedekunze fedekunze mentioned this pull request May 9, 2022
12 tasks
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.

2 participants