fix: convert TON WalletConnect sendMessage params to spec-compliant format - #5567
Merged
Conversation
…ormat The TonWalletConnectConnector was passing sendMessage params through without converting field names to the snake_case format required by the WalletConnect TON JSON-RPC spec. This caused wallets to fail with "Messages are absent" because: 1. Field names were camelCase (validUntil, extraCurrency) instead of snake_case (valid_until, extra_currency) as required by the spec 2. Params were wrapped in an array, but the sample wallet's approveTonRequest handler passes request.params directly to sendMessage without unwrapping — unlike signData which correctly unwraps with request.params[0] Changes: - Convert validUntil to valid_until with a default 60s expiry - Convert extraCurrency to extra_currency in message objects - Ensure amount is always a string (wallets validate typeof) - Send params as a plain object instead of array for compatibility The injected wallet connector (TonConnectConnector) already handled this conversion correctly. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
9 Skipped Deployments
|
|
0xmkh
approved these changes
Feb 27, 2026
Contributor
Visual Regression Test Results ✅ PassedChromatic Build: https://www.chromatic.com/build?appId=6493191bf4b10fed8ca7353f&number=795 👉 Please review the visual changes in Chromatic and accept or reject them. |
Contributor
📦 Bundle Size Check✅ All bundles are within size limits 📊 View detailed bundle sizes> @reown/appkit-monorepo@1.7.1 size /home/runner/work/appkit/appkit > size-limit |
Contributor
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Fix TON
sendMessagevia WalletConnect failing withTonValidationError: Messages are absenton the wallet side.The
TonWalletConnectConnectorwas passingsendMessageparams through to the WalletConnect provider without converting field names to the snake_case format required by the WalletConnect TON JSON-RPC spec. This caused wallets (including the WalletConnect sample wallet) to fail validation because:validUntil/extraCurrency(camelCase) instead ofvalid_until/extra_currency(snake_case)[{...}]but the sample wallet'sapproveTonRequestpassesrequest.paramsdirectly towallet.sendMessage()without unwrapping — unlikesignDatawhich correctly usesrequest.params[0]The injected wallet connector (
TonConnectConnector) already handled this conversion correctly.Changes:
validUntil→valid_until(with default 60s expiry)extraCurrency→extra_currencyin message objectsamountis always a string (wallets validatetypeof)Type of change
Checklist
Note
Medium Risk
Touches TON transaction submission over WalletConnect by changing the JSON-RPC
ton_sendMessagepayload shape/field names; could affect wallet compatibility if any clients relied on the previous (incorrect) format.Overview
Fixes TON WalletConnect
sendMessagerequest formatting to match the WalletConnect TON JSON-RPC spec.TonWalletConnectConnector.sendMessagenow normalizes message fields (stringifiesamount, mapsextraCurrencytoextra_currency, and builds amessagesarray) and sendston_sendMessageparamsas a plain object withvalid_until(defaulting to now+60s) instead of wrapping the params in an array.Written by Cursor Bugbot for commit d2d1433. This will update automatically on new commits. Configure here.