使用方法
- 复制安装命令,在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/ton-org/kit --skill ton-proof开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。
TON Proof Authentication
Generate a signed TonConnect proof-of-ownership payload for a domain and challenge string. This proves control of the active wallet without sending a transaction.
MCP Tools
| Tool | Required | Optional |
|---|---|---|
generate_ton_proof | domain, payload | walletSelector |
get_wallet | — | walletSelector |
Workflow
- Get the exact
domainandpayloadfrom the user or the verifying service - Do not edit, normalize, decode, or invent the payload; it is part of the signed proof
- Ask one short yes/no confirmation before sending; If there are tools for dialogs/confirmation available, use them instead of a free-text prompt.
- Call
generate_ton_proofwith the domain and payload - Return the proof JSON to the user, or submit it to the service only when the user explicitly asked for that integration step
Output
The proof includes:
address: active wallet address in raw formatchain: TON Connect chain id (-239for mainnet,-3for testnet)walletStateInit: wallet state init in base64publicKey: wallet public keytimestamp: Unix timestamp used in the proofdomainLengthBytesanddomainValue: signed domain metadatasignature: base64 TonProof signaturepayload: original challenge payload
Notes
- TonProof is for authentication and proof of wallet ownership; it does not transfer funds
- TonProof still requires signing access. Imported read-only agentic wallets need operator key rotation completed before this tool can generate a proof
- Only generate a proof for domains and payloads the user intentionally provided or that came directly from the verifying service
- If multiple wallets are configured, pass
walletSelectorinstead of changing the active wallet for a one-off proof - If no wallet is configured, use the
ton-create-walletskill first

