-
Notifications
You must be signed in to change notification settings - Fork 607
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
download genesis automatically with ipfs #1489
Comments
why isn't get.osmosis.zone the goal we target here? |
...where get.osmosis.zone gives you a .dmg ;) Most people have a pretty deep cli allergy, but osmosis can run just about anywhere. I have been thinking about this one, I actually think that it should happen during init instead of after. I'm going make a PR, but please don't feel any obligation to merge it if you don't feel like it move things forward or if you feel like it adds to many modules. It will likely and a lot of modules, this is something that I do not like about IPFS. Basically, I would really like features like this all across cosmos. |
Unfortunately, this is blocked by this: We could mess around with replace statements, but I think it is best to delay this change. |
Background
We can't make enough RPC nodes. It is impossible. Plus, we want to make "the signal" unstoppable. This means that eventually, Osmosis and its related DAOs need to ship onto user machines, as desktop apps.
Currently those of us on the "technical side" of the house have all shared the experience of guiding someone through hunting down genesis and seeds.
In fact, many of us have spent days of our lives doing the same. This is counter-productive and bad.
Suggested Design
Osmosis should download its own genesis state by default, and state sync by default, using addresses from the cosmos chain registry. Here's the code:
Acceptance Criteria
osmosisd init
should no longer be necessary except for validators and others doing "fancy things" with their nodesThe text was updated successfully, but these errors were encountered: