TON Tecnología - TON tecnología

✈️ 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. 📎 Ссылка скрыта

✈️ 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. 📎 Ссылка скрыта

✈ 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 issues: CORS issues, manifest not found. 🔨 Examples 👍 Correct: App hosted on: Ссылка скрыта manifest.json: { "url": "Ссылка скрыта ... } 👎 Incorrect: App hosted on: Ссылка скрыта manifest.json: { "url": "Ссылка скрыта ... } 🔗 Specification Ссылка скрыта 💬 Have suggestions on the standard? Please contribute at Ссылка скрыта ❤ 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: Ссылка скрыта 💬 Encountered issues? Please report them on GitHub at Ссылка скрыта 🎁 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 Ссылка скрыта for improved reliability • Updated fallback wallets list to match Ссылка скрыта • 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/[email protected] @tonconnect/[email protected] @tonconnect/[email protected] 🔗 Specification Ссылка скрыта 💬 Encountered issues? Please report them on GitHub at Ссылка скрыта ❤ 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 Ссылка скрыта 💬 Encountered issues? Please report them on GitHub at Ссылка скрыта 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: Ссылка скрыта and Ссылка скрыта 💬 Encountered issues? Please report them on GitHub at Ссылка скрыта 🎁 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 Ссылка скрыта ⬇ 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 Ссылка скрыта 🎁 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.