I posted a rough idea of IBC Hub Rollup for Sovereign Rollups on Celestia forum.
To know sovereign rollups, read: ttps://celestia.org/learn/sovereign-rollups/an-introduction/
Sovereign rollups will form inter-cluster / mesh network topology, while conventional smart contract rollups will form intra-cluster / hub & spoke network topology.
To reduce the complexity and number of combinations in the mesh network topology / dense network, I think the IBC Hub Rollup for Sovereign Rollups will be needed.
Rollkit team and IBC go team seems to take time until finishing other tasks in the roadmap. If other teams can contribute to it, the serving time can be reduced and can accelerate the IBC adoption not only in Cosmos SDK / comet BFT chains. However, even if we are interested in contributing to it, topics kind of fund for ecosystem growth are always in stagnation and of course it is difficult to contribute to it fully voluntarily without funding support.
Is it a optimal equilibrium for the IBC ecosystem? Taking long time for serving IBC not only for Cosmos SDK / comet BFT chains will lead to the decline of the presence of IBC ecosystem in the wide crypto ecosystem. Isn’t it better to support funding not only for fixed teams but also for teams who intend to contribute to IBC widely?
I want to discuss how we can contribute to IBC ecosystem in sustainable ways.