How do I install the Ton Proof skill?

Run npx skillmds@latest add ton-org/ton-proof in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ton Proof safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ton Proof?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ton Proof free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ton Proof?

ton-org (@ton-org) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ton Proof by ton-org — Agent Skill

Name: Ton Proof
Author: ton-org

Ton Proof

Generate TonConnect TonProof signatures for third-party authentication. Use when the user wants to log in with a TON wallet, prove wallet ownership, authenticate to an API such as GetGems, or generate a TonProof for a domain and challenge payload.

ton-org 740a01a 2.1 KB Updated Sep 17, 2026

File contents

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 domain and payload from 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_proof with 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 format
chain: TON Connect chain id (-239 for mainnet, -3 for testnet)
walletStateInit: wallet state init in base64
publicKey: wallet public key
timestamp: Unix timestamp used in the proof
domainLengthBytes and domainValue: signed domain metadata
signature: base64 TonProof signature
payload: 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 walletSelector instead of changing the active wallet for a one-off proof
If no wallet is configured, use the ton-create-wallet skill first

---name: ton-proofdescription: Generate TonConnect TonProof signatures for third-party authentication. Use when the user wants to log in with a TON wallet, prove wallet ownership, authenticate to an API such as GetGems, or generate a TonProof for a domain and challenge payload.---# TON Proof AuthenticationGenerate 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` |## Workflow1. Get the exact `domain` and `payload` from the user or the verifying service2. Do not edit, normalize, decode, or invent the payload; it is part of the signed proof3. Ask one short yes/no confirmation before sending; If there are tools for dialogs/confirmation available, use them instead of a free-text prompt.4. Call `generate_ton_proof` with the domain and payload5. Return the proof JSON to the user, or submit it to the service only when the user explicitly asked for that integration step## OutputThe proof includes:- `address`: active wallet address in raw format- `chain`: TON Connect chain id (`-239` for mainnet, `-3` for testnet)- `walletStateInit`: wallet state init in base64- `publicKey`: wallet public key- `timestamp`: Unix timestamp used in the proof- `domainLengthBytes` and `domainValue`: signed domain metadata- `signature`: base64 TonProof signature- `payload`: 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 `walletSelector` instead of changing the active wallet for a one-off proof- If no wallet is configured, use the `ton-create-wallet` skill first

Frequently asked questions