Glossary
Terms that show up across the OMY documentation. If something here contradicts what you read in a specific page, the specific page wins — flag the conflict by opening a GitHub issue.
A
Assertion — One yes/no claim about the world, materialized as an immutable contract on TON. Spawned by the OracleFactory; progresses through a five-state lifecycle.
Asserter — Anyone who calls propose() on an open assertion, posting a
USDT bond. Synonymous with "proposer".
Arbitration window — The time after a dispute during which the
resolver must settle. Default 7 days. If exceeded, anyone can call
TimeoutRefund to recover both bonds.
At-least-once delivery — Property of OracleResult: may be delivered
more than once. Consumers must dedupe by questionId. The most common
integration bug is forgetting this.
B
Bond — Refundable collateral the proposer and disputer lock at proposal/dispute time. The mechanism that makes lying expensive. Always refunded if you're right; partially or fully lost if you're wrong.
Bond clamp — Pattern of sizing the bond proportionally to TVL, floored
and capped. Default: 2% of total collateral, floor at configured oracleBond,
cap at MAX_BOND_CAP = 10 000 USDT.
C
Callback recipient — The address OMY notifies when an assertion finalizes. Set in the Meta cell at creation; usually the consumer contract that asked the question.
Cancelled — Terminal status of an assertion after TimeoutRefund fires.
Both bonds are refunded; consumer is not notified with a final answer.
Commit-reveal — Two-window voting scheme used in Phase 2 DVM. Voters commit a hashed vote in window 1, reveal the plaintext in window 2.
Committee — Phase 1 resolver. M-of-N trusted multisig that settles disputes. Replaced by DVM in Phase 2 (but stays available for consumers that explicitly bound it).
Consumer — A contract that asks OMY questions and reacts to
OracleResult. Examples: prediction market, bridge, parametric insurance,
RWA escrow.
D
Dedupe — Pattern of rejecting OracleResult messages with a questionId
the consumer has already processed. Mandatory because of
at-least-once delivery.
Disputer — Anyone who challenges a proposed answer by posting a matching bond. In production, often watcher bots scanning for misstated answers.
DVM — Data Verification Mechanism. Phase 2 resolver: stake-weighted
commit-reveal voting in $OMY. See Governance → DVM.
F
Factory — Short for OracleFactory, the single deployer of new assertions.
Final fee — Non-refundable fee skimmed from the proposer's bond at propose time. Phase A: 2 USDT. Routes to treasury.
Finalize — The state transition from Proposed to Resolved when the
liveness window elapses without dispute. Permissionless — anyone can pay
gas to call it.
I
Identifier — A uint256 field in the Meta cell that tags
assertions by category (price feed type, event class, RWA milestone class).
Off-chain indexers filter by it.
J
Jetton — TON's fungible-token standard (TEP-74). OMY bonds are paid in the jetton bound at factory deploy (USDT).
L
Liveness — The challenge window length, set at assertion creation. If no
one disputes within liveness seconds, the proposed answer is accepted.
Lifecycle — The five-state machine of an assertion: Open → Proposed → {Resolved, Disputed} → {Resolved, Cancelled}. See
Concepts → Lifecycle.
M
Meta — Reference cell carried by every assertion. Holds the identifier, fact timestamp, callback recipient, and question text.
Monetization snapshot — The protocolFee + treasuryAddress pair stored in
each assertion's Config at deploy time. Once set, immutable for that
assertion. Factory governance can change values for future assertions only.
O
$OMY — OMY's governance and staking token. Phase 2 only. Stake to
vote in the DVM; earn 50% of all protocol fees pro-rata. Launches once
traction metrics are met (why).
OracleFactory — Single contract that deploys new assertions, binds their
bond jetton wallets via TEP-89, and emits AssertionCreated.
OracleResult — The cross-contract message the assertion sends to its
callback recipient at resolution. Payload: {questionId, answer: bool}.
OracleDisputed — The cross-contract message the assertion sends to its
callback recipient when it enters Disputed status. Lets consumers pause
business logic until final resolution.
Optimistic oracle — Oracle model where claims are accepted by default unless challenged within a window. Cheap in the common case, expensive only on disputes. See Protocol overview → Two models.
P
Phase A — Pre-token-launch operations. USDT fees route to multisig
treasury. Committee resolver. No $OMY.
Phase B — Post-token-launch. $OMY exists and is staked into the DVM.
50% of fees route to stakers. Committee stays available for backward
compatibility.
Phase C — Post-mainnet, post-token. Yield-on-reserves layer:
TreasuryVault sweeps idle USDT into TON DeFi (whitelisted protocols) and
optionally buys back $OMY from the yield.
Propose — Action of claiming an answer + posting a bond. The first state-changing transition in an assertion's lifecycle.
Protocol fee — Synonym for final fee. The Phase A target is 2 USDT.
Q
Quorum (GAT) — In Phase 2 DVM, the minimum total revealed stake required
for a tally to count. Below quorum, the case reopens. Snapshot at case open
from (circulating $OMY × gatBps), capped to a floor.
R
Reemit — Permissionless action: anyone can pay gas to make a resolved
assertion re-fire its OracleResult callback. Covers the case where the
first delivery dropped (bounce, gas exhaustion). Why consumers must dedupe.
Resolver — The contract that settles disputed assertions. Phase 1:
CommitteeResolver (M-of-N multisig). Phase 2: StakeVoteResolver (DVM).
Resolution fee — Silent 1% skim from the market's collateral pool at the moment of resolution. Reduces per-share payout from $1.00 to $0.99. Routes to treasury.
S
SPAT — Supermajority Persistence Approval Threshold. Phase 2 DVM constant: the winning side must reach ≥65% of revealed stake (not just a simple majority) for the case to resolve.
Schelling point — The "obvious" answer that rational voters converge on because they expect every other voter to do the same. The conceptual basis of stake-weighted voting in the DVM.
Slash — Stake loss for voting on the losing side (or for committing without revealing) in the DVM. Funds the rewards for winners.
Stake — Locked $OMY in the DVM. Earns rewards from disputes that
resolve in the staker's favor; slashed when wrong.
T
TEP-74 — TON's fungible-token (jetton) standard. Bonds and AMM trading flow through it.
TEP-89 — TON's wallet-discovery extension. The factory asks the jetton master for a contract's wallet address. Production-correct for any jetton, including real USDT.
TimeoutRefund — Permissionless escape from a stuck disputed assertion. After the arbitration window elapses without resolution, anyone can call it; both bonds refund, status moves to Cancelled.
OMY — The protocol (and the umbrella brand). Optimistic oracle for TON, built in Tolk.
Treasury — The address that receives fee inflows. Phase A: a founder
multisig. Phase B: the RewardsDistributor contract that streams 50% to
staked $OMY holders, 50% to a smaller protocol treasury.
U
Underfunded — Status of an intake where the sender attached less than
bondAmount + protocolFee. The assertion refunds the input and does NOT
throw. Stays in Open.
See also
- Concepts — the mental model
- Architecture — the contract topology
- SDK Reference — every opcode and constant