Top spot in contest. Again.

What’s next?

💎 What happens when punks build websites?

This: https://www.rsquad.io/

“It is a system that mints tgBTC on TON executing every step by smart contracts and decentralized algorithms.”
— from the stage at The Gateway

We told the story. This is what happens when devs hold the mic.

“Why not wait for someone else to do it?”

Because we didn’t feel like being bored to death.
Because Hyperlane on TON just makes sense.

Five months of silence.

We were busy breaking things
that weren’t supposed to break.

Validators were aware.
The chain survived.

There’s a sign on the site.
If you know, you know.
If not — read-only now.

TON Rust Node is here. Chaos unleashed.

Blocks screaming, systems bending, unstoppable power?

Breaking ground on the TON network
after the TON Rust Node launch, like never before.

Follow the signal: https://tonrust.io

🎬 Tech Updates EP2 | Roman Nguyen

Yesterday we announced TON Rust Node. Today, meet the team behind it.

Roman Nguyen, CTO of RSquad Blockchain Lab, explains what they built and why it matters for anyone running TON infrastructure.

👉 Watch the full episode

💬 What would you like to see from TON in 2027? Share below.

Gateway|TON Community | TON Builders | TON Hubs |X | YouTube | LinkedIn TON.org

We stayed quiet for a long time. We were building the product, supporting operators, and genuinely counting on fair competition and joint work — which, by the way, was actually happening. Teams were finding bugs in each other's implementations, sharing observations, surfacing more and more nuances of how the protocol actually behaves. That's what healthy collaboration for the good of the ecosystem looks like.

We deliberately kept out of the public eye both the circumstances under which the decision to build this node was made, and who made it. We figured the product would speak for itself.

But since public claims about the status of the Rust implementation are now on the table — let's talk facts.

Status of TON Rust Node.

The node has moved out of the experimental stage and is in rollout. The first Rust validators went live on mainnet more than 3 months ago and have been running stably ever since. Today on mainnet there are several validators, dozens of full node / liteserver instances, and archive nodes. It's run by our team, by independent operators, and by infrastructure teams. The current migration request stands at around a hundred validator nodes.

The nodes sync stably, participate in consensus, maintain the current state of the network, and create no problems for block propagation or compatibility.

Code, documentation, tooling — all open: https://github.com/RSquad/ton-rust-node

Coverage: consensus (catchain & simplex), validator, full node, liteserver, archive, TVM/executor, and the full QUIC/ADNL/RLDP/Overlay/DHT stack. Infrastructure layer: Docker, Kubernetes/Helm, nodectl for cluster management, election & staking automation, Prometheus/Grafana, HashiCorp Vault for key management without storing keys on disk. Load testing — 36 nodes across three geographies, 2000+ TPS sustained.

Yes, we occasionally run into issues. Yes, there were problems — it would be silly to pretend otherwise. But it would be equally silly to pretend that 90% of the time these issues trace back to breaking protocol changes pushed unilaterally, without coordination with teams maintaining alternative implementations. That's a process question, not an implementation quality question.

Now to the substance.

The argument in the original statement boils down to this: the priority is MTONGA, therefore alternative implementations are "not on the agenda." But MTONGA is Make TON Great Again. Open again. Great again.

Pavel Durov himself, announcing the next step, put it plainly: the focus shifts to technological superiority.

Here's the thing: technological superiority in a blockchain isn't one reference implementation controlled by one group. That's the opposite of technological superiority. That's a monoculture. One bug in the only implementation, and the whole network halts. No amount of testing, reviews, or internal discipline closes that gap — because the blind spots inside a single team are shared blind spots.

Ethereum and Bitcoin — the two networks with the largest market caps in the entire industry — have operated with multiple independent clients for years, for exactly this reason. It's the only known way to build genuine resilience. This isn't ideology. It's engineering.

Saying "we don't need alternative implementations because we're focused on the technology" is a contradiction in a single sentence.

On ideals.

TON was conceived as open, decentralized, free infrastructure. Telegram — as a space for freedom of thought, action, and speech. Either those values exist or they don't.

You don't make TON open and great again through closed development of an open-source product, zero community support, unilateral breaking changes, and public attacks on alternatives instead of debate on the merits. That's the exact opposite direction from what was originally built into TON, and from what Telegram itself proclaims.

We're for free competition. For openness. For collaboration. For facts. Our goal is to make the solution better, not to prove someone else's is worse.

Finally.

We know and we see the support from everyone using this node — and trust us, there are more of you than it might look from the outside. To everyone who took a chance on this node, ran it in production, reported issues, or just shared honest feedback — thank you. This product is what it is because of you.

We keep building. More is coming: technical deep-dives, the reasoning behind architectural decisions, migration case studies. And, in time, the backstory — what we've seen, what we've worked around, and why this node had to be built at all. We've held a lot of it back so far. But since we're working in public now, there's no real reason not to start sharing the facts. Stay tuned.

We're just getting started.

On-chain is final, off-chain is noise,
Real engineers don't play with custodial toys.

If infra can initiate transfers, it’s a target.
Everything else is just a notification layer.

Ground truth: https://rsquad.io/feed/non-custodial-by-design-multisig-mpc-and-signless-authorization

The boring portfolios fade away,
Three crowns from CSSDA today.

Best UI Design. Best UX Design. Best Innovation.
People's Choice — a public coronation.
Jury Special Kudos on the foundation.

Then FWA stepped up to second the motion:
81 points. 7 days. Same forward motion.
Fourth crown in. No need for promotion.

Punks at the gate. Punks on the throne.

The proof's on the wall:
▪️ CSSDA
▪️ FWA