Draw Lifecycle
DraftStatus: Draft Version: 0.1.0 Last Updated: 2026-05-16 Owner: Axodus Lottery / CryptoDraw
Purpose
A draw must follow a deterministic lifecycle so users, operators, governance, and reviewers understand when entries open, close, randomness is requested, results are final, claims open, and claims expire.
Draw Round Object
Fields may include draw_id, game model, game model version, status, ticket open and close times, randomness request and fulfillment times, result publication time, claim window, ticket count, ticket root if any, randomness source, result, prize pool, fee policy, governance reference, and report reference.
Status Model
Statuses may include Draft, Scheduled, Open, Closing, Closed, Indexing, Randomness Requested, Randomness Fulfilled, Result Computed, Result Published, Claims Open, Claims Closed, Finalized, Cancelled, Disputed, and Paused.
Lifecycle Flow
- Governance or an authorized operator creates the draw configuration.
- The draw is scheduled and the ticket window opens.
- Users create valid tickets under the active game rules.
- The ticket window closes and the ticket set is finalized.
- A ticket root is generated if indexing is used.
- Randomness is requested and fulfilled.
- Results are computed from randomness and game rules.
- Results are published and winners are calculated.
- The claim window opens.
- Claims are processed, unclaimed prizes follow policy, and the draw report is published.
Cancellation and Refunds
Cancellation may occur due to unresolved randomness failure, security issue, compliance or governance pause, operational incident, integrity issue, or policy-defined draw conditions. Refund policy must define payment asset, network costs, free-entry handling, and reporting.