Is Cosmos Missing a Better Support Culture?

Conversation
1

Over the years, one pattern keeps coming back across the Cosmos ecosystem.

Builders, validators and contributors often say they struggled to get support.

We’ve all heard comments like:

  • “Nobody replied.”
  • “We were ghosted.”
  • “We couldn’t find the right person.”
  • “We never received any follow-up.”

In some cases, this may reflect a genuine lack of support. Teams are busy, priorities change, and not every request can be handled.

But I also think there is another side to the story.

Many requests happen entirely in private: DMs, Telegram chats, Discord messages, introductions between friends, etc. Because they’re invisible, nobody else in the ecosystem knows that someone is looking for help.

This means that people who could have answered or contributed never even get the opportunity.

So I wonder if the problem isn’t actually twofold.

From the requester’s side

  • Ask for help more publicly instead of relying only on private conversations.
  • Make requests visible so anyone in the ecosystem can contribute.
  • Build a searchable knowledge base for future builders facing similar issues.

From the support side

I also believe ecosystem teams could become more mature in how support is handled.

Not every request deserves a “yes,” but almost every request deserves an answer.

Even a simple:

  • “We’re not the right team.”
  • “This isn’t on our roadmap.”
  • “Try contacting X.”
  • “We can’t help with this.”

…is far better than silence.

Public responses are valuable because they benefit everyone, not just the original requester. Future builders can discover the discussion instead of asking the same questions again.

Ultimately, support is not only about solving problems.

It’s also about communication, transparency, and making people feel that their request was actually heard.

I’m curious whether others have experienced the same thing.

Do you think Cosmos should encourage more public support channels, a stronger culture of visible requests, public replies and more dedicated people to this tasks ?

2 Likes
2

I think this is an important point, and I would frame it less as a “support problem” and more as a coordination layer problem.

In a large distributed ecosystem like Cosmos, support is not only about who has the answer. It is also about how a request moves through the ecosystem until it reaches the right context.

A request usually has a lifecycle:

  1. Intake: where the request is made.

  2. Triage: what type of request it is.

  3. Routing: who is the right team, working group, validator, relayer, repository, or governance venue.

  4. Ownership: who can give an answer or at least confirm scope.

  5. Closure: what was decided, even if the answer is “no,” “not now,” or “wrong place.”

When this lifecycle happens only in private DMs, the ecosystem loses visibility. The requester may feel ignored, while the people capable of helping may never even see the request. Also, the answer does not become reusable knowledge.

So I agree that public support channels matter, but I think the deeper need is a lightweight public routing system.

Not a centralized help desk. That would not fit Cosmos.

More like a shared coordination pattern:

  • clear categories for requests;

  • public places where builders and validators know where to ask;

  • visible triage from the community;

  • simple acknowledgment from the relevant side;

  • public closure, even when there is no solution;

  • searchable history for future contributors.

This would reduce repeated questions, reduce silent dead ends, and make support more scalable without requiring every team to answer everything.

Validators could also be part of this routing layer. They are often close to users, infrastructure issues, governance discussions, and ecosystem operations. They may not always be the final authority, but they can help identify where a request belongs.

For me, the goal is not to make every request receive a positive answer.

The goal is to make the path of the request visible.

In decentralized ecosystems, support should not depend only on private access to the right person. It should become part of the public coordination infrastructure.

2 Likes
3

Good to have guys like you around, a little bit quirky but always committed to the mission.
I guess general scepsis is appropriate in a space that is flooded with malicious actors ( aka scammers). I thought blockchain was designed to minimize trust between two parties, but in practice it seems every possible way to cheat each other is being used to gain every available $$ using intransparency in onchain mechanism to fool those with lesser knowledge…

As long as the general mindset won’t shift towards a more “grown up” way to interact with each other, this blockchain will remain a toy, not becoming a tool

Blockchain was originally designed to abolish leadership structures (yeah gov proposal etc… you know) but it seems this doesn’t apply for the current situation.

I got accused being a scammer a hundreds of times, as soon as the name Juno came into play- Yeah, Interchain incubator, the place to go… .. stupidly we favored Juno over Solana in 2022, which turned out a, ahem lets say pretty naive decision retroactively.

Nevertheless i count the cw VM superior even to anchor, but its sad to hear stupid claims that there are no cosmwasm devs around so we need to switch to EVM.
Thats the hen-egg problem: The root cause is not a lack of developers that would like to get a more intuitive VM to work with, the problem is that due to certain weaknesses in the Tokenization model 95% of all launched chains (aka Tokens) are doomed to be sold into oblivion from “network rewards”. Rewards to “secure” the network lead inevitably to the destined death of those chains. Of course a lot of actors got rich that way, and many many more investors got bleeded out.
Thats the recipe to kill a SDK unfortunately, once your reputation is gone, there is no recover for it.
Don’t take it personal, i don’t take anything serious anymore in the space anymore too.

Check guys like the guinch that take probably more initiative than most of those 10k$ paycheck receivers.
Thanks mate for stepping up the scene, same goes out to kwosh and some others

1 Like
4

I don’t take it personally. I understand the skepticism, especially after what happened across several Cosmos chains. Bad incentives, poor token models and loss of trust are real problems.

My point is not that public coordination fixes everything. It does not fix broken tokenomics or bad actors.

But when support, routing and accountability happen only in private, the ecosystem becomes even less transparent. So even in a damaged environment, making requests and answers more visible is still a step toward maturity.

1 Like