Why different staking protocols in TON show different APY?

After the sub-second update, validator rewards increased ~6x. Previously, different calculation models could show values like 4.19% and 4.28%, while after the update they show ~25.44% and ~22.83% depending on the formula and reward accounting mechanics. Let’s briefly break down where these numbers come from and why they differ.

In TON, staking works in cycles: rewards are distributed only during the active validation phase ~18 hours, while the full cycle including election and holding takes around ~36 hours. Because of this, a single validator participates in roughly half of all rounds per year ~240 out of ~481 — this is critical for APY calculation.

APY (annual percentage yield) accounts for compound interest: rewards are automatically added to the stake and start earning in subsequent validation rounds. In the formula below, which is currently used, compounding accumulates only over ~240 rounds in which the staked amount is actually active.

APY = ((1 + reward_per_round) ^ (rounds_per_year / 2)) - 1
APY = ((1.00085507) ^ 240) - 1
APY ≈ 22.83%

When you stake TON in liquid staking, half of the stake works in even rounds and half in odd rounds, so rewards are received roughly every ~18 hours. If you combine them, it results in a full reward over ~36 hours.

Read more about how staking works in TON

Hi, we’ve got a small dev inbox experiment here

We’re constantly building tools for TON — WalletKit, AppKit, TON Connect, AI agents and all that good stuff. And the more we build, the more new use cases and developer questions we see that are not always obvious upfront

So we’re opening a dev open mic for the community. Simple format: you drop a question → I answer as an engineer, not as a press release. If a question is really good, we might break it out into a separate post

Anyway, let’s have a proper dev conversation in the comments

TON developer documentation has been fully updated

Now everything needed to build in TON ecosystem is gathered in one place:

— smart contract documentation
— application development flows
— SDKs and tools
— general documentation for TON blockchain

Navigation is now much simpler, the structure is clearer; finding what you need is way much faster.

Click to see fully revised TON documentation

docs.ton.org — updated structure, improved search and much more

TON Tech team shipped a major documentation update. Here are the highlights:

— new navigation built around developer flows
— dedicated Applications section for AppKit, TON Connect, TON Pay and WalletKit
— redesigned TON Center API reference
— new search with proper prioritization
— llms.txt and markdown endpoints for AI agents
— hundreds of DX and UX fixes across the documentation

Read more about the docs.ton.org update here

TON Tech X | TON Tech RU

🪙 Toncoin Name Change — Community Vote

TON has changed substantially in recent months. Telegram is taking on a leading role in the network and is becoming its largest validator. The chain itself is now 10× faster with fees down 6×. Gram was the name the network's founders gave the token in the original TON White Paper, and it's never left the codebase.

That is why Telegram is proposing to rename the native token from Toncoin to Gram, a fitting moment to bring it forward.

The blockchain stays TON / The Open Network, only the token's name and ticker change. Balances, addresses, contracts, NFTs, staking, DeFi, all unchanged. No swap, bridge, claim, or migration. No action required.

⚠️ Any site, bot, or link asking you to "claim GRAM" or "migrate TON" is a scam.

How the vote works
Runs for one week on TON Vote, an established open DAO platform on TON ▪️ Voting power is weighted by TON balances

👉 Vote here

TON Connect v3. TON Connect has received a major update with gasless transactions, connect-and-action flows in a single step, and new tools for working with jettons and NFTs.

Read more about the update

Intro • 1 • 2 • 3 • More

TON Tech • 𝕏

Gasless transactions. Applications can now cover transaction fees for users and accept payments directly in jettons. For example, a user can buy something with USDT even if there is no TON in their wallet to pay for gas.

Intro • 1 • 2 • 3 • More

TON Tech • 𝕏

Embedded requests. Wallet connection and action execution can now be combined into a single flow. Instead of switching between the app and wallet twice, users can confirm both the connection and the transaction on a single screen.

Intro • 1 • 2 • 3 • More

TON Tech • 𝕏

TON Connect Bridge v3. The new bridge introduces horizontal scaling and shared infrastructure for the entire ecosystem. Wallets once again operate through a unified bridge, while developers get end-to-end observability from a click in a dApp all the way to a signature in the wallet.

Intro • 1 • 2 • 3 • More

TON Tech • 𝕏

Read more about all the updates, including new dApp scenarios, Structured items, Trace ID, the new Demo App, and AppKit and WalletKit improvements in the full article.

Intro • 1 • 2 • 3 • More

TON Tech • 𝕏