“Trust us” is not an audit.
Provably fair
draw.
A verifiable on-chain draw exposes its randomness record, selection rules and payouts for inspection. This guide explains Pyth Entropy, shows where to check a Ticket4Life distribution, and distinguishes what you can verify from the assumptions and risks that remain.
By Ticket4Life · Revised
The problem with “certified fair”
Traditional lotteries
Off-chain draws can rely on published procedures, oversight and independent checks. What you can inspect depends on the operator's disclosures. A fairness statement and a public record that lets you reproduce a selection are different kinds of evidence; look for the method and its limits, rather than the label.
On-chain draws
An on-chain draw inverts the trust model. The rules are a smart contract anyone can read; the randomness arrives with a cryptographic proof; the payouts are transactions anyone can follow. Fairness stops being a promise and becomes a property you can test — which is exactly what we will do below, on a real Sunday draw.
Where the randomness comes from — Pyth Entropy, in plain language
01 · A provider commits
Pyth's provider commits to a sequence of numbers using a hash chain. A request records another contribution and assigns a sequence number. The provider's value is revealed after the required block confirmations.
02 · The numbers combine
The Entropy contract checks the provider's revealed value against its commitment, combines it with the request contribution, and calls the requesting contract. The protocol still relies on provider behavior and chain assumptions described in Pyth's documentation.
03 · The contract obeys
The final value lands in the callback of the distribution-pool contract (PrizePool), which selects the 13 tickets to be paid and pushes the USDC to their wallets in the same flow. No human touches the selection; the sequence number and random value are recorded on-chain, forever.
Read the Pyth Entropy protocol design and trust assumptions for the full mechanism, including reveal availability and transaction-ordering risks. Verifiable commitments do not make every part of the system trust-free.
Inspect a real draw — four checks, no wallet required
- Step 1 — Open the draw history. Go to ticket4.life/history. Every draw is listed — including the labeled Genesis and Protocol draws from the beta — with its date, distribution total, payouts, and its Pyth proof: a sequence number and the final random number.
- Step 2 — Open the transaction. Each draw links to its transaction on BaseScan, Base's public explorer. You are now looking at the same data every node in the network validated — not our website's copy of it.
- Step 3 — Follow the money. Inspect the USDC token transfers and payout events. The distribution rules allocate 50% / 25% / 10% to the first three tickets and share 15% among up to ten more. Several selected tickets can belong to one wallet, so repeated addresses are possible. Reconcile the transferred amounts with the recorded distribution, allowing for rounding. If a transfer fails, the contract records a claimable amount instead; the payout handbook explains this fallback.
- Step 4 — Check the count is honest. The supply is on-chain too: with the current number of minted tickets public, “13 recipients out of N tickets” is not a marketing claim but an arithmetic fact you can check against the Transparency page.
What provable fairness does not prove — the honest part
Provable fairness proves the draw is honest — it says nothing about whether the product is good. It does not prove the distribution will be large, that the yield engine will perform, or that the contracts are bug-free. It does not make a ticket a safe asset. At Ticket4Life it also coexists with a fact we label rather than hide: during the early beta, the protocol's own tickets are entered too, so the first recipients repeat — each of those draws is still provably fair, and each is labeled on the history page. Verify the fairness; judge the rest with your own eyes.
Content reviewed 27 September 2026 against the sources linked below; third-party products change their terms — always verify on their official pages. This article is information, not financial advice. Ticket4Life involves smart-contract and yield risk: never commit funds you cannot afford to lose. See our Terms and Handbook.
Sources and further reading
Keep reading
Premium Bonds vs Ticket4Life
Compare NS&I Premium Bonds and Ticket4Life: payout funding, ownership, capital protection and exit conditions. Different products with different risks.
Read the article →Yield-Funded Draws
How yield funds distributions, how savings products, vault deposits and NFT tickets differ, and which capital, custody and exit risks remain.
Read the article →See it run, don't take our word.
Ticket4Life is live on Base: every draw and every payout is verifiable on-chain, and the treasury is published on the Transparency page. Start with the draw history, or mint a lifetime ticket in five minutes — even without a wallet.
Not financial advice. Ticket4Life involves smart-contract and yield risk — never commit funds you cannot afford to lose. Participation may be restricted in your jurisdiction.