✈️ 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!
Post #137
2.72K
- ❤ 16
- ❤🔥 1