💀 Is Cocoon done?

⚫️ According to Resistor, Cocoon’s public network currently has no active workers left — the nodes that provide compute capacity. Without them, the network can’t process requests, which means Cocoon is effectively unusable right now.

⚫️ This could simply be a temporary outage. Still, it’s hard to ignore that there hasn’t been much demand for the technology inside the ecosystem over the past year. According to Dr. Doge’s dashboard, only two nodes were available on the network over the past month, with just 17 registered clients, while compute providers earned less than 600 TON in total.

⚫️ Telegram itself doesn’t seem to be paying much attention to the technology either. The last changes to Cocoon’s open-source code were made more than four months ago, while the project’s official channel hasn’t been updated since last year.

⚫️ There’s another odd detail. Even if the workers come back online, Cocoon’s public client will still be running Qwen3-32B — an outdated model released more than a year ago. Meanwhile, Telegram’s built-in translator, which the company says processes messages through Cocoon’s confidential network, is already running on the newer Qwen3.5.

⚫️ So either Telegram is using a separate version of Cocoon with different code and private infrastructure, or it may no longer be using the public network at all. There’s no way to verify that from the outside, but one thing is clear: the public Cocoon network badly needs updates, more compute providers, and more users.

@thedailyton