Submitted to the Cosmos Hub Governance on 2021-09-07 16:45 UTC
Voting Started on 2021-09-07 16:45 UTC
Voting ends on 2021-09-21 16:45 UTC
The Hub has long been envisioned as a central point in the IBC architecture. In the battle to build and ship IBC this central vision has remained unchanged, but with so much focus on the need to build out other zones with real economies to support this network (the CosmosSDK is the result of this effort), the idea of the hub as an Interchain Router hasn’t been discussed in a serious context for quite a while.
This is understandable: Cosmos needed so many other pieces to come together before the Hub had a chance to even start performing this function. Those other zones have been created, they each have products and economies. The bootstrapping era of IBC is well underway.
These new zones joining are noticing a problem: they need to maintain a large amount of infrastructure (archive nodes and relayers for each counterparty chain) to connect with all the chains in the ecosystem, a number that is continuing to increase quickly.
Luckly this problem has been anticipated and IBC architected to accomodate multi-hop transactions. However, a packet forwarding/routing feature was not in the initial IBC release. This proposal aims to fix this for the Hub.
This is a proposal to include a new feature to IBC on the Hub that allows for multi-hop packet routing for ICS20 transfers. By appending an intermediate address, and the port/channel identifiers for the final destination, clients will be able to outline more than one transfer at a time.
Strangelove Ventures has delivered an [IBC Middleware module](https: //github.com/cosmos/ibc-go/pull/373) that will allow the hub to play the role of IBC Router that was always envisioned for it. Passing of this propsal will begin the era of the Hub offering interchain services to other chains and profiting from those relationships.
To pay the hub validators and stakers, this proposal implements a governance configurable fee (which we propose should be initially set to 0.0 to encourage adoption) that will be taken out of each packet and given to the community pool. The community pool will then periodically trade these fees for ATOM and distribute them to staked holders. The exact distribution method of these fees is left TBD in this proposal as it is not initially required and can be implemented in a future governance proposal. One way to do this would be using the [Groups module](https: //docs.cosmos.network/master/architecture/adr-042-group-module.html), Community spend proposals and the Gravity DEX.
A vote YES on this proposal indicates that this feature should be included in the next hub upgrade. We (as the Hub) believe that time is critical right now and we cannot wait to begin providing this service to other chains. A NO vote indicates that this shouldn’t be included in the next upgrade.
[Full Proposal text and additional links available here](governance/README.md at master · strangelove-ventures/governance · GitHub
This proposal went onto the hub before being posted on the forum which is not typical for the lifecycle of a proposal. The forum has been the go to place for public discussion of proposals so that ATOM holders can make informed decisions in governance. In private telegrams and discords the topic has been debated thoroughly by various Cosmos core contributors. It has a number of varied opinions that should be more visible to the public discourse.
I encourage active and civil discourse here, we all want the same thing: a successful Cosmos Hub. Pasting external conversations that have been confirmed OK to reproduce by those involved is also encouraged.