How to verify a user draw on the blockchain

1. Open the user draw in ElyxS and confirm its network and draw number.
2. Select Verify draw. Viewing the report does not require a wallet transaction.
3. Wait until both the browser calculation and the direct network comparison finish.
4. Read the report summary before opening individual stages.
5. Expand each applicable stage to compare recorded and calculated values.
6. Use the report's current SupraScan links when you need the source transaction.
7. Treat missing evidence as incomplete verification, not as a successful check.

Do not use a contract address, network, or explorer link copied from an old document. Open the current draw in ElyxS so the report uses its recorded network and contract.

The summary separates the browser calculation from the direct network comparison:

• Result confirmed means every applicable calculation passed and the required transactions and events matched data read directly from Supra RPC, the public network interface used by the report.
• A mismatch was found means at least one calculated value, transaction, or event did not match its source evidence.
• The result could not be fully verified means a required source value is missing.
• Network verification is incomplete means the browser repeated the calculations, but the report could not obtain the source transactions directly from Supra RPC.
• Not all data can be checked against the network means the result transactions matched, but another required record was unavailable.

An incomplete report is not proof of manipulation. It means the available evidence is not sufficient for the stronger conclusion.

The first stage compares the terms recorded when the draw was created with the current contract snapshot. For user-created draws, the browser also recalculates the relevant JSON and BCS hashes.

The report can confirm those terms directly against the network only when the creation record includes a usable source transaction.

If that source is absent, matching browser calculations do not turn the description and rules into independently verified blockchain evidence. The report marks this limitation instead of reporting full confirmation.

The report rebuilds the ticket set used when randomness was requested and compares its hash with the recorded request data. This is the participation snapshot used for the result.

The separate participant list is built from indexed purchases and can change while sales remain open. Do not use the current list by itself as proof of the final ticket snapshot.

Supra dVRF provides verifiable randomness. The report checks that the request and response belong to the selected draw and round, that their identifiers and random bytes match, and that the response was accepted by the contract.

This verifies the relationship between the request, response, and recorded result. It does not by itself verify the prize description, prize delivery, or every rule outside the displayed checks.

The browser applies the same recorded selection method to the random bytes and frozen ticket snapshot. It then compares the calculated winning ticket number and wallet address with the contract record.

If the complete ticket snapshot is unavailable, the winner can be recorded in the contract while independent recalculation remains incomplete.

Follow the report status rather than treating the recorded address alone as full verification.

For a prize held by the contract, use the draw and prize pages to check whether the winner can receive it.

For an organizer-provided prize, the report can verify the published terms and winner when evidence is available. It cannot verify the prize's existence, condition, or external delivery.

Prize receipt, organizer prize return, and participant refunds are separate asset actions. See Prizes in user draws and Claim a prize or refund for those workflows.

When source data is available, the report lets you download a portable evidence file. It contains the values needed to reproduce the calculations and does not require a wallet or private keys.

Reproducing a calculation from the downloaded file proves that the file is internally consistent with that calculation.

It does not independently prove that every value came from the network. Direct transaction and event comparison remains a separate part of the live report.

1. Confirm that the report shows the intended network and draw number.
2. Refresh the report once to rule out an incomplete data update.
3. Open the source transaction through the report's current SupraScan link.
4. Do not repeat a purchase, prize receipt, or refund while its original transaction remains uncertain.
5. If the mismatch remains, contact Support with the draw link, safe explorer links, and screenshots. Never send a seed phrase or private key.

For help reading one source transaction, use How to read SupraScan. Exact contract functions and data structures belong in Smart Contracts.

• Verify Draw Results
• How to read SupraScan for ElyxS
• Prizes in user draws
• Smart Contracts