DApps

Private Payment

Send TON with privacy built into the payment flow. Private Payment turns transfers into proof-backed channel activity, giving users a cleaner way to move value and giving builders a payment rail made for private Ethereum applications.

TONPrivate stateTransferPayment
Open observer

Start with a private transfer.

The Tonigma airdrop campaign has ended, so this is not a reward submission guide. Use this flow to set up the local runtime, join the Tonigma channel, and make a real Private Payment transfer.

Work with a local agent

Ask a local AI agent to walk you through the terminal steps. It should explain each command, stop before spending gas or TON, and never ask you to paste secrets into chat.

Install the runtime

Install or update @tokamak-private-dapps/private-state-cli, run the CLI install step, then confirm the CLI version and help output before continuing.

Configure mainnet RPC

Configure an Ethereum mainnet RPC URL. Ankr was recommended in the original Tonigma guide because channel and wallet recovery can be slow on many free RPC providers.

Create a private transfer

Use a funded burner account, join the Tonigma private channel, create or recover a local wallet workspace, and make one real transfer notes transaction.

Verify the hash

Save the Ethereum transaction hash for the transfer notes transaction only. Do not confuse it with a join, deposit, approval, import, or setup transaction.

Prompt your local agent

Private Payment setup is easiest when a local AI agent can run or explain terminal commands on your machine. Start with this prompt and keep all secrets local.

I want to start using Private Payment on Tonigma. Please act as my careful local technical assistant.

Rules:
- Do not ask me to paste seed phrases, private keys, RPC API keys, or recovery secrets into chat.
- Explain each command before I run it.
- Stop before any transaction that spends ETH gas or TON and ask for my explicit confirmation.
- If a command is uncertain, inspect private-state-cli --help instead of guessing.

Goal:
Guide me until I have created one real Private Payment transfer notes transaction on Tonigma and can identify the Ethereum transaction hash for that transfer.

Install the CLI

Ask your agent to install the latest CLI, install runtime artifacts, and inspect the current help output before it proceeds.

  1. npm install -g @tokamak-private-dapps/private-state-cli@latest
  2. private-state-cli install
  3. private-state-cli --help

Safety checklist

  • Never paste a seed phrase, private key, RPC API key, or recovery secret into chat.
  • Use a burner MetaMask account instead of a main wallet unless you intentionally choose otherwise.
  • If a private key is needed, store it only in a restricted local file and use the CLI's documented file-based option.
  • Before broadcasting any transaction, confirm the network, channel, sender, recipient, estimated gas, and TON effects.
  • Use exact or minimal token approvals where possible; do not approve unlimited allowance without a clear reason.

What your agent should do

  1. Check whether Node.js and npm are installed.
  2. Install or update the private-state CLI and runtime artifacts.
  3. Configure an Ethereum mainnet RPC URL without exposing API keys in chat.
  4. Prepare a funded burner account with enough ETH for gas and enough TON for channel use.
  5. Check whether the account is already joined to the Tonigma channel before creating a new join transaction.
  6. Create or recover the local Private Payment wallet workspace.
  7. Prepare one small transfer notes transaction and wait for explicit confirmation before broadcasting.
  8. After success, identify the 66-character Ethereum transaction hash for the transfer notes transaction.
  9. Confirm the hash is not from a join, deposit, approval, import, or setup transaction.