One draw after sellout#

Tickets are minted before the result is known. After sellout closes the ticket set, the collection makes one Chainlink VRF request. Chainlink produces randomness with a cryptographic proof, which the configured coordinator verifies on-chain before delivering the result.

The contract accepts only its recorded request from its fixed coordinator. Its owner cannot replace the coordinator, choose a different random result or request a reroll after a successful request. Randomness funding is separate from ticket receipts.

Distinct winning tickets#

Finalization selects the configured one to ten winning token IDs without replacement, with six as the default. This guarantees the configured count of distinct winning NFTs once the draw completes. Rejection sampling avoids the bias of taking a random number modulo an arbitrary collection size. Each winning ticket receives a different top score, so there are no tied winning positions.

For six awards in a 1,000-ticket collection, each ticket has a 6-in-1,000 chance of any award. Six different NFTs win, but a wallet can hold more than one of them. Mint order, collection color and decorative linework do not improve a ticket’s chance.

All remaining tickets receive distinct lower scores in token order after the winners are removed. This is a random selection of winning tickets, not a complete random shuffle of every losing score.

Permanent numbers, later scores#

V10 generates a ticket’s four numbers in Solidity from its assigned token ID and a fixed collection key. The reversible mapping is one-to-one, so different NFTs in that collection have different ordered combinations. Each number is from 1 to 16; digits can repeat within a combination. Numbers can repeat across collections, so always include the network and collection address when identifying an NFT.

The mapping is public and predictable. It supplies ticket identity, not randomness or a final score. No buyer supplies numbers or a seed, and no VRF request runs at each mint or at deployment. One later VRF draw after sellout determines winners and scores independently of the permanent numbers.

After finalization, a 1,000-ticket collection with six awards gives the winners scores 1,000 through 995 and the other tickets unique scores 1 through 994. The four numbers remain unchanged. The contract can resolve the combination to its token and then read that token’s final score.

When results are pending#

Sellout, randomness delivery and finalization are separate on-chain steps. A delay does not mean the collection has selected a different result. Requesting randomness and finishing the draw are permissionless contract actions, but they still need transactions and a functioning, sufficiently funded randomness service.

A sold-out current collection does not have a timeout refund or a reroll path if the randomness service is delayed. That dependency and contract risk remain relevant even though the result is verifiable.