Four questions to ask of the rules
What exactly must happen? Which source counts as confirmation? When does the observation period end? How are exceptions handled? Write down the answers and compare them with the original. Signing a document and announcing an intention to sign are different conditions. Do not expand a short phrase into whichever meaning feels natural.
Confirmation mechanisms differ
The documentation distinguishes UMA-resolved markets from short Up/Down markets using Chainlink TWAP. One mechanism should not automatically be assigned to the other. A reader needs the selected contract’s mechanism and evidence of its result. Seeing an oracle name is not itself confirmation that a particular outcome has been settled.
Three dates with different meanings
The event date, contract deadline and confirmation time can differ. Trading closure or a passed deadline does not prove resolution. An unknown confirmation time must remain unknown. An archive should preserve the state at capture time, source and history so a later explanation does not overwrite what was actually observed earlier.
Translation supports interpretation
OddsAtlas explanations in Russian and English are linked to a version of the source question and rules. A source clarification requires another review. If wording differs, return to the original rather than choosing a convenient translation as an alternative condition. Timing, price boundaries, cancellations and disputed situations particularly require this care.
Compare versions by their contents, not just fetch dates. A new price snapshot may preserve the same unchanged conditions.
FAQ /
Common questions
Can YES be assigned automatically after a deadline?
No. The condition must be met and the result explicitly confirmed. Passing a date does not answer the contract question.
Can closed be treated as the same as resolved?
No. Closure and resolution are distinct states. Display the reported status and confirmed outcomes separately instead of inventing a missing result.