🔨 TON Connect SDK Update
We're excited to announce a new release of the TON Connect SDK with significant enhancements for dApp developers.
We kindly request all dapp developers to update to the latest version to ensure optimal performance and user experience.
👥 @tonconnect/{sdk,ui,ui-react}
• New wallet feature requirements API
• Extra currencies in transactions
• React 19 compatibility
📁 New package versions
• @tonconnect/protocol 2.2.7
• @tonconnect/sdk 3.1.0
• @tonconnect/ui 2.1.0
• @tonconnect/ui-react 2.1.0
⬇️ To update, run
💡 To learn more, visit the GitHub page at https://github.com/ton-connect/sdk.
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-connect/sdk/issues.
⭐️ Special thanks to the Tonkeeper team for their contribution to this release!
🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!
We're excited to announce a new release of the TON Connect SDK with significant enhancements for dApp developers.
We kindly request all dapp developers to update to the latest version to ensure optimal performance and user experience.
• New wallet feature requirements API
• Extra currencies in transactions
• React 19 compatibility
• @tonconnect/protocol 2.2.7
• @tonconnect/sdk 3.1.0
• @tonconnect/ui 2.1.0
• @tonconnect/ui-react 2.1.0
npm install @tonconnect/ui-react@latest or npm install @tonconnect/ui@latestPlease open Telegram to view this post
VIEW IN TELEGRAM
❤12👍8❤🔥2😨2⚡1🌚1
🔥 New smart contract challenge — Tact Smart Battle
🧩 5 tasks
💰 $20k in prizes
🪪 On-chain reputation
💼 Real chance to get a job at TON
If you’ve joined past challenges — you’ll love this one.
📌 Announcement & details: https://news.1rj.ru/str/toncontests/194
🧩 5 tasks
💰 $20k in prizes
🪪 On-chain reputation
💼 Real chance to get a job at TON
If you’ve joined past challenges — you’ll love this one.
📌 Announcement & details: https://news.1rj.ru/str/toncontests/194
❤13👍11🔥11👎4🤬3🤣3
🔨 Introducing TON Connect QA
We're thrilled to announce the first alpha release of @tonconnect/qa, our new testing toolkit for TON dApps!
This new package helps developers automate QA for applications using TON Connect, making it easier to test wallet connections and transaction flows.
ℹ️ Note: The alpha version currently supports Tonkeeper Extension only, but this is sufficient for writing comprehensive e2e tests.
👥 Perfect for:
• Testing wallet connections and transaction flows
• Creating e2e tests for TON Connect integrations
⬇️ To install, run
💡 To learn more, visit the GitHub page at https://github.com/ton-connect/ton-connect-qa/
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-connect/ton-connect-qa/issues
🎁 Your input will help us improve this toolkit for the entire TON development community!
We're thrilled to announce the first alpha release of @tonconnect/qa, our new testing toolkit for TON dApps!
This new package helps developers automate QA for applications using TON Connect, making it easier to test wallet connections and transaction flows.
• Testing wallet connections and transaction flows
• Creating e2e tests for TON Connect integrations
npm install --save-dev @tonconnect/qaPlease open Telegram to view this post
VIEW IN TELEGRAM
🔥10👍5❤2
🔨 Dev Tools Updates
Fresh updates are here for TON development tools — boosting reliability, developer experience, and overall tooling performance. Be sure to upgrade and take advantage of the latest improvements!
👥 @ton/blueprint
📁 v0.32.0 – 2025-05-02
• Added compiler version display during contract build
• Introduced 'All Contracts' option in build wizard
• New function to build all Tact contracts (ideal for pre-test rebuilds)
• Improved error messages for non-PascalCase contract names
• blueprint build --all now properly exits with non-zero code on failure
📁 v0.31.0 – 2025-04-24
• Added Fift output support for FunC and Tolk build commands
• Integrated API reference into code
👥 @ton/sandbox
📁 v0.30.0 – 2025-05-12
• Updated config to v10
📁 v0.29.0 – 2025-04-30
• Refreshed API documentation
• Updated emulator WASM binary (TON v2025.04)
⬇ To update, run
💡 To learn more, visit the GitHub page at https://github.com/ton-org/blueprint or https://github.com/ton-org/sandbox.
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-org/blueprint/issues.
🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!
Fresh updates are here for TON development tools — boosting reliability, developer experience, and overall tooling performance. Be sure to upgrade and take advantage of the latest improvements!
• Added compiler version display during contract build
• Introduced 'All Contracts' option in build wizard
• New function to build all Tact contracts (ideal for pre-test rebuilds)
• Improved error messages for non-PascalCase contract names
• blueprint build --all now properly exits with non-zero code on failure
• Added Fift output support for FunC and Tolk build commands
• Integrated API reference into code
• Updated config to v10
• Refreshed API documentation
• Updated emulator WASM binary (TON v2025.04)
npm install @ton/blueprint@latest or npm install @ton/sandbox@latest.Please open Telegram to view this post
VIEW IN TELEGRAM
🔥7❤🔥2😱2❤1
🔨 Dev Tools Updates
Fresh updates are here for TON development tools. Be sure to upgrade and take advantage of the latest improvements!
👥 @ton/blueprint v0.33.0 – 2025-05-02
• Added support for tact.config.json
• Supported tolk v0.12
⬇ To update, run
💡 To learn more, visit the GitHub page at https://github.com/ton-org/blueprint.
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-org/blueprint/issues.
🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!
Fresh updates are here for TON development tools. Be sure to upgrade and take advantage of the latest improvements!
• Added support for tact.config.json
• Supported tolk v0.12
npm install @ton/blueprint@latestPlease open Telegram to view this post
VIEW IN TELEGRAM
🔥5🌚2❤1
🔨 Dev Tools Updates
Fresh updates are here for TON development tools — boosting reliability, developer experience, and overall tooling performance. Be sure to upgrade and take advantage of the latest improvements!
📁 @ton/blueprint v0.34.0 – 2025-05-20
📁 @ton/sandbox v0.31.0 – 2025-05-20
👥 Noticeable changes
• Introduced
• Added possibility to publish wrappers as npm packages through
• Added benchmarks functionality through
• Supported wallet id for mnemonic provider through env variables
⬇ To update, run
💡 To learn more, visit the GitHub page at https://github.com/ton-org/blueprint or https://github.com/ton-org/sandbox.
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-org/blueprint/issues.
🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!
Fresh updates are here for TON development tools — boosting reliability, developer experience, and overall tooling performance. Be sure to upgrade and take advantage of the latest improvements!
• Introduced
blueprint rename command to rename contracts• Added possibility to publish wrappers as npm packages through
blueprint pack command• Added benchmarks functionality through
blueprint snapshot and blueprint test --gas-report commands• Supported wallet id for mnemonic provider through env variables
npm install @ton/blueprint@latest and npm install @ton/sandbox@latest.Please open Telegram to view this post
VIEW IN TELEGRAM
🔥8🫡3❤1👍1
🔨 Dev Tools Updates
Fresh updates are here for TON development tools — boosting reliability, developer experience, and overall tooling performance. Be sure to upgrade and take advantage of the latest improvements!
📁 @ton/blueprint v0.35.0 – 2025-06-02
📁 @ton/sandbox v0.32.0 – 2025-06-02
📁 @ton/test-utils v0.7.0 – 2025-06-02
👥 Noticeable changes
• Added support for Tolk v0.13
• Added setting of PREVBLOCKS information
• Added address, opcode, and error denoscriptions to the toHaveTransaction method
• Added TON Lite Client as a network provider support
• Added Tolk Verifier via blueprint verify command
• Added Wallet v4r1 support
• Enabled custom manifestUrl in blueprint configuration
⬇ To update, run npm install @ton/blueprint@latest @ton/sandbox@latest @ton/test-utils@latest.
💡 To learn more, visit GitHub pages: https://github.com/ton-org/blueprint, https://github.com/ton-org/sandbox and https://github.com/ton-org/test-utils.
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-org/blueprint/issues.
🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!
Fresh updates are here for TON development tools — boosting reliability, developer experience, and overall tooling performance. Be sure to upgrade and take advantage of the latest improvements!
• Added support for Tolk v0.13
• Added setting of PREVBLOCKS information
• Added address, opcode, and error denoscriptions to the toHaveTransaction method
• Added TON Lite Client as a network provider support
• Added Tolk Verifier via blueprint verify command
• Added Wallet v4r1 support
• Enabled custom manifestUrl in blueprint configuration
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥9🫡3❤2🎉1
🔨 Dev Tools Updates
Fresh updates are out for TON development tools! These releases bring enhanced reliability, a smoother developer experience, and stronger tooling performance. Make sure to upgrade and enjoy the latest improvements!
📁 @ton/blueprint v0.36.0 – 2025-06-16
📁 @ton/sandbox v0.33.0 – 2025-06-16
📁 @ton/test-utils v0.8.0 – 2025-06-16
👥 Noticeable changes
• Added support for Func v0.4.6
• Added support for Tact v1.6.13
• Added support for Tolk v0.99
• New Jest matcher: toThrowExitCode for validating exitCode in tests.
• New Chai assertion: throwExitCode for similar exit code validation.
• ExitCode enum: Introduced for standardizing exit codes
• Added fetchConfig and setGlobalVersion utility functions
• Added blockchain.randomSeed property to update random seed in transactions or get methods
• Added support for updating blockchain config via loadConfig and updateConfig functions
• Blockchain.now not updating in blockchain.sendMessageIter is resolved
• Immutability fix: Blockchain.snapshot now returns copy, not reference
• Switched to Dirent.parentPath from deprecated .path
• Network Provider Enhancements. Added getConfig, getContractState and waitForLastTransaction methods
• Added utility getNormalizedExtMessageHash functions
⬇ To update, run npm install @ton/blueprint@latest @ton/sandbox@latest @ton/test-utils@latest.
💡 To learn more, visit GitHub pages: https://github.com/ton-org/blueprint, https://github.com/ton-org/sandbox and https://github.com/ton-org/test-utils.
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-org/blueprint/issues.
🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!
Fresh updates are out for TON development tools! These releases bring enhanced reliability, a smoother developer experience, and stronger tooling performance. Make sure to upgrade and enjoy the latest improvements!
• Added support for Func v0.4.6
• Added support for Tact v1.6.13
• Added support for Tolk v0.99
• New Jest matcher: toThrowExitCode for validating exitCode in tests.
• New Chai assertion: throwExitCode for similar exit code validation.
• ExitCode enum: Introduced for standardizing exit codes
• Added fetchConfig and setGlobalVersion utility functions
• Added blockchain.randomSeed property to update random seed in transactions or get methods
• Added support for updating blockchain config via loadConfig and updateConfig functions
• Blockchain.now not updating in blockchain.sendMessageIter is resolved
• Immutability fix: Blockchain.snapshot now returns copy, not reference
• Switched to Dirent.parentPath from deprecated .path
• Network Provider Enhancements. Added getConfig, getContractState and waitForLastTransaction methods
• Added utility getNormalizedExtMessageHash functions
Please open Telegram to view this post
VIEW IN TELEGRAM
❤2🏆2
🚀 Announcing FunC Debugger: Debug TON Smart Contracts with Ease!
We're excited to introduce the FunC Debugger – a powerful tool for TON developers to debug smart contracts efficiently! Say goodbye to guesswork and hello to streamlined contract debugging with real-time insights.
Key Features:
🔹 Stepping: Execute code line-by-line (Step In/Over/Out)
🔹 Breakpoints: Pause execution at specific code points
🔹 Variable Inspection: View contract state and variables in real-time
🔹 Call Stack: Track function execution flow
🔹 No bytecode modification: Unlike an earlier beta release of the debugger, this version does not modify the bytecode, so code hashes and gas usage matches exactly
How to Install & Use
1) Create a new project, or upgrade dependencies (blueprint 0.37.0, sandbox 0.34.0, and func-js 0.10.0) for existing projects
2) Modify the test: add blockchain.debug = true or smartContract.setDebug(true) before the section you'd like to debug; optionally, increase the test's timeout (to avoid errors in the console)
3) Add debugInfo: true to .compile.ts files of the contracts that you would like to debug
4) Install VS Code extension "TVM Debugger"
5) Launch the test
6) Connect using the extension (Cmd+Shift+P / Ctrl+Shift+P -> Debug TVM contract) once prompted
You can also take a look at the videos for a short demo of the debugger, and a demo of how to install it into a new project.
If you encounter any problems, please do not hesitate to open issues in the sandbox github page.
Happy debugging!
We're excited to introduce the FunC Debugger – a powerful tool for TON developers to debug smart contracts efficiently! Say goodbye to guesswork and hello to streamlined contract debugging with real-time insights.
Key Features:
🔹 Stepping: Execute code line-by-line (Step In/Over/Out)
🔹 Breakpoints: Pause execution at specific code points
🔹 Variable Inspection: View contract state and variables in real-time
🔹 Call Stack: Track function execution flow
🔹 No bytecode modification: Unlike an earlier beta release of the debugger, this version does not modify the bytecode, so code hashes and gas usage matches exactly
How to Install & Use
1) Create a new project, or upgrade dependencies (blueprint 0.37.0, sandbox 0.34.0, and func-js 0.10.0) for existing projects
2) Modify the test: add blockchain.debug = true or smartContract.setDebug(true) before the section you'd like to debug; optionally, increase the test's timeout (to avoid errors in the console)
3) Add debugInfo: true to .compile.ts files of the contracts that you would like to debug
4) Install VS Code extension "TVM Debugger"
5) Launch the test
6) Connect using the extension (Cmd+Shift+P / Ctrl+Shift+P -> Debug TVM contract) once prompted
You can also take a look at the videos for a short demo of the debugger, and a demo of how to install it into a new project.
If you encounter any problems, please do not hesitate to open issues in the sandbox github page.
Happy debugging!
🔥15❤10
Blueprint just made gas optimization easy. Run one command:
npx blueprint test --gas-report, get a detailed report showing exactly how much gas each method uses. Compare versions side-by-side and spot inefficiencies instantly with Sandbox's new metrics tools.https://docs.ton.org/v3/guidelines/smart-contracts/testing/collect-contract-gas-metric
Please open Telegram to view this post
VIEW IN TELEGRAM
❤🔥9👍3🔥2🦄2
Forwarded from TOLK lang
🫧 Tolk v1.0: lazy loading, partial updating, AST inlining — and extremely low gas fees
This is happening today.
I managed not only to finish up the compiler, but also to migrate standard contracts from FunC to Tolk.
I covered every contract with gas metrics to check whether it's more efficient than FunC or not. I didn't believe my eyes. I double-checked, triple-checked, but nothing changed. The results are correct. And now I am ready to present them to you.
🧪 Benchmarks!
Every contract has several metrics. For example, "basic jetton — mint".
FunC: 19278. Tolk: 11611.
Gas savings: -39.77%
|————————————————–-
| 01 — Jetton (mint, transfer, burn, discover)
| -39.77% | -30.32% | -33.66% | -26.75%
|————————————————–-
| 02 — NFT (deploy, transfer, onchain get)
| -43.79% | -37.47% | -44.28%
|————————————————–-
| 03 — Notcoin
| -35.72% | -27.98% | ...
|————————————————–-
| 04 — tgBTC
| -23.94% | -26.99% | ...
|————————————————–-
| 05 — Wallet v5
| -21.66% | -22.92% | ...
|————————————————–-
| 06 — Vesting
| -45.30% | -29.61% | ...
|————————————————–-
| 07 — Telegram gifts
| -54.81% | -39.39% | ...
|————————————————–-
I have migrated 7 contracts — preserving the original behavior and passing the same tests.
All benchmarks are open. No cheating. Just a smart compiler — and a language designed to be optimized.
— Even wallet?! But it's very low-level and tricky!
Even wallet. You just express your thoughts without any tricks — and it works automatically.
— But how? How is it possible to achieve such numbers?
Of course, I've put a lot of smartness into the compiler. A strong type system. Automatic inlining. Built-in serialization. The magic
But first of all, Tolk is built for readability. These contracts aren't "just cleaner" than their FunC equivalents — they're elegant. No magic. No low-level intrigues. Just clean, consistent logic — whether it's a Jetton or a Wallet.
And gas savings? They are a consequence. I didn't micro-optimize. Each contract was rewritten in about a day — just focusing on clarity. The core principle is simple: once you make it elegant, it automatically becomes efficient.
✅ Notable changes in Tolk v1.0:
1. Lazy loading — only read what you actually use
2. AST-based inlining — zero-cost getters and methods
3. Peephole optimizations, TVM-11 — smaller code, lower gas
PR on GitHub with detailed info.
Just take a look:
That's it. Lazy loading and partial updates (calculating immutable slices for writing) — one magic
⚙️ The Release. What's inside
- JetBrains IDE plugin — with completion, resolving, etc... ✓ done
- VS Code Extension — with suggestions, stdlib integration, etc... ✓ done
- Language server — for any LSP-compatible editor... ✓ done
- FunC-to-Tolk converter — migrate a project in 10 seconds... ✓ done
- Documentation — for smooth transition from FunC... ✓ done
And the TOLK language itself — exactly as I've visioned it... 7 months ago
📅 The essence of Numbers
At this moment, abstract yourself from the text. Take a look at the calendar.
Today is 07/07/25 (I mean 2+5, of course).
After the TON Gateway, throughout all November, I was laying out the roadmap towards Tolk v1.0. On December 1, I started working. It means, that the journey till now took exactly 7 months 7 days. If you scroll this channel to the top, you'll see an announcement... Of Tolk v0.7
🪐 What's next?
I could have written about my plans — for the language, TVM, ABI, TypeScript wrappers... but I won't.
Because today, instead of rushing into the future, maybe we can allow ourselves to look back.
To pause the endless race — just for a moment.
To notice how many beautiful coincidences pass us by — unnoticed in our constant hurry.
Just step outside.
Close your eyes.
Count to seven.
Feel it.
When you're ready —
Let's Tolk
This is happening today.
I managed not only to finish up the compiler, but also to migrate standard contracts from FunC to Tolk.
I covered every contract with gas metrics to check whether it's more efficient than FunC or not. I didn't believe my eyes. I double-checked, triple-checked, but nothing changed. The results are correct. And now I am ready to present them to you.
🧪 Benchmarks!
Every contract has several metrics. For example, "basic jetton — mint".
FunC: 19278. Tolk: 11611.
Gas savings: -39.77%
|————————————————–-
| 01 — Jetton (mint, transfer, burn, discover)
| -39.77% | -30.32% | -33.66% | -26.75%
|————————————————–-
| 02 — NFT (deploy, transfer, onchain get)
| -43.79% | -37.47% | -44.28%
|————————————————–-
| 03 — Notcoin
| -35.72% | -27.98% | ...
|————————————————–-
| 04 — tgBTC
| -23.94% | -26.99% | ...
|————————————————–-
| 05 — Wallet v5
| -21.66% | -22.92% | ...
|————————————————–-
| 06 — Vesting
| -45.30% | -29.61% | ...
|————————————————–-
| 07 — Telegram gifts
| -54.81% | -39.39% | ...
|————————————————–-
I have migrated 7 contracts — preserving the original behavior and passing the same tests.
All benchmarks are open. No cheating. Just a smart compiler — and a language designed to be optimized.
— Even wallet?! But it's very low-level and tricky!
Even wallet. You just express your thoughts without any tricks — and it works automatically.
— But how? How is it possible to achieve such numbers?
Of course, I've put a lot of smartness into the compiler. A strong type system. Automatic inlining. Built-in serialization. The magic
lazy keyword.But first of all, Tolk is built for readability. These contracts aren't "just cleaner" than their FunC equivalents — they're elegant. No magic. No low-level intrigues. Just clean, consistent logic — whether it's a Jetton or a Wallet.
And gas savings? They are a consequence. I didn't micro-optimize. Each contract was rewritten in about a day — just focusing on clarity. The core principle is simple: once you make it elegant, it automatically becomes efficient.
✅ Notable changes in Tolk v1.0:
1. Lazy loading — only read what you actually use
2. AST-based inlining — zero-cost getters and methods
3. Peephole optimizations, TVM-11 — smaller code, lower gas
PR on GitHub with detailed info.
Just take a look:
val st = lazy Storage.load();
// the compiler skips everything and loads only what you access
return st.publicKey;
That's it. Lazy loading and partial updates (calculating immutable slices for writing) — one magic
lazy keyword to rule them all.⚙️ The Release. What's inside
- JetBrains IDE plugin — with completion, resolving, etc... ✓ done
- VS Code Extension — with suggestions, stdlib integration, etc... ✓ done
- Language server — for any LSP-compatible editor... ✓ done
- FunC-to-Tolk converter — migrate a project in 10 seconds... ✓ done
- Documentation — for smooth transition from FunC... ✓ done
And the TOLK language itself — exactly as I've visioned it... 7 months ago
📅 The essence of Numbers
At this moment, abstract yourself from the text. Take a look at the calendar.
Today is 07/07/25 (I mean 2+5, of course).
After the TON Gateway, throughout all November, I was laying out the roadmap towards Tolk v1.0. On December 1, I started working. It means, that the journey till now took exactly 7 months 7 days. If you scroll this channel to the top, you'll see an announcement... Of Tolk v0.7
🪐 What's next?
I could have written about my plans — for the language, TVM, ABI, TypeScript wrappers... but I won't.
Because today, instead of rushing into the future, maybe we can allow ourselves to look back.
To pause the endless race — just for a moment.
To notice how many beautiful coincidences pass us by — unnoticed in our constant hurry.
Just step outside.
Close your eyes.
Count to seven.
Feel it.
When you're ready —
Let's Tolk
🔥10❤2❤🔥1💊1
🔨 Dev Tools Updates
Fresh updates are out for TON development tools! This release brings enhanced reliability, a smoother developer experience, and improved performance across the board. Most notably, dev tools now offer full support for the newly released Tolk v1.0 — the next-gen language for smart contract development on TON.
📁 @ton/blueprint v0.38.0 – 2025-07-07
📁 @ton/sandbox v0.35.0 – 2025-07-07
📁 @ton/test-utils v0.9.0 – 2025-07-07
👥 Noticeable changes
• Supported Tolk v1.0
• Update default config to match latest update
• Added mode matcher for transaction
⬇ To update, run npm install @ton/blueprint@latest @ton/sandbox@latest @ton/test-utils@latest.
💡 To learn more, visit GitHub pages: https://github.com/ton-org/blueprint, https://github.com/ton-org/sandbox and https://github.com/ton-org/test-utils.
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-org/blueprint/issues.
🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!
Fresh updates are out for TON development tools! This release brings enhanced reliability, a smoother developer experience, and improved performance across the board. Most notably, dev tools now offer full support for the newly released Tolk v1.0 — the next-gen language for smart contract development on TON.
• Supported Tolk v1.0
• Update default config to match latest update
• Added mode matcher for transaction
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥7❤1🙏1
Forwarded from TON Core
🎉 Unified TON Extension for VS Code is here!
Following the single convenient JetBrains IDE plugin, we are now introducing a unified extension for TON development for VS Code that supports all necessary languages and technologies.
This is the first contribution from Petr, who recently joined the TON Core team to make life sweeter for TON developers.
📜 The extension provides advanced features for the main TON technologies: Tolk, FunC, TL-B, Fift Assembly, TASM, BoC, Blueprint! If you use the old extensions for Tolk or FunC, we recommend trying the new extension, as it offers better language support (we even support try/catch for FunC 😎).
📥 Install now
- VS Code Marketplace
- Open VSX (if you use Cursor, Windsurf, etc.)
We thank the @tontech team for the FunC debugger which is now integrated into the extension, so you don't need to install a separate extension!
Happy hacking! 🛠️✨
Following the single convenient JetBrains IDE plugin, we are now introducing a unified extension for TON development for VS Code that supports all necessary languages and technologies.
This is the first contribution from Petr, who recently joined the TON Core team to make life sweeter for TON developers.
📜 The extension provides advanced features for the main TON technologies: Tolk, FunC, TL-B, Fift Assembly, TASM, BoC, Blueprint! If you use the old extensions for Tolk or FunC, we recommend trying the new extension, as it offers better language support (we even support try/catch for FunC 😎).
📥 Install now
- VS Code Marketplace
- Open VSX (if you use Cursor, Windsurf, etc.)
We thank the @tontech team for the FunC debugger which is now integrated into the extension, so you don't need to install a separate extension!
Happy hacking! 🛠️✨
🔥11❤6🦄3
We're excited to announce that Sign Data is now officially supported in TON Connect v2.2.0! This feature allows dApps to request signatures on arbitrary data — ideal for authentication, message signing, and more.
We kindly encourage all developers to explore and integrate this powerful capability into their dApps.
signData• Supports
text, binary, and cell data types• Enables secure off-chain data signing
• @tonconnect/protocol 2.3.0
• @tonconnect/sdk 3.3.0
• @tonconnect/ui 2.2.0
• @tonconnect/ui-react 2.2.0
const result = await tonConnectUI.signData({
type: "text",
text: "Confirm new 2fa number: +1 234 567 8901"
});
console.log('Signed:', result);npm install @tonconnect/ui-react@latest or npm install @tonconnect/ui@latest• SignData request/response specification
• SignData documentation
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥10❤8🥰3💘1
Great news — the latest TON update (v2025.06) brings TVM v11, and TON Devtools is already fully compatible!
npm create ton@latest
Let’s build powerful things on TON
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥6❤5🏆3
🔨 Dev Tools Updates
New updates have landed for TON development tools — delivering greater stability, better performance, and a smoother workflow for developers building on TON.
📁 @ton/blueprint v0.39.1 – 2025-08-05
📁 @ton/sandbox v0.36.0 – 2025-08-04
📁 @ton/test-utils v0.10.0 – 2025-08-04
👥 Highlights & New Features
• New
•
•
• Code coverage support
•
•
• Support for the Bun test runner
⬇ To update, run
💡 To learn more, visit GitHub pages: https://github.com/ton-org/blueprint, https://github.com/ton-org/sandbox and https://github.com/ton-org/test-utils.
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-org/blueprint/issues.
🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!
New updates have landed for TON development tools — delivering greater stability, better performance, and a smoother workflow for developers building on TON.
• New
--compiler-version flag for selecting specific compiler versions during contract verification•
buildLibrary wrapper compile config and compile function option to convert the built code into a library•
Blockchain.getTransactions method to fetch transactions• Code coverage support
•
allowParallel flag in Blockchain.sendMessageIter, allowing for testing MITM attack•
autoDeployLibs flag for automatic detection of deployed libraries• Support for the Bun test runner
npm install @ton/blueprint@latest @ton/sandbox@latest @ton/test-utils@latestPlease open Telegram to view this post
VIEW IN TELEGRAM
❤10👍6🏆3
Please update and test so your dApp is ready for the stable 2.3.0 on Mon, Aug 25. This is part of a larger effort to increase success rate across the TON ecosystem.
• ton_proof limits: payload ≤ 128 bytes, domain ≤ 128 bytes, payload + domain ≤ 222 bytes. If you exceed these limits, the connection will fail.
• sendTransaction & signData: requests are now strictly validated against the spec. Non-conformant requests will fail.
• Connect (ton_proof only): ensure your payload and domain sizes are within limits. Typical failure causes: the payload or domain does not meet the limits.
• Send transctions: verify the request shape, required fields, types, encodings exactly match the spec. Typical failure causes: invalid address format, amount not a string, bad payload/stateInit encoding, unknown fields.
• Sign data: verify the request type and fields are correct. Typical failure causes: wrong type and field combination, bad encoding.
Please open Telegram to view this post
VIEW IN TELEGRAM
❤16❤🔥1
This continues our push to improve reliability and success rates across the TON ecosystem.
• BREAKING: ton_proof limits: payload ≤ 128 bytes, domain ≤ 128 bytes, payload + domain ≤ 222 bytes. If you exceed these limits, the connection will fail.
• BREAKING: sendTransaction & signData: requests are now strictly validated against the spec. Non-conformant requests will fail.
• stateInit, payload, and cell now accept both Base64 and Base64URL, auto-converted to Base64 per spec.
• Migrated wallet list URL to https://config.ton.org/wallets-v2.json for improved reliability
• Updated fallback wallets list to match https://config.ton.org/wallets-v2.json
• Client ID added to all deeplinks to allow better UX on the wallet side.
• Improved overall package quality and stability, increased test coverage.
• Connect (ton_proof only): ensure your payload and domain sizes are within limits. Typical failure causes: the payload or domain does not meet the limits.
• Send transactions: verify that the request shape, required fields, types, encodings exactly match the spec. Typical failure causes: invalid address format, amount not a string, bad payload/stateInit encoding, unknown fields.
• Sign data: verify the request type and fields are correct. Typical failure causes: wrong type and field combination, bad encoding.
npm install @tonconnect/sdk@3.3.1 @tonconnect/ui@2.3.1 @tonconnect/ui-react@2.3.1Please open Telegram to view this post
VIEW IN TELEGRAM
❤🔥4💘3❤1👌1
🔨 Simplifying code coverage in Blueprint
The new update introduces command, which collects coverage reports from all tests into the
📁 @ton/blueprint v0.41.0 – 2025-09-23
📁 @ton/sandbox v0.37.2 – 2025-09-23
⬇ To update, run
💡 To learn more, visit GitHub pages: https://github.com/ton-org/blueprint, https://github.com/ton-org/sandbox.
💬 Encountered issues? Please report them on GitHub at https://github.com/ton-org/blueprint/issues.
🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!
The new update introduces command, which collects coverage reports from all tests into the
coverage directory. Update your packages and try it out now!
blueprint test --coverage
npm install @ton/blueprint@latest @ton/sandbox@latestPlease open Telegram to view this post
VIEW IN TELEGRAM
🔥9❤🔥3🌚3
We're introducing enhanced verification features to provide users with better transparency and trust indicators. Rollout to wallets is starting — please review your manifests to ensure optimal user experience.
• Your app's hosting domain should match the domain specified in your manifest.json → url parameter
• No SDK changes required, existing integrations continue working
• Feature is being deployed to wallets progressively
• Domain alignment: ensure your app domain matches the domain in manifest.json url parameter. Typical issue: url parameter contains different domain than app hosting domain.
• Manifest accessibility: verify your manifest.json is accessible. Typical issues: CORS issues, manifest not found.
👍 Correct:
App hosted on: https://myapp.ton.org
manifest.json: { "url": "https://myapp.ton.org", ... }👎 Incorrect:
App hosted on: https://myapp.ton.org
manifest.json: { "url": "https://another.myapp.ton.org", ... }
Please open Telegram to view this post
VIEW IN TELEGRAM
👍8💘3🔥2