Support full history of cosmos hub

[okwme]

Summary

Each hard fork upgrade of the cosmos hub creates a new blockchain. In order to make queries about the previous versions, nodes need to be kept online, even though they're no longer producing blocks. I'd like ICF to keep RPC and REST endpoints online for each historical version of the Cosmos Hub.

Problem Definition

Proposal

For cosmoshub-1, cosmoshub-2 and cosmoshub-3 there is a specific binary that is used to run the node. It needs to be configured to have a halt-height so that it doesn't fail trying to produce new blocks after the constituent upgrade heights were reached. That should allow the nodes to stay online and queryable.

For cosmoshub-4 there were soft fork upgrades that mean different binaries are necessary to be run after different heights. The history of cosmos hub upgrades can be seen in the roadmap home dir. For each of the soft forks of cosmoshub-4 to be accessible, each of the binaries should be able to be run on the same node, targeting the same home directory for data. They will need to be configured to use different ports of course. Then with a proper mapping of URLs to port IDs we can provide endpoints for queries that are correlated to different block heights. For instance the URLs could looks like this with a reference to which infra node is needed to support them:

# server-1
rpc-cosmoshub-1.interchain.io
rest-cosmoshub-1.interchain.io

# server-2
rpc-cosmoshub-2.interchain.io
rest-cosmoshub-2.interchain.io

# server-3
rpc-cosmoshub-3.interchain.io
rest-cosmoshub-3.interchain.io

# server-4
rpc-cosmoshub-4-1.interchain.io
rest-cosmoshub-4-1.interchain.io
rpc-cosmoshub-4-2.interchain.io
rest-cosmoshub-4-2.interchain.io
rpc-cosmoshub-4-3.interchain.io
rest-cosmoshub-4-3.interchain.io
rpc-cosmoshub-4-4.interchain.io
rest-cosmoshub-4-4.interchain.io

More fine grained details about which version of gaia to use and which range of block heights to query for can be seen in the history of cosmos hub upgrades above.

---

For Admin Use

• [ ] Not duplicate issue
• [ ] Appropriate labels applied
• [ ] Appropriate contributors tagged
• [ ] Contributor assigned/self-assigned

[okwme]

There's additional archival data and information available at https://archive.interchain.io/

[glnro]

• Setup meeting with Hypha to review Ansible script

[glnro]

@okwme What do we want the architecture for sentry nodes to look like...one to many or one to one? Have been discussing w @tokamak-git, wanted to wait before moving forward.

Also, do we want multiple sentries for different regions?

[tokamak-git]

archive 4 endpoints configured for internal use. e.g. as a seed node for state sync. refer gaiad status --node https://rpc-cosmoshub-4-4.interchain.io

[tokamak-git]

@glnro how would you like to proceed?

[glnro]

Taking a look at this tonight to close out

[mmulji-ic]

@tokamak-git discussed with @glnro, we can close this.

[okwme]

Re-open as a long term issue to track "nice-to-have" features for the full history of gaia.

These include

• backporting tests
• performance improvements
• unified queries
  • use one query format then route and reconfigure to the correct format depending on height

[mpoke]

@mmulji-ic what's the latest status of this issue?

[mpoke]

Closing this issue as it's currently not in the of the work done on this repo. We'll reopen in the future if there is interest.