Lessons from Building with Cosmos
summary
Projects choose Cosmos SDK for immediate cross-chain connectivity via IBC relayer and for fast finality; teams migrate from UTXO or bespoke L1s to get out-of-the-box IBC, build appchains, and add EVM/Solana bridges to reach enterprise clients. Pain points: most open-source value does not flow back into ATOM, and foundations undercapture fees. Concrete fixes discussed include deploying GMP/IBC fee rails so hubs earn transaction revenue, foundations doing BD and pilot placements instead of grants only, and focusing on treasury sustainability rather than token sell-offs.
AI-written summary · about
chapters (11)
- 0:00Building on Cosmos
- 1:03Why teams chose Cosmos
- 3:50Interoperability drives Cosmos
- 5:12Challenges on non-EVM chains
- 8:44Cosmos tech vs community
- 11:32Value flow to other ecosystems
- 15:24Capturing ecosystem value
- 18:15ICF financial planning
- 21:08Foundations supporting builders
- 26:03Treasury sustainability strategies
- 28:11Sustainable business models
related talks
12mCØSMOS
25mBig Things to Discuss
32mBuilding on CØSMOS! ALPHA LEAKS!
20mWhat is the Builders Program?
28mCode, Community, & Commerce: The Future of Payments with Solana’s Open-Source Ecosystem
10mInterchain to be flooded with Liquidity
18mNeutron: New Cosmos Project leveraging Interchain Security
39mIt Takes a Village: Why Open Source and Open Development are the Keys to Blockcha...