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!