How it works

Reading public data

When you look up an address, the browser asks a public TON indexer for it and renders the answer. The only thing sent is the address or hash you searched for. No wallet is involved, and nothing is stored on a server on your behalf.

Signing a transfer

1. Your phrase is decrypted in this browser after you enter the password.
2. The message is built and signed locally.
3. Before you confirm, the signed bytes are sent to an emulator that replays them against current chain state, and the result is shown: what leaves the wallet, what arrives, the fee, and any flag on the counterparty.
4. Only if you confirm are the same bytes broadcast to the network.

The phrase itself is never transmitted — not to this site, not to an indexer, not to Telegram. What travels is a signed message, which is what the network needs.

Broadcast is not success

A message can be accepted by a node and still fail on chain. The app separates the stages — signed, broadcast, confirmed, executed — and does not report success until the network has confirmed it. When the result is unknown, it says so and gives you the identifier to check, rather than inviting you to send again.

Networks

Every object link names its network explicitly. Mainnet and testnet data are never mixed, and an unknown network in a URL is an error rather than a silent default.