TonTech – Telegram
TonTech
29.5K subscribers
23 photos
3 videos
1 file
112 links
TON Dev community
Download Telegram
🔨 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!
Please open Telegram to view this post
VIEW IN TELEGRAM
10👍6🏆3
✈️ 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!
Please open Telegram to view this post
VIEW IN TELEGRAM
16❤‍🔥1
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!
Please open Telegram to view this post
VIEW IN TELEGRAM
❤‍🔥4💘31👌1
🔨 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!
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥9❤‍🔥3🌚3
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.jsonurl 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 issues: CORS issues, manifest not found.

🔨 Examples
👍 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", ... }


🔗 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!
Please open Telegram to view this post
VIEW IN TELEGRAM
👍8💘3🔥2
✈️ 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
Please open Telegram to view this post
VIEW IN TELEGRAM
👍20❤‍🔥5
✈️ 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
Please open Telegram to view this post
VIEW IN TELEGRAM
9👍5
Forwarded from TON Dev News
🚀 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
🔥106
✈️ 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, dTon

🗓 Target ecosystem-wide release: November 15

📎 Reference — https://github.com/the-ton-tech/scaled-ui-jetton

📎 Specification — https://github.com/the-ton-tech/TEPs/blob/scaled-ui/text/0000-scaled-ui-jettons.md
Please open Telegram to view this post
VIEW IN TELEGRAM
🏆3
✈️ 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
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥11👎1🤬1
Forwarded from TOLK lang
🫧 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.
🔥6
Forwarded from Toncoin
📚 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
❤‍🔥9🏆6💘51🙏1🦄1
✈️ We Need Your Feedback on TON

TON teams across the ecosystem are refreshing the strategy, and builders’ input is a key part of that process.

This is a short 3-question form about real blockers and opportunities you see.

Your feedback may help inform the discussions and priorities across the ecosystem.

📎 https://walletresearch.typeform.com/to/IwFt5CSL
Please open Telegram to view this post
VIEW IN TELEGRAM
😁15👎10😨10🤣3❤‍🔥2👍2😍2🤬1🕊1