RSquad

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