TON Tech

TON Tech: what we’ve built and what’s available now Over the past months, we’ve been expanding TON developer stack. This is a quick overview of what’s available today TON Connect The protocol to connect apps and wallets on TON. Over the past months, we’ve improved its stability, speed, security and compatibility with the rest of the stack — so the rest of the developer stack can build on top of it AppKit SDK for building TON apps using familiar patterns. Provides ready-to-use primitives for balances, transactions, swaps and NFTs, with built-in integrations so these features work out of the box WalletKit SDK for building wallets across web, iOS, Android and React Native. Handles TON Connect, signing, asset management and transaction flow AgentKit Tools for building AI agents that can interact with TON via MCP. Balances, transactions, swaps and assets are accessible through natural language Network progress Sub-second finality has been rolled out. TON Core upgraded the blockchain and API, and we’ve worked with ecosystem projects to roll out the update. What this means • <1 sec transaction confirmation • faster block production • improved real-time UX If you’re building, this channel will save you time We’ve just launched a Russian-language TON Tech channel Follow for updates in Russian @tontechru Where TON builders talk TON Dev Chat (EN) • TON Dev Chat (RU) Use this to start Docs • build with SDKs • explore AppKit • work with TON Connect How all parts connect and why this stack exists — read the full article

💎 AppKit | Alpha Announcement TON is the blockchain built into Telegram. Apps built on TON can reach Telegram's billion+ users directly. Until now, every team had to build wallet connections, transaction handling, and DeFi integrations from scratch. Weeks of work before a single line of product code. Today we're announcing AppKit alpha to change that. What's live now: ▪️ Wallet management and transaction sending ▪️ DeFi integration (swaps, staking) ▪️ TON Connect support ▪️ TypeScript and React support ▪️ LLM-friendly (describe an app, build a prototype in minutes) WalletKit is also production-ready for wallet developers on iOS, Android, React Native, and Web. More features coming at Gateway (May 1-2). 👉Read more Tribute Tickets | Gateway | TON Community | TON Builders | TON Hubs |X | YouTube | LinkedIn |TON.org

💎 AppKit — Early Access Now Open A new way to build TON apps. Blockchain complexity fades into the background. You focus on product. 🔗 Apply for the Early Adopter List. *Selected developers will have access to Beta version. Gateway Tickets | Hotel Booking | TON Community | TON Builders | TON Hubs | X | YouTube | Website | Blog | LinkedIn

✈️ We Need Your Feedback on TON Roadmap We’re updating TON strategy and need direct input from active builders. The form is very short — just 3 questions about your real blockers and opportunities. Your answers will directly influence what we fix and prioritize next. 📎 https://walletresearch.typeform.com/to/IwFt5CSL

📚 New TON Documentation is Live We rebuilt the entire documentation from scratch based on community feedback. What's new: ▪️ AI Assistant - Ask questions in plain language and get instant answers from the entire documentation ▪️ Easier Navigation - Flat structure rewritten by blockchain engineers ▪️ Comprehensive Guides - New content for blockchain foundations, TON Connect, mytonctrl, Sandbox, Blueprint, smart contracts, and more ▪️ Dr. Durov's Whitepapers - Now in web format with AI summaries and cross-links Built with feedback from Zengo, RSquad, TonTech, TON API team, TON Core, and shaped and delivered by TON Studio. Try it: docs.ton.org  👉 Read more

🫧 Tolk v1.2: rich bounced messages, cheap deployment, and a breaking change that you'll love Tolk v1.2 is here, aligned with TVM 12 — bringing new assembler instructions that make contracts cheaper and cleaner. This update introduces one breaking change, several powerful new capabilities, and a few quality-of-life improvements across the compiler. ✅ Notable changes in Tolk v1.2: 1. Breaking change: address is now "internal only" 2. Rich bounces: not 256 bits, but the full body on bounce 3. Cheap builder-to-slice, StateInit, and address composition 4. Improved compilation errors 5. Anonymous functions (lambdas) 6. Borrow checker to catch undefined behavior PR on GitHub with detailed info. ✔ `address` is now "internal only" Before: * address meant internal/external/none Now: * address — internal only * address? (nullable) — internal/none, exactly like "maybe address" in @ton/core * any_address — internal/external/none In 99% of contracts only internal addresses are used. External ones are rare, and "none" can be expressed as nullable.

struct Storage {
    // internal, checked automatically
    owner: address
}

With new TVM 12 instructions, addresses are validated automatically during (de)serialization without extra gas — no more manual isInternal() checks. So yes, it's technically a breaking change, but it removes a ton of noise. A short migration guide, as well as technical details, available here. ✔ Rich bounced messages Historically, a bounced message only returned the first 256 bits of the original body. Now TVM 12 supports rich bounces — which lets you obtain the entire body instead.

createMessage({
    bounce: BounceMode.RichBounce,
    ...
})

In onBouncedMessage, you get access to the original body, exit code, gas used, and more. Old true/false bounce flags still work for backward compatibility. Rich bounces simplify complex message flows and inter-contract communication — one of the most painful aspects of TON until now. ✔ Cheap builder-to-slice and address composition Previously, converting a builder to a slice (endCell + beginParse) consumed a lot of gas because cells are expensive. Now there's a new instruction — BTOS (builder-to-slice) — without intermediate cell creation. - b.endCell().beginParse() is now cheap: auto-optimized to BTOS - "builder-to-address" is the same BTOS; hacks around "return a builder with a valid address" can be removed - cheaper StateInit hashing and address calculations Just update to Tolk v1.2 + TVM 12, and you'll immediately save gas. ✔ Anonymous functions (lambdas) Can be used in general-purpose frameworks, perfectly integrated with the type system:

fun customRead(reader: (slice) -> int) { ... }

customRead(fun(s) {
    return s.loadUint(32)
})

✔ Low-level compiler enhancements Also included: better diagnostics with precise ranges, new peephole optimizations, tuple ↔ object conversions, and multiple small fixes. A lightweight borrow checker prevents undefined behavior on concurrent mutations. As always, all additions are carefully described in a PR. 🌳 We've also started improving TVM itself — new assembler instructions are designed specifically to fit the Tolk type system and optimizer. I have always said: the language is just the beginning. Perfect developer experience requires improving every layer of TON's stack. The road may be sharp and curvy — but we're definitely heading in the right direction.

✈️ TEP-526: Scaled UI Standard Adopted for TON The Scaled UI standard has been officially adopted, introducing a unified way for wallets and dApps to display token amounts using a scaling factor — enabling advanced token models such as rebasing and yield accrual, while preserving full on-chain accuracy. This ensures consistent and transparent balance representation across the TON ecosystem. ❤️ Thanks to the community and early adopters — all teams working with jettons are encouraged to implement this standard for consistent user experience. 📎 https://github.com/ton-blockchain/TEPs/blob/master/text/0526-scaled-ui-jettons.md

✈️ Call for Integration: Scaled UI Standard for TON If your product displays or interacts with jettons, you need Scaled UI support. This is especially critical if you plan to integrate xStocks or similar tokenized assets — without this standard, users will see incorrect balances and face confusion. TonAPI and TON Wallet have already started implementing Scaled UI, a key step toward consistent balance rendering across the ecosystem. To all teams working with jettons, please add this to your roadmap to ensure accurate display and seamless user experience. Let’s make an experience consistent, accurate, and ready for the next wave of tokenized products. Thank you for your collaboration! 💪 👥 Projects to highlight: • DEXs: Ston.fi, DeDust, Tonco, Swap.Coffee • Wallets: @wallet, Tonkeeper, MTW • Explorers: Tonviewer, Tonscan.org, Tonscan.com, DYOR • APIs: TON API, Toncenter 🗓 Target ecosystem-wide release: November 15 📎 Reference — https://github.com/the-ton-tech/scaled-ui-jetton

🚀 First beta release of the new TON documentation is now live! 🗺 Jump ahead to beta-docs.ton.org or stay here to learn about the project's backstory, current achievements, and future plans. For quite some time, developers shared the same feedback: TON documentation is too scattered, difficult to navigate, and has obvious gaps and inconsistencies. We at TON Studio took that seriously and initiated the TON Docs Revamp project in late July. It is focused on the following four goals: • To introduce a streamlined, discoverable structure that would be easy to navigate and search • To make documentation welcoming to all developers, from newcomers to seasoned professionals • To introduce and maintain stricter quality checks from humans and AIs to ensure proof-read, up-to-date, consistent, and clear content • And, finally, to set up documentation release pipelines for major TON builders, while making community contributions straightforward and approachable 🏆 Today, with the help and suggestions from various developer teams, including Zengo, RSquad, TonTech, TON API team, and TON Core, the TON Studio is proud to present the first public version of this documentation. It already fulfills the first goal of comprehensive structure and rapidly moves towards achieving the third goal of content. 🦄 That said, this is a beta release: many pages await their contents, some pages require secondary reviews, while infrastructure, pipelines, and processes are only nourishing, not mature yet. All constructive feedback is appreciated. So, what's in store already? We've got: • Flat, easy-to-navigate structure • Hands-on articles with real examples whenever we can provide them • Visuals and diagrams, including various Mermaid diagrams • Smart AI search and summaries • Automatic CI spell checks and AI reviews based on the growing style guide • ...and much, much more! 🏠 TON Docs Revamp features an engaging landing page that guides users through their TON journey, whether they're first exploring TON, building smart contracts, integrating wallets, or just want to access and navigate the documentation quickly. 📝 Re-written or brand new content includes pages for: mytonctrl, mylocalton, development setups with Sandbox and Blueprint (with major help from TonTech), IDEs and SDKs, gas estimation, analytics, oracles, bridges, TMAs, TON Connect, standard wallet contracts, Jettons, NFTs, TVM instructions (with proper search and discovery), TL-B, FunC and other TON-specific programming languages, web versions of whitepapers (with cross-links and solid AI summaries), and even a "Coming from Ethereum" guide! 📈 And this is just the beginning. Plans ahead and for the next month include: - Release pipelines and assignments of relevant technical owners - Docs, infrastructure, and processes for approachable community contributions - More playgrounds, interactive components, and interactivity - Much more content - Stronger AI-based assistance as documentation grows 🎯 The main goals of this beta release are to show preliminary progress, willingness to make things right, and to collect feedback from the developer community before the full release, which is tentatively scheduled for November 17th. We are nothing without the feedback from the community. If something is missing or confusing, let us know by filing a GitHub issue. Furthermore, help review new content whenever you or someone you know is deeply familiar with the topic. TON is vast, and there is always something to know or be aware of. Prominent ecosystem projects are invited to host, co-own, and maintain their documentation with us. Keeping things in one place will enrich the user experience and AI responses. 💪 Let's make the best documentation for TON. Together. → Beta release URL: beta-docs.ton.org → GitHub repository: github.com/ton-org/docs → Future milestones: github.com/ton-org/docs/milestone/3

✈️ New Proposal: Tokenized Vaults Standard for TON The Tokenized Vaults standard, created by the Torch Finance team, introduces a unified interface for vaults on TON, enabling seamless deposits, withdrawals, and balance queries while ensuring compatibility with dApps and protocols across the ecosystem. Adapted from ERC-4626 and tailored for TON’s asynchronous architecture, it provides a consistent foundation for yield strategies, liquidity products, and composable DeFi applications. 💬 We invite developers to review the draft and share feedback before adoption. 📎 https://github.com/ton-blockchain/TEPs/pull/524

✈️ New Proposal: Scaled UI Standard for TON The Scaled UI standard introduces a unified way for wallets and dApps to display token amounts using a scaling factor — enabling advanced token models such as rebasing and yield accrual, while preserving full on-chain accuracy. This ensures consistent and transparent balance representation across the TON ecosystem. 💬 We invite developers to review the draft and share feedback before adoption. 📎 https://github.com/ton-blockchain/TEPs/pull/526

✈ TON Connect Enhancement — Domain Verification 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. 👥 What changed • 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 🗒 What to test • 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 failure causes: CORS issues, manifest not found. 🔨 Examples

👍 Correct: App hosted on: https://myapp.google.com manifest.json: { "url": "https://myapp.google.com", ... } 👎 Incorrect: App hosted on: https://myapp.google.com manifest.json: { "url": "https://anotherdomain.com", ... }

🔗 Specification https://github.com/ton-blockchain/ton-connect/pull/91 💬 Have suggestions on the standard? Please contribute at https://github.com/ton-blockchain/ton-connect/pull/91 ❤ Your feedback helps us improve the TON Connect ecosystem!

🔨 Simplifying code coverage in Blueprint 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

📁 @ton/blueprint v0.41.0 – 2025-09-23 📁 @ton/sandbox v0.37.2 – 2025-09-23 ⬇ To update, run npm install @ton/blueprint@latest @ton/sandbox@latest 💡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!

✈ TON Connect UI 2.3.1 — PLEASE UPDATE This continues our push to improve reliability and success rates across the TON ecosystem. 📁 @tonconnect/sdk v3.3.1 📁 @tonconnect/ui v2.3.1 📁 @tonconnect/ui-react v2.3.1 👥 What changed • 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. 🗒 What to test • 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. ⬇ To update, run npm install @tonconnect/sdk@3.3.1 @tonconnect/ui@2.3.1 @tonconnect/ui-react@2.3.1 🔗 Specification https://github.com/ton-blockchain/ton-connect/blob/main/requests-responses.md#methods 💬 Encountered issues? Please report them on GitHub at https://github.com/ton-connect/sdk/issues. ❤ Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!

✈️ TON Connect UI 2.3.0-beta.3 — BREAKING CHANGE (pre-release) 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. 📁 @tonconnect/sdk v3.3.0-beta.3 📁 @tonconnect/ui v2.3.0-beta.3 📁 @tonconnect/ui-react v2.3.0-beta.3 👥 What changed • 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. 🗒 What to test • 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. 🔗 Specification https://github.com/ton-blockchain/ton-connect/blob/main/requests-responses.md#methods 💬 Encountered issues? Please report them on GitHub at https://github.com/ton-connect/sdk/issues with your payload (redact secrets), error, wallet, and versions. ❤️ Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK!

🔨 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 --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 ⬇ 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!

✈️ TON Devtools x TVM v11 Great news — the latest TON update (v2025.06) brings TVM v11, and TON Devtools is already fully compatible! 📁 TON release notes https://github.com/ton-blockchain/ton/releases/tag/v2025.06 ⬇ Ready to start? Kickstart your next smart contract project with:

npm create ton@latest

Let’s build powerful things on TON ❤

✈️ TON Connect v2.2.0 — Sign Data Support 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. 🛡 New method: signData • Supports text, binary, and cell data types • Enables secure off-chain data signing 📁 New package versions • @tonconnect/protocol 2.3.0 • @tonconnect/sdk 3.3.0 • @tonconnect/ui 2.2.0 • @tonconnect/ui-react 2.2.0 🖌 Example usage

const result = await tonConnectUI.signData({
  type: "text",
  text: "Confirm new 2fa number: +1 234 567 8901"
});

console.log('Signed:', result);

⬇ To update, run npm install @tonconnect/ui-react@latest or npm install @tonconnect/ui@latest 💡 Further reading • SignData request/response specification • SignData documentation 💬 Encountered issues? Please report them on GitHub at https://github.com/ton-connect/sdk/issues. 🎁 Your feedback and usage examples are crucial. Share your experiences to help us evolve the SDK! Special thanks for Tonkeeper Team to helping with this update.

🎉 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! 🛠️✨

🔨 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!