Cosmos Quarterly #1 Q2-26 - Three Pillars, Three Teams

image 1920×768 644 KB Hey folks! This is the first Cosmos Quarterly . Last week we ran a special-edition community call : two hours, built entirely from questions you sent via the forum, Telegram, and DM. We got a lot of them. A sample of what landed in the list: “Why is the roadmap taking 2 years to develop?” “How does ATOM profit from Skip: Go fees?” “Why isn’t the IBC attestation service launched on the Hub as a decentralized neutral notary?” “Which metrics measure active Hub users and ecosystem growth?” Among many others. Reading them all together, something became obvious. Most questions were trying to understand something bigger: how Cosmos Labs actually works now, what our different priorities are, and why. The company changed a lot over the past two years, and more so in the last 4 months. While you’ve seen a lot of the work, you haven’t heard the story of these changes and how our work is structured today. The short of it: the team is bigger, and Cosmos Labs now works in three dedicated pillars: ecosystem, open source, enterprise. Each with its own team. Progress is not single-tracked, but multi-tracked, with independent goals and resources. All updates…

Excerpt (1196 of 30760 characters). Read the whole post on the forum ↗

Excellent summary. Thanks!

Thank you! Love to see this!!

Thanks, folks! We will iterate the format as we learn/hear more.

Summary is really helpful.

I’m absolutely open to continuing the Atom intents work or otherwise building if it’s additive to the mission.

It seems like Cosmos Labs isn’t doing tokenization or enterprise blockchain generically but is instead trying to go to deep on specific verticals which is high risk but potentially builds a moat.

Yes you can continue the Atom Intents and ask CL to support this initiative.

Yeah I think that could play a role in the interop problems we lay out! You are right on the last point, narrower attack zone, but there’s a big ask from the client-side on bringing ready-made use-cases across groups of consumers.

Lets go Zaki ! We believe in your talent to make Atom great again

Thank you for the detailed update. The move to three dedicated teams with a team and budget focused specifically on the Hub is encouraging.

From the perspective of an independent Cosmos SDK chain builder, the forthcoming builder-intake path and community sandbox are especially important. There are already sovereign chains testing real IBC, ATOM, USDC, asset issuance, and application layer use cases that could provide useful integration feedback.

When the intake path opens, will independent Cosmos chains be able to submit technical case studies, interoperability feedback, and live product updates for consideration in the roadmap and Hub Weekly?

I would be interested in contributing practical findings from operating a live Cosmos SDK mainnet connected to the Hub ecosystem.

Hands down. Those findings are welcome, and yes that info is welcome. Today, we have constant calls week by week with chains in the ecosystem to take that input. Reach out in TG (@qxnico), and we can coordinate a first chat as we set up the intake path/sandbox and get ahead of it.