Forwarded from Telegram Contests
Telegram and TON Core announce a new bug bounty contest!
Prize Fund: Up to $100,000
Deadline: 23:59, March 27 (Dubai time)
Task: Analyze TONβs new consensus algorithm for potential vulnerabilities.
Reports on other validator bugs are also welcome, but consensus-related issues remain the top priority.
Prize Fund Distribution
The total prize fund, up to $100,000, will be allocated based on each participant's overall contribution.
Guidelines and Submissions
For detailed instructions, contest rules, and submission guidelines, refer to this document.
Additional Opportunities
Winners may have the chance to join the Telegram or TON Core teams.
Please open Telegram to view this post
VIEW IN TELEGRAM
π₯25β€14π8π1
Tolk Programming Langauge 1.3
β Type
β Type
β Type
β Type string β text chunks backed by snaked cells, with
β Compile-time string methods:
β Null coalescing operator β
β Import path mappings β
β Compile-time reflection via
β Custom serializers now support structures and generics.
β The compiler now reports multiple errors at once.
β Focused on stability β fixed dozens of minor issues found by LLM fuzzing.
β Extensive internal refactoring towards being stateless and multi-threaded.
Release Β»
Read more Β»
β Type
array<T> β dynamically sized arrays backed by TVM tuples.β Type
unknown β a TVM primitive with unknown contents.β Type
lisp_list<T> β nested two-element tuples (FunC-style).β Type string β text chunks backed by snaked cells, with
StringBuilder for concatenation.β Compile-time string methods:
"str".crc32(), "str".sha256(), etc.β Null coalescing operator β
?? like in TypeScript.β Import path mappings β
import "@third_party/utils".β Compile-time reflection via
@stdlib/reflection.β Custom serializers now support structures and generics.
β The compiler now reports multiple errors at once.
β Focused on stability β fixed dozens of minor issues found by LLM fuzzing.
β Extensive internal refactoring towards being stateless and multi-threaded.
Release Β»
Read more Β»
π₯26β€21π€9π4β‘2π€¬2π©2π2π1π€©1
Sub-Second mainnet activation starts
The public bug bounty contest for the TON Sub-Second update has been completed.
We thank all participants for their work and valuable feedback. The corresponding changes have already been applied to the codebase. No major consensus changes were required.
The final contest results and reward distribution will be announced later.
This contest was the final stage of testing before mainnet activation. Prior to that, the update had already passed internal testing by TON Core and extended testing in testnet.
We are now starting the activation of the Sub-Second update in TON mainnet.
For additional reliability, activation will be performed in 3 stages:
Update plan:
March 31 (today): Upgrade validator nodes to the version supporting the latest consensus changes.
April 2: Vote to activate the new consensus on the basechain and enable a moderate block rate increase.
April 7: Vote to fully activate fast consensus on both the basechain and masterchain and then upgrade validator nodes.
The Sub-Second update is a major protocol upgrade comprising a substantial number of changes.
Despite comprehensive testing, validators are advised to maintain heightened operational readiness during the next two weeks, from March 31 to April 12.
The TON Core team will remain available throughout the deployment and is prepared to respond promptly to any situations.
The public bug bounty contest for the TON Sub-Second update has been completed.
We thank all participants for their work and valuable feedback. The corresponding changes have already been applied to the codebase. No major consensus changes were required.
The final contest results and reward distribution will be announced later.
This contest was the final stage of testing before mainnet activation. Prior to that, the update had already passed internal testing by TON Core and extended testing in testnet.
We are now starting the activation of the Sub-Second update in TON mainnet.
For additional reliability, activation will be performed in 3 stages:
Update plan:
March 31 (today): Upgrade validator nodes to the version supporting the latest consensus changes.
April 2: Vote to activate the new consensus on the basechain and enable a moderate block rate increase.
April 7: Vote to fully activate fast consensus on both the basechain and masterchain and then upgrade validator nodes.
The Sub-Second update is a major protocol upgrade comprising a substantial number of changes.
Despite comprehensive testing, validators are advised to maintain heightened operational readiness during the next two weeks, from March 31 to April 12.
The TON Core team will remain available throughout the deployment and is prepared to respond promptly to any situations.
β€29π12π₯6
Sub-Second for the TON Ecosystem
As part of the Sub-Second mainnet rollout, ecosystem participants should review the following guidance.
For Validators and Node owners
Follow @tonstatus.
For API developers
Please update your own nodes as described in the corresponding post.
APIs will continue functioning after the network upgrade. No additional compatibility changes are required.
If you were previously using low-end hardware, you may need to upgrade it due to the increased block rate
To deliver near-instant UX, we recommend adopting the latest API practices:
β Enable WebSockets support.
β Optimize general API latency.
β Support Pending and Confirmed operation statuses.
You can refer to the changes in the Toncenter API.
For exchanges and payment services
If you are running your own node, please update it as described in the corresponding post.
If you are using an API, whether external or self-hosted, no action is required.
No additional changes are needed. Transaction finality should continue to be determined based on masterchain finalization, as before.
For products and dApps
If you are running your own node, please update it as described in the corresponding post.
If you are using an API, whether external or self-hosted, no action is required.
Products and APIs will continue functioning after the network upgrade. No additional compatibility changes are required.
To deliver near-instant UX, we recommend adopting the latest UX practices:
β Use Toncenter Streaming API V2.
β Display an operation in the UI once it reaches Pending status.
β Mark an operation as completed once it reaches Confirmed status.
You can refer to the changes in mytonwallet.io and tonscan.org.
As part of the Sub-Second mainnet rollout, ecosystem participants should review the following guidance.
For Validators and Node owners
Follow @tonstatus.
For API developers
Please update your own nodes as described in the corresponding post.
APIs will continue functioning after the network upgrade. No additional compatibility changes are required.
If you were previously using low-end hardware, you may need to upgrade it due to the increased block rate
To deliver near-instant UX, we recommend adopting the latest API practices:
β Enable WebSockets support.
β Optimize general API latency.
β Support Pending and Confirmed operation statuses.
You can refer to the changes in the Toncenter API.
For exchanges and payment services
If you are running your own node, please update it as described in the corresponding post.
If you are using an API, whether external or self-hosted, no action is required.
No additional changes are needed. Transaction finality should continue to be determined based on masterchain finalization, as before.
For products and dApps
If you are running your own node, please update it as described in the corresponding post.
If you are using an API, whether external or self-hosted, no action is required.
Products and APIs will continue functioning after the network upgrade. No additional compatibility changes are required.
To deliver near-instant UX, we recommend adopting the latest UX practices:
β Use Toncenter Streaming API V2.
β Display an operation in the UI once it reaches Pending status.
β Mark an operation as completed once it reaches Confirmed status.
You can refer to the changes in mytonwallet.io and tonscan.org.
β€33π₯16π9π―7π₯°2π€2
Forwarded from TON Status
Sub-Second is Live
The vote to enable Sub-Second has passed, and the blockchain has switched to the new high-speed mode.
The blockchain is currently running stably.
About 7% of validators have not yet updated, so the block production rate is still slightly below the target
We ask validators who have not yet updated to do so.
API developers and product developers β please make sure everything is working properly in your services.
The vote to enable Sub-Second has passed, and the blockchain has switched to the new high-speed mode.
The blockchain is currently running stably.
About 7% of validators have not yet updated, so the block production rate is still slightly below the target
We ask validators who have not yet updated to do so.
API developers and product developers β please make sure everything is working properly in your services.
π₯31β€14π10π¦7
Scheduled Closure of the Token Bridge V3
Effective April 27 at 12:00 UTC, token transfers from Ethereum to TON through the bridge-v3.ton.org will be permanently discontinued.
Claims for previously completed transfers will remain available.
Transfers from TON to Ethereum will remain available. The token-amount-based fee for such transfers will be removed.
This is a planned closure of the Token Bridge V3, following the earlier discontinuation of jUSDT and Toncoin transfers. All user funds remain safe.
The Token Bridge played an important role in the early development of the TON ecosystem.
The ecosystem is transitioning to newer cross-chain solutions:
https://ton.org/bridges
Effective April 27 at 12:00 UTC, token transfers from Ethereum to TON through the bridge-v3.ton.org will be permanently discontinued.
Claims for previously completed transfers will remain available.
Transfers from TON to Ethereum will remain available. The token-amount-based fee for such transfers will be removed.
This is a planned closure of the Token Bridge V3, following the earlier discontinuation of jUSDT and Toncoin transfers. All user funds remain safe.
The Token Bridge played an important role in the early development of the TON ecosystem.
The ecosystem is transitioning to newer cross-chain solutions:
https://ton.org/bridges
π16π€©12π’6β€3π3π3π3β‘2π€―1
Blockchain Fee Reduction
The TON Core team has prepared a blockchain update (TON 2026.04, TON 2026.04-1) to reduce fees by 6x, in line with Pavel Durovβs MTONGA plan.
This update includes:
1) Performance improvements
The previous Sub-Second update improved not only operation speed but also overall blockchain performance, making a fee reduction possible. Since then, additional optimizations and performance improvements have also been implemented, including a new mempool based on a persistent Cartesian tree.
2) Fixes
In addition to performance improvements, this update will include fixes for issues identified on mainnet after the Sub-Second release. In particular, it addresses loss of synchronization on some liteservers and rare block rate instability.
Planned Schedule:
April 28, 2026 12:00 UTC β Validator software update.
April 30, 2026 13:00 UTC β Vote to lower gas prices in the blockchain configuration.
Lower fees are important for the next stages of the MTONGA plan. Since fees do not constitute a significant portion of validator rewards, validator rewards are expected to decrease by less than 0.4%.
Mainnet validator operators are asked to be prepared to update their software on 28 April and to participate in the vote on 30 April.
The TON Core team has prepared a blockchain update (TON 2026.04, TON 2026.04-1) to reduce fees by 6x, in line with Pavel Durovβs MTONGA plan.
This update includes:
1) Performance improvements
The previous Sub-Second update improved not only operation speed but also overall blockchain performance, making a fee reduction possible. Since then, additional optimizations and performance improvements have also been implemented, including a new mempool based on a persistent Cartesian tree.
2) Fixes
In addition to performance improvements, this update will include fixes for issues identified on mainnet after the Sub-Second release. In particular, it addresses loss of synchronization on some liteservers and rare block rate instability.
Planned Schedule:
April 28, 2026 12:00 UTC β Validator software update.
April 30, 2026 13:00 UTC β Vote to lower gas prices in the blockchain configuration.
Lower fees are important for the next stages of the MTONGA plan. Since fees do not constitute a significant portion of validator rewards, validator rewards are expected to decrease by less than 0.4%.
Mainnet validator operators are asked to be prepared to update their software on 28 April and to participate in the vote on 30 April.
β€68π₯39β‘28π€―6
TON Core
Blockchain Fee Reduction The TON Core team has prepared a blockchain update (TON 2026.04, TON 2026.04-1) to reduce fees by 6x, in line with Pavel Durovβs MTONGA plan. This update includes: 1) Performance improvements The previous Sub-Second update improvedβ¦
Voting by validators on reducing network fees has begun
Validators, please participate in the vote.
Follow the voting progress here.
UPD: All proposals were accepted, fees on the mainnet have been reduced, thank you!
Validators, please participate in the vote.
Follow the voting progress here.
UPD: All proposals were accepted, fees on the mainnet have been reduced, thank you!
β€41β10π3π€©3π€¬1π©1
Tolk 1.4 Programming Language
Introducing source maps, debugger support, ABI export, and auto-generated TypeScript wrappers.
β ABI export for toolchains, explorers, SDKs, and UI integrations.
β Auto-generated TypeScript wrappers for Tolk smart contracts.
β Source maps that connect TVM execution back to Tolk source code, variables, stack layout, and call frames.
β Debugger marks that enable step-by-step debugging of fully optimized production contracts.
β Language enhancements continuing Tolkβs evolution toward a general-purpose smart contract language.
Release Β»
Introducing source maps, debugger support, ABI export, and auto-generated TypeScript wrappers.
β ABI export for toolchains, explorers, SDKs, and UI integrations.
β Auto-generated TypeScript wrappers for Tolk smart contracts.
β Source maps that connect TVM execution back to Tolk source code, variables, stack layout, and call frames.
β Debugger marks that enable step-by-step debugging of fully optimized production contracts.
β Language enhancements continuing Tolkβs evolution toward a general-purpose smart contract language.
Release Β»
π₯21β€5π€―3π¨βπ»2π¦2π±1π³1
Introducing Acton β a new, modern toolchain for developing smart contracts on TON
Acton covers the full development lifecycle: project creation, testing, debugging, dApp integration, deployment, and verification.
CLI-first by design, it works naturally for both developers and AI agents.
1. One toolchain, not a bunch of utilities
Create, build, test, lint, format, deploy, and verify TON contracts in a single coherent environment around Tolk.
2. A tighter build-test-debug loop
Write tests directly in Tolk programming language, run them fast, debug failed transactions, and inspect what actually happened on-chain.
3. Security built in
Coverage, fuzzing, mutation testing, gas profiling, and CI help catch regressions early.
4. A native debugger
Step in, step over, step out, watch variables, and inspect the call stack. A smooth Web2-style developer experience, now inside a blockchain language.
5. Friendly for AI agents
A modern CLI tool that becomes an agent's runtime, with skills and manuals bundled.
6. IDE integtation
Use it with VS Code, JetBrains, Cursor, Zed, and other LSPβbased editors.
Read more Β»
Docs Β»
Author's notes Β»
Acton covers the full development lifecycle: project creation, testing, debugging, dApp integration, deployment, and verification.
CLI-first by design, it works naturally for both developers and AI agents.
1. One toolchain, not a bunch of utilities
Create, build, test, lint, format, deploy, and verify TON contracts in a single coherent environment around Tolk.
2. A tighter build-test-debug loop
Write tests directly in Tolk programming language, run them fast, debug failed transactions, and inspect what actually happened on-chain.
3. Security built in
Coverage, fuzzing, mutation testing, gas profiling, and CI help catch regressions early.
4. A native debugger
Step in, step over, step out, watch variables, and inspect the call stack. A smooth Web2-style developer experience, now inside a blockchain language.
5. Friendly for AI agents
A modern CLI tool that becomes an agent's runtime, with skills and manuals bundled.
6. IDE integtation
Use it with VS Code, JetBrains, Cursor, Zed, and other LSPβbased editors.
Read more Β»
Docs Β»
Author's notes Β»
ton-blockchain.github.io
Acton β a unified toolchain for TON
Acton is an all-in-one CLI built around Tolk β from project creation to tests, debugging, dApp integration, deployment, and verification.
π₯22π€―15β€7π±7β€βπ₯2π³1π¨βπ»1π¦1
This media is not supported in your browser
VIEW IN TELEGRAM
One of Actonβs key features is its advanced support for developing TON smart contracts using AI.
π€―61β€βπ₯48π±31β€9π₯9π5π4π¨βπ»2π³1π1π¦1