Matches orders and proposes a result. It cannot move a user's Vault funds anywhere except a validated EventPool deal.
Read a TonFair deal directly on TON.
A simple match becomes a branching blockchain trace: two Vaults fund escrow, the result is proposed, a challenge window runs, and settlement pays the winner. This guide shows what every line means.
Five screens, one complete lifecycle
These are unmodified dark-theme Tonviewer captures. The explanations are separate HTML overlays, so the source remains readable and every step links back to the explorer.
Who does what?
A user's non-custodial contract. It funds matched deals, receives payouts, and sends balance notifications to the scanner.
Escrow and settlement logic for an event. It validates both deposits, stores the result state, and pays according to code.
| Opcode | Name | What to look for in Tonviewer |
|---|---|---|
| 0x105 | DepositForDeal | Each Vault sends its exact side of the matched deal to EventPool. |
| 0x110 | DealFunded | The second valid deposit changes the deal from FUNDING to FUNDED. |
| 0x600 | ProposeResult | The proposed outcome is stored and the challenge window begins. |
| 0x601 | Challenge | A funded participant disputes during the allowed window. |
| 0x602 | OracleResolve | The independent oracle posts its final result after a challenge. |
| 0x700 | Settle | Permissionless payout or emergency refund, depending on contract state. |
| 0x603 | Vault balance notice | A payout reached the winner's Vault; the scanner is told to refresh its balance. |
Analyze an address or transaction
Data is fetched read-only from TonAPI in your browser. Known TonFair opcodes are labelled; unknown operations stay explicitly unclassified.
This viewer is educational and read-only. TonAPI data is not used by TonFair contracts for funding, challenges, or settlement. Always verify critical details in Tonviewer and the open-source contracts.