Skip to content

docs: clarify TON signData support boundaries#783

Draft
cursor[bot] wants to merge 1 commit into
onekeyfrom
cursor/documentation-automation-system-e7ff
Draft

docs: clarify TON signData support boundaries#783
cursor[bot] wants to merge 1 commit into
onekeyfrom
cursor/documentation-automation-system-e7ff

Conversation

@cursor
Copy link
Copy Markdown

@cursor cursor Bot commented May 11, 2026

Summary

  • document the new tonSignData TON Connect flow in docs/chain.md
  • clarify in docs/device-method-support.md that the device compatibility matrix only reflects declared overrides
  • note that tonSignData is wired in SDK and playground examples but is not yet part of the verified device compatibility matrix

Codepaths covered

  • packages/core/src/api/ton/TonSignData.ts
  • packages/core/src/types/api/tonSignData.ts
  • packages/hd-transport/src/types/messages.ts
  • packages/connect-examples/expo-example/src/data/ton.ts
  • packages/connect-examples/expo-example/src/testTools/deviceCompatibility/plugins/*.ts

Gaps addressed

  • missing public interface docs for tonSignData
  • unclear support boundary between SDK wiring and device-level compatibility verification
Open in Web View Automation 

Co-authored-by: Leon <lixiao.dev@gmail.com>
@revan-zhang
Copy link
Copy Markdown
Contributor

revan-zhang commented May 11, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants