Create README.md for dymension_1100-1#404
Open
svv28 wants to merge 19 commits into
Open
Conversation
Contributor
Author
|
Hi! can you give any feedback on this, pls? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I created README.md for mainnet chain. This is just first iteration and information could and should be added: e.g. prebuilt binaries for
amdandarmshould be added in dym releases repo, and links add added here.IMO, the information like this must be in official docs. In long term period, if any need to sync a full node from the scratch will occur (e.g. Kyve' Dymension' data pool creation) exact information of binary versions and upgrade heights will be needed.
besides that I renamed mainnet folder from
dymensiontodymension_1100-1. imo, this should be done sooner or later to avoid the mess in case of chain-id change.in case If this will be merged, I've prepared
chain.jsonupdate in chain-registry:(svv28/chain-registry@cab4af1)