Skip to content

docs: add TON RPC reference documentation #663

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

docs: add TON RPC reference documentation #663

wants to merge 4 commits into from

Conversation

@devin-ai-integration
Copy link
Contributor

@devin-ai-integration devin-ai-integration bot commented Oct 16, 2025 •
edited
Loading

Description

This PR adds technical clarification to the TON RPC documentation's ton_sendMessage success response section. Based on user feedback, the documentation now includes:

  1. Disclaimer note: Added a <Note> component explaining that the base64bocEncodedTransaction result is a base64 encoded BOC (Bag of Cells) of an external message.

  2. Code example: Added a TypeScript code snippet demonstrating how to build an external-in message, which is what the response represents. This helps developers understand the structure and how to construct similar messages.

The changes are focused on improving developer understanding of the response format for the ton_sendMessage RPC method.

Tests

  • Ran spell check successfully (pnpm run spell) - 0 issues found
  • Ran the changes locally with Mintlify and confirmed that the changes appear as expected
  • Ran a grammar check on the updated/created content using ChatGPT

Important Review Items

⚠️ Code Example Accuracy: The TypeScript example was provided by the user but should be verified for:

  • Correct TON SDK types and method signatures (Message, Address.parse(), beginCell(), etc.)
  • The transfer variable is referenced but not defined in the snippet - this may be intentional to show where transaction data goes, but please verify this is clear enough

⚠️ Documentation Formatting: Verify the <Note> component renders correctly in the deployed preview and is the appropriate way to add technical notes in the RPC reference section.

Direct link to the deployed preview files

Devin Session: https://app.devin.ai/sessions/8f2bbd850e994568be56475deb6eb995
Requested by: [email protected] (@ganchoradkov)

@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@github-actions
Copy link

@devin-ai-integration[bot] Please review the tone of voice for the content changes in this PR against Reown's brand guidelines.

📝 Content Review Request

Files to review: 1

  • advanced/multichain/rpc-reference/ton-rpc.mdx

Review focus:

  • Tone alignment with Reown's brand guidelines
  • Clear and accessible language for developers
  • Professional yet approachable communication
  • Consistent terminology usage

Guidelines summary:

  • Clear & Accessible: Translate complex ideas into approachable language
  • Professional yet Friendly: Maintain authority while being welcoming
  • Developer-Focused: Understand technical audience but remain inclusive
  • Avoid: Overly casual language, fear-based messaging, buzzwords, jargon without explanation
  • Embrace: Clear explanations, confident tone, transparency, respectful communication

Please analyze the content changes and provide constructive feedback on tone and voice alignment.

@devin-ai-integration @riveign
docs: update TON RPC with official WalletConnect methods
a4adada 
- Replace placeholder methods with official ton_sendMessage and ton_signData
- Add network/chain information table with CAIP-2 chain IDs
- Include WalletConnect RPC proxy endpoint configuration
- Update request/response formats to match official specification
- Add detailed type definitions for all parameters
- Include notes on wallet implementation requirements

Co-Authored-By: [email protected] <[email protected]>
@github-actions
Copy link

@devin-ai-integration[bot] Please review the tone of voice for the content changes in this PR against Reown's brand guidelines.

📝 Content Review Request

Files to review: 1

  • advanced/multichain/rpc-reference/ton-rpc.mdx

Review focus:

  • Tone alignment with Reown's brand guidelines
  • Clear and accessible language for developers
  • Professional yet approachable communication
  • Consistent terminology usage

Guidelines summary:

  • Clear & Accessible: Translate complex ideas into approachable language
  • Professional yet Friendly: Maintain authority while being welcoming
  • Developer-Focused: Understand technical audience but remain inclusive
  • Avoid: Overly casual language, fear-based messaging, buzzwords, jargon without explanation
  • Embrace: Clear explanations, confident tone, transparency, respectful communication

Please analyze the content changes and provide constructive feedback on tone and voice alignment.

@devin-ai-integration @riveign
docs: simplify TON network table header and remove WalletConnect RPC …
a97aa96 
…proxy

- Change table header from 'CAIP-2 / CAIP-25 Chain ID' to just 'CAIP-2'
- Remove WalletConnect RPC proxy endpoint section

Co-Authored-By: [email protected] <[email protected]>
@github-actions
Copy link

@devin-ai-integration[bot] Please review the tone of voice for the content changes in this PR against Reown's brand guidelines.

📝 Content Review Request

Files to review: 1

  • advanced/multichain/rpc-reference/ton-rpc.mdx

Review focus:

  • Tone alignment with Reown's brand guidelines
  • Clear and accessible language for developers
  • Professional yet approachable communication
  • Consistent terminology usage

Guidelines summary:

  • Clear & Accessible: Translate complex ideas into approachable language
  • Professional yet Friendly: Maintain authority while being welcoming
  • Developer-Focused: Understand technical audience but remain inclusive
  • Avoid: Overly casual language, fear-based messaging, buzzwords, jargon without explanation
  • Embrace: Clear explanations, confident tone, transparency, respectful communication

Please analyze the content changes and provide constructive feedback on tone and voice alignment.

@github-actions
Copy link

@devin-ai-integration[bot] Please review the tone of voice for the content changes in this PR against Reown's brand guidelines.

📝 Content Review Request

Files to review: 1

  • advanced/multichain/rpc-reference/ton-rpc.mdx

Review focus:

  • Tone alignment with Reown's brand guidelines
  • Clear and accessible language for developers
  • Professional yet approachable communication
  • Consistent terminology usage

Guidelines summary:

  • Clear & Accessible: Translate complex ideas into approachable language
  • Professional yet Friendly: Maintain authority while being welcoming
  • Developer-Focused: Understand technical audience but remain inclusive
  • Avoid: Overly casual language, fear-based messaging, buzzwords, jargon without explanation
  • Embrace: Clear explanations, confident tone, transparency, respectful communication

Please analyze the content changes and provide constructive feedback on tone and voice alignment.

@bkrem bkrem requested a review from ganchoradkov October 24, 2025 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ganchoradkov ganchoradkov Awaiting requested review from ganchoradkov

At least 1 approving review is required to merge this pull request.

Assignees

@ganchoradkov ganchoradkov

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ganchoradkov