Skip to documentation
Resources/Docs
DevelopersSinjoh v2

Randomness & reward publication

What the enclave proves, what the chain verifies and what remains an attester responsibility.

2 min read·
On this page

The draw commits before the proof

A raffle post records its token, round, ordered ticket root, prior-draw reference and assigned public key. The proof input binds keccak256(token, round, ticketRoot). The on-chain Chainlink ECVRF verifier rejects a proof for another key or committed input.

  1. 01Closed holder interval
  2. 02Published ticket root
  3. 03Committed round + key
  4. 04Enclave VRF proof
  5. 05On-chain winner/credit recording

Enclave and host boundaries

The randomness key is generated inside an AWS Nitro Enclave and retained only in protected encrypted form with backup/standby handling. The host rebuilds the posted ticket list, verifies its root and requests the proof for that input. The selected design does not make the enclave independently validate the entire chain or all holder eligibility.

The host computes selected winners and proofs under the contract’s interval algorithm and frozen prior-draw reference. The contract verifies the proof and selections before recording credits. A host cannot substitute another seed without failing that commitment check.

Randomness proof versus holder measurement

A valid randomness proof establishes the output for a committed key/input. It does not itself prove that the ticket list contains every eligible holder or that prices, sanctions and exclusions were measured correctly. Those are attester responsibilities made inspectable through published inputs, deterministic reconstruction and on-chain allocation bounds.

Publication and rotation continuity

Reward publications record block ranges, observations, configuration, exclusions, skipped periods and results. Matching content is pinned through the configured IPFS providers. Rebuilding from the published inputs should reproduce the root/ticket intervals.

Each posted raffle retains its assigned public key. A key rotation applies to later posts; protected old key material must remain available until pending old-key draws finish. Rotation does not rewrite existing roots or silently cancel reserved prizes.