Rules, odds and trust
How it works
What enters you in a draw, when new tokens count, how your chance is worked out, what a draw pays, how its randomness is made, and what the program cannot enforce. In plain words, with the values this network uses.

The values on this page (interval, costs, limits, fees, tiers) are read from the lottery program once the page has loaded.
01: Taking part
Holding is what enters you
A wallet that holds $GTL is in the draws by itself. Nothing is sent to the program, nothing has to be signed, and you never have to visit this site to take part.
The program reads your wallet. It keeps one entry for each wallet: an account that records how many of the wallet's tokens take part in the draws. The program writes an entry only from the balance it reads itself, in a transaction called a reading (the instruction sync_holder). Anyone may send a reading for any wallet. The keeper, the service that sends the program's routine transactions, reads every wallet whose balance changed before each draw. An entry can never count more than the program saw in the wallet.
Your tokens stay in your wallet. The program holds no $GTL at all: it reads balances and has no instruction that moves anyone's tokens. That holds for as long as the program is not replaced by its upgrade authority (see What you have to trust).
Which balance counts. Only the wallet's standard token account for $GTL (its associated token account), which the program works out from the wallet's address itself. Anything at that address that is not that wallet's $GTL account counts as 0. A frozen account still counts.
Who pays for a reading. Whoever sends it pays the network fee and, for a wallet that has no entry yet, the rent of the new entry account (Set by the program's configuration). Sending readings is the keeper's job; you can send one for your own wallet on My entry if you do not want to wait.
One entry per wallet. Weight is in proportion to the tokens counted, so splitting a holding across several wallets adds nothing. Each wallet's weight is rounded down on its own, so a split can weigh up to one base unit less for each extra wallet, never more, and each wallet has to hold the minimum on its own.
Pausing. The admin can pause entries. While they are paused, readings add no new tokens to any entry; tokens that leave a wallet still come off its entry, and pending tokens (below) still start to count when their time comes.
What does not count
If an entry is smaller than what a wallet holds, one of these is usually why. Each of them counts as 0:
- Tokens in a liquidity pool, staked or lent.
- Tokens in a token account other than the wallet's standard (associated) $GTL account.
- Wallets that are program addresses: multisig vaults, pools and other program-owned accounts.
- Wallets on the public exclusion list.
- Holdings below the minimum.
Program addresses are addresses no ordinary key signs for: the vaults of multisig wallets, the accounts of liquidity pools and other programs. Most of them could never receive or claim a prize. The same goes for the reserved addresses no payment can reach, such as the system program and the other built-in programs, the system's own information accounts, the burn address and this program itself.
The exclusion list is public and kept by the admin: exchange, team and treasury wallets. An excluded wallet counts as 0 from its next reading.
The minimum applies to the whole balance: a wallet that holds less than Set by the program's configuration counts as 0, not as the part below the minimum.
An out-of-date entry is the other reason: an entry shows the wallet as it was at its last reading, so tokens bought since are not in it yet, and tokens sold since are still in it until the next reading.
02: When tokens count
When new tokens start to count
New tokens never count in the round in which the program first sees them. They count from a later round, once they will have been held one full round interval by that round's draw. There are no last-minute entries.
Round intervalSet by the program's configuration
An entry holds two amounts. Counted tokens take part in the draws. Pending tokens have been seen in the wallet by a reading but do not count yet. A reading that finds more tokens than the entry holds adds the difference to pending, aged from the moment of that reading, not from the moment they were bought.
A reading moves pending tokens to counted once both of these are true:
- A later round. The round in progress is later than the round in which the pending tokens last arrived.
- Held for one full round interval. The time they arrived plus one round interval (Set by the program's configuration) is not later than that round's scheduled draw.
Usually this means tokens seen during one round count from the next one, provided a reading in that round finds them still in the wallet. Tokens seen after the round's scheduled time, while its lock has not landed yet, wait one round more. Wallets can be read only while a round is open: from the lock until the round is settled, no reading is accepted.
Pending tokens of the same round are taken together. Tokens bought during one round join those already pending from it, at their average arrival time weighted by amount. A late purchase can therefore count a little sooner than it would on its own, by as much as the earlier pending tokens make up for; on average, what starts to count has always been held at least one interval by the draw.
Tokens leaving a wallet come off pending first, then off counted, at the next reading. What stays keeps its age.
The round in progress
A reading sees the new tokens and records them as pending. They have no weight in this round's draw.
The next round
Once they will have been held one full round interval by its draw, a reading in that round moves them to counted. They count in that draw and every later one for as long as they stay in the wallet.
03: Holding age
Weight grows with holding age
An entry's weight is its counted tokens times a multiplier, rounded down. The multiplier depends on the holding age: the average age of the counted tokens.
Buying more lowers the holding age. When pending tokens start to count, their arrival time is merged with that of the tokens already counted, at the average weighted by amount and rounded up to the later second. New tokens never inherit old age. Buying the same amount again halves the holding age, measured from the moment the new tokens were first seen; selling keeps the age of what stays.
Selling keeps the age of what stays. A reading sees only the balance at that moment, so changes between two readings count as their net result: a reading that finds the wallet empty closes the entry, and tokens bought after that start from nothing; a wallet that sells and buys back the same amount before anyone reads it keeps its entry and its age.
The multiplier is recorded at a reading. When the holding age reaches a higher tier, the higher multiplier takes effect at the entry's next reading. The keeper reads entries whose tier changed; until then the recorded multiplier is the one used. A draw uses the weights as recorded at its lock.
The tiers are part of the program's configuration. The program accepts multipliers from 1x to 10x that never decrease with age, and changes only while a round is open; a round that is locked keeps the weights it locked. A change applies to each entry at its next reading.
Loyalty tiers on this network
| Holding age at least | Multiplier | |
|---|---|---|
| Set by the program's configuration. | ||
The last column shows what the smallest holding that counts weighs in each tier, as an illustration of the multiplier. Weight is in proportion to the tokens counted.
Selling everything ends the holding age
Counted
…
tokens that count in draws
Multiplier
…
from the holding age
Weight
…
its share of each selection
Set by the program's configuration.
04: Odds
Your chance per prize
There are no fixed odds. Your chance depends on your entry's weight against everyone else's, and on how many prizes the round has.
Chance per prize selection
your weight ÷ total weight in the draw
Your weight is your entry's weight as recorded at its last reading.
Every prize is a separate selection, with replacement. Each prize's winner is drawn from the full weight of the round, so an entry that has already won can win the next prize too. One wallet can win several prizes in a round, or none for many rounds.
The chance of at least one prize is 1 − (1 − p)ⁿ, where p is your chance per selection and n the number of prizes. The numbers of PS5 consoles and GTA VI copies follow exactly from the round's budget, so for them n is known: the chance of at least one console is 1 − (1 − p) to the power of the number of consoles. Only the numbers of SOL prizes and TTWO prizes are drawn at the reveal, so for them the site gives a range. While the reserve boost can still join the budget there are two possible outcomes, and the site gives both, with the boost's chance (see What a draw pays).
TTWO is a token issued by Trek Nexus Markets Ltd under the Backpack Securities name. Its value follows the share price of Take-Two Interactive, which does not issue or endorse it. What it means to hold it
Estimated before the lock, locked after it. Until a round locks, readings change entries, yours and everyone else's, so your share can change. Before the lock the site labels the figure "Estimated probability per prize. This can change before the round locks." After the lock it says "Probability per prize based on this round's locked weights."
Nothing is guaranteed. Taking part pays no interest and no return, and an entry can go many rounds without a prize. Prize money comes from revenue paid into the program (see Where the prize money comes from), never from holders' tokens, which the program does not touch. A prize you win is paid only if your wallet still holds the counted tokens when it is paid (see Hold through the draw). Your own odds are on My entry.
Your entry weighs 1,000 and every entry in the draw together weighs 100,000. Your chance per prize selection is 1,000 ÷ 100,000 = 1%.
1 prize
At least one: 1.00% · Expected: 0.01
5 prizes
At least one: 4.90% · Expected: 0.05
10 prizes
At least one: 9.56% · Expected: 0.10
1 − (1 − 0.01)ⁿ. With ten prizes, a wallet like this one still wins nothing in about nine rounds out of ten.
05: What a draw pays
What a draw pays
At the lock, part of the reward pool becomes the round's budget. The budget pays for PS5 consoles first, then GTA VI copies from what is left, then SOL prizes from the rest. The numbers of consoles and copies follow from the budget; only the SOL prizes are random. TTWO prizes have a budget of their own, in tokens (next section).
The budget. When a round locks, a configured share of the reward pool moves into the prize escrow: that is the round's budget. The program never allows more than 90%. The rest stays in the pool for later rounds, and so does any part of the budget that is not paid out: prizes plus rollover always equal the budget.
The costs. A PS5 console, a GTA VI copy and the smallest SOL prize are set in US dollars. At the lock they are converted to SOL at the price read from the Pyth oracle, minus a safety buffer, and recorded in the round. The SOL price therefore decides how many consoles and copies a budget pays for. The smallest SOL prize is never below what it costs to open an empty account, so a prize can always be paid to a new wallet.
The budget is then spent in a fixed order, the ladder:
- PS5 consoles: as many as the budget pays for at the console cost, up to the most per round and the most prizes per round. None when consoles are switched off.
- GTA VI copies: from what is left, as many as it pays for at the copy cost, up to the most per round, the prizes still free, and the share of the budget copies may take. None when copies are switched off.
- SOL prizes: from the rest. The randomness draws how many, between the configured lowest number (or fewer, when the rest pays for fewer) and as many minimum prizes as the rest pays for within the prizes still free. Each gets the minimum; what is left above the minimums is split between them at random, and no single SOL prize may exceed the largest-prize share of the budget. Rounding and what cannot be placed under that cap roll over.
Each console and copy reserves its full cost: there are no fractional prizes. A console is in a round only if that round's budget pays for one. Consoles and copies may take the whole budget, so a round can pay no SOL prize at all.
Reserve boost. On this network: Set by the program's configuration. When it is on, every lock also moves that share of the jackpot reserve's balance into the prize escrow as the round's boost candidate, recorded in the round record. The randomness then adds it to the budget with the configured chance; otherwise it goes back to the reserve. Until the reveal, a locked round's budget is therefore one of two amounts: the base budget, or the base budget plus the escrowed candidate. So before a draw there are exactly two possible counts of consoles and copies, one for each, and the site shows both. If the boost joins, any part of the budget that is not paid out rolls into the reward pool.
Rounds with nothing to draw are skipped. When no entry has weight, or the budget cannot pay one minimum prize and the prize vault gives no TTWO budget either, the round is skipped instead of locked: no randomness is requested, the pool rolls over and the next round opens on schedule. A round with a TTWO budget and no SOL prize is still locked and drawn, and the reserve boost is tried in it too.
The worked example is filled in from this network's configured costs once the page has loaded.
Projected, locked, then the schedule
06: TTWO prizes
TTWO prizes
A round can also have TTWO prizes: tokens paid from the program into each winner's wallet. They have a budget of their own, separate from the SOL budget, and no round is promised one.
What TTWO is. TTWO is a token issued by Trek Nexus Markets Ltd under the Backpack Securities name. Its value follows the share price of Take-Two Interactive, which does not issue or endorse it. What it means to hold it, and what you should read before you hold $GTL, is in the notice at the end of this section (What a TTWO prize is).
Where the tokens come from
While TTWO prizes are switched on, bought on the open market with a share of the fee revenue, by the operator's purchase wallet (below), for one account of the program, the prize vault, which belongs to the program's own state account. When the token cannot be bought, for instance while its market is closed, nothing is bought, and later rounds share what the vault already holds. A network with no prize token set has no prize vault, holds no TTWO and keeps back no share of the fee revenue. The program holds no holder's $GTL: your tokens stay in your wallet.
Tokens anyone else sends to the prize vault count as prize tokens too: the program cannot refuse them.
While TTWO prizes are switched on, a share of every fee claim goes to the operator's purchase wallet, a public address, which buys TTWO with it for the lottery's prize vault, so that anyone can compare a claim with the revenue paid in plus that transfer. Without a prize token, no share is kept back: every fee claim is paid into the program in full.
How a round's TTWO prizes are drawn
The TTWO budget is fixed at the lock. When a round locks, the program reads the prize vault. What it holds beyond the tokens already set aside for earlier prizes is free; a configured share of the free tokens becomes the round's TTWO budget and is set aside for it. The budget is fixed before the round's randomness exists, so nobody who learns the randomness can change it. On the front page, the figure for a round that is still open is labelled "before this round's purchase": the purchase made with that round's fee claim can still add to the vault before the lock.
No TTWO budget when the share would be less than one smallest TTWO prize (for instance while markets are closed and nothing is bought), when the issuer has paused the token, when the prize vault is frozen, or when the token or the vault cannot be read as the program reads them. Then the round has no TTWO prize. A round with a TTWO budget and no SOL prize is still a round: it locks and is drawn.
How many, and how much each. The round's randomness decides how many TTWO prizes there are, within the range the site shows for the round: at most the configured number, and no more than the budget pays smallest prizes for. It then splits the budget between them at random. Each prize is at least the smallest TTWO prize, and none is above the largest share of the round's TTWO budget. What cannot be placed goes back to the vault's free tokens for later rounds: when a single prize is drawn, about half of the budget stays in the vault.
Winners are drawn like every other prize: by weight, with replacement, from the same randomness. The TTWO prizes do not change the SOL schedule of the round.
How a TTWO prize is paid
By the program itself, into the winner's own wallet. When the prize is awarded, the program checks the same rule as for every prize: the winning wallet must still hold the $GTL counted for it. If it does, the program sends the TTWO from the prize vault into the wallet's standard TTWO account, and opens that account if there is none; the prize bot that sends the award pays its rent. In the default mode the winner does nothing: there is no claim, no sign-in and nothing to send (claim mode, below, is the exception). Every payment carries the note "GTL round <id> slot <n>", so anyone can find it in the winner's TTWO account.
Forfeited when the winning wallet no longer holds the counted $GTL, is on the exclusion list, is an address no payment can reach, or has turned TTWO prizes off. The tokens go back to the prize vault for later rounds.
Owed, paid later, or returned
When the payment cannot be made at that moment, the prize is owed to its winner instead. The program records why:
- The issuer had paused the token.
- The token named a transfer hook program.
- The prize vault was frozen.
- The prize vault held less than the tokens reserved for prizes (only the issuer can make it hold less than it reserved).
- The winner had no TTWO account, and a new one would have started frozen.
- The winner's TTWO account was frozen.
- The winner's TTWO account accepted only confidential transfers.
- The payment could not be made when the prize was awarded.
- The round was drawn in claim mode: the winner receives the prize by signing for it.
- The token or the prize vault could not be read.
Anyone can send an owed prize later, once nothing blocks it (in claim mode, only its winner): the winner, the prize bot or any other wallet, on My prizes or a round's page. Whoever sends it pays the network fee, and the rent of the winner's TTWO account if it has to be opened. The prize was earned at the award, so the winner does not have to hold $GTL any longer.
The claim window. An owed prize can be paid until its claim window ends: a span after its round is settled, fixed when the round locked. After that, anyone may return it to the prize vault for later rounds. A round with owed prizes is complete, but not final, and its record stays on-chain until no prize in it is owed.
Turning TTWO prizes off for your wallet
While TTWO prizes are off for your wallet, a TTWO prize it wins goes back to the tokens kept for later draws, and so does one still owed to it when you turn them off, with no SOL instead. Your wallet stays in every draw for the other prizes. The switch is on My entry. Turning TTWO prizes off creates a small marker account for your wallet: your wallet pays its rent and gets it back when you turn them on again (the figure is beside this text). A prize can also be refused this way after the draw, until it is paid.
Claim mode, if the operator turns it on
The program has a second way to pay TTWO prizes, which the operator can switch on: in claim mode no TTWO prize is sent at the award. Each one is owed to its winner, who receives it only by signing a transaction within the claim window, and that transaction names the fingerprint of a wording the operator publishes. It proves only that the winner's key signed; it proves nothing about who the winner is or where they live. Claim mode is not automatic: a winner who does not sign in time does not receive the prize. A round keeps the mode it locked with, but switching to claim mode also reaches prizes already owed. Which mode runs on this network is in the panel beside this text.
What the issuer can do
The token's issuer controls it, not the lottery: what it can do is in the notice below. Whatever the issuer does, every round still locks or is skipped, is drawn and is settled: a prize that cannot be paid is owed, never lost from the record.
Nothing is promised
What a TTWO prize is
TTWO is a token issued by Trek Nexus Markets Ltd under the Backpack Securities name. Its value follows the share price of Take-Two Interactive, which does not issue or endorse it.
07: The draw, step by step
The draw, step by step
Every step is an on-chain instruction that anyone can send. A keeper sends them as soon as they are due. The program computes every result itself; what the sender of a step can still influence (which recent price update the lock uses, and, for the validator producing the lock's block, that block's hash) is set out under What you have to trust.
Step 1: Read
While the round is open. The keeper sends a reading for every wallet whose balance changed, and anyone may send one for any wallet. From the lock until the round is settled, no reading is accepted.
Fixed here Each entry's counted tokens and weight
Step 2: Lock
At or after the scheduled time. Freezes every weight, moves the budget into escrow, reads the SOL price and converts the console cost, the copy cost and the minimum prize to SOL, stores the parameters (the sell-back rate among them) and commits to all of it. Randomness is requested from ORAO in the same instruction.
Fixed here Who is in, the budget, the costs, the limits
Step 3: Seal
From the next slot, within 512 slots (under two minutes on mainnet): records the hash of the slot the lock landed in.
Fixed here The lock-slot hash
Step 4: Reveal
Once ORAO has answered. Combines the inputs into the round's randomness, decides whether the reserve boost joins, fixes the prize schedule (consoles, then copies, then SOL prizes) and returns unused budget to the pool.
Fixed here The boost, how many SOL prizes and how large
Step 5: Draw
Selects a winning entry for every prize, by weight, from the frozen weights.
Fixed here Who wins each prize
Step 6: Pay
Anyone, one prize at a time. The program reads the winning wallet: if it still holds the tokens counted for its entry and is not excluded, a SOL prize goes from escrow to the wallet, and a console or a copy becomes a voucher in it, its cost moving to the voucher liability vault. Otherwise the prize is forfeited.
Fixed here Paid or forfeited
Step 7: Finalize
Once every prize is paid or forfeited. Returns what is left in escrow, forfeited prizes included, to the reward pool and opens the next round. Draw times stay on the original schedule.
Hold through the draw
A prize is paid only if the winning wallet still holds the tokens counted for it when the prize is paid. At payment the program reads the winner's $GTL account again and compares it with the tokens counted in the entry. If the balance is at least that much and the wallet is not on the exclusion list, the prize is paid. Otherwise it is forfeited: nothing is paid, and the amount goes back to the reward pool when the round is finalized, for later draws.
Only the moment of payment counts. A winner whose balance dipped and came back before the payment is paid. One who sold after the last reading, before or after the lock, is not. The keeper pays right after the draw, but anyone may send a payment, so a winner can also pay its own prize, at a moment of its choosing, whenever the counted tokens are in its wallet.
A prize that can never reach its winner is forfeited too, so that the round can always finish: when the winning address is one of the reserved addresses, or an account only the runtime creates and nobody can sign for. A wallet that its owner turned into a program account is still paid.
Nothing can be borrowed for the check. A payment refuses to run in a transaction that contains an instruction of any other program than this one, the system program and the compute-budget program, so tokens cannot be borrowed, or bought and sold again, around the balance check inside that transaction. Transactions placed next to it are another matter (see What you have to trust). The exclusion list cannot change between a lock and the settlement, so it cannot be used to take a prize from a wallet that has been drawn.
On the results page
What the site's draw states mean
Entries closed
The scheduled time has passed and the lock has landed. While the lock is still on its way the site says Entries closing: until it lands, wallets can still be read. Tokens bought either way count from a later round.
Funding and weights locked
The lock froze the weights, moved the budget into escrow, recorded the SOL price, the costs and the parameters, and requested randomness. No wallet can be read until the round is settled.
Awaiting randomness
The round waits for the seal and for ORAO's answer, then for someone to send the reveal. This normally takes under a minute; when it takes longer, the site says how long and what can happen next.
Results finalized
The randomness is revealed, every winner is drawn, every prize is paid or forfeited, and the next round is open.
Settled, TTWO owed
Shown in place of Results finalized when every prize is settled but a TTWO prize is still owed. The next round is open, and the round's results can still change: the owed prize is paid later, or goes back to the prize vault after its claim window.
When randomness is late
The site shows a late step as late, with how long it has taken. It never resets the clock or shows a result that is not on-chain. Entries stay frozen until the round ends one way or the other: no wallet can be read in the meantime.
Cancellation. Once the randomness timeout (Set by the program's configuration) has passed since the lock, anyone can cancel a round that can no longer be revealed: one whose randomness never arrived, or one that was never sealed and whose lock-slot hash the cluster no longer holds. The budget goes back where it came from, entries can be read again, and no winners are selected. A round whose seal window of 512 slots was missed cannot be drawn, so it waits for that timeout and can then be cancelled.
A round that can still be revealed can never be cancelled, so once ORAO's answer is in, nobody can throw the result away. There is no instruction that requests randomness for a round again. An ORAO authority can still withhold its answer, which ends in a cancellation (see What you have to trust).
08: Randomness
Where the randomness comes from
A round's randomness is a hash of three values: ORAO's VRF output, the lock hash, and the hash of the slot the lock landed in. Each comes from a different source, and the program checks all three. Who can still influence them is set out under What you have to trust.
ORAO VRF output. Inside the lock, the program asks ORAO's verifiable random function for a value for a seed it derives itself from the round number and a one-time nonce. The program refuses a seed that already has a request, so nobody can occupy it in advance (whoever orders the lock's own block can only make the lock fail, and it is sent again with a new nonce), and the request cannot be replaced afterwards.
The lock hash. A SHA-256 commitment to the frozen weight tree, the total weight, the budget, the boost candidate, the parameters and a recent slot hash. It ties the randomness to exactly who was in the round and what it could pay.
The hash of the lock slot. It does not exist yet when the lock is sent, so whoever sends the lock cannot work out the draw in advance and decide whether to go ahead with it. The validator that produces that block influences its hash; that limit is under What you have to trust. The hash of the lock slot is that slot's bank hash, which the program reads from the cluster's SlotHashes record once the slot is complete ("sealing" the round). It is not the blockhash that block explorers show for the slot.
Every number the draw needs (whether the reserve boost joins, the number of SOL prizes and how the remainder is split between them, each winner) is then derived from the randomness with SHA-256 and rejection sampling, so there is no modulo bias. The numbers of consoles and copies are not random: they follow from the budget.
1 · ORAO VRF output
Signed by ORAO
for a seed the program derives from the round
2 · Lock hash
Fixed at the lock
weights, budget, parameters, a recent slot hash
3 · Hash of the lock slot
Recorded at the seal
did not exist while the lock was sent
SHA-256("GTL-RAND-v2" ‖ 1 ‖ 2 ‖ 3)
The round's randomness, stored in the round record
- Reserve boost, if on
- Number of SOL prizes
- How the SOL remainder is split
- The winner of each prize
Check a round yourself
Each round's page recomputes the round in your browser from public data, with an independent implementation of the program's math: the parameters hash, the lock hash, the VRF seed, the randomness, the reserve-boost decision, the prize schedule (consoles, copies and SOL prizes), the totals, and, while the weight tree is unchanged since the lock, every winner.
What the check does not prove
- That ORAO's fulfillment authorities did not steer or withhold their answer (see What you have to trust).
- That the validator producing the lock's block did not try variants of it.
- That the SOL price was a fair one, beyond it being a verified oracle update inside the freshness window.
- That a console or a game copy was delivered. Delivery happens off-chain, by an operator.
- That the entries were up to date at the lock. A wallet's entry is as recent as its last reading.
- That the program running is the one whose code was reviewed. The upgrade authority can replace it.
09: Vouchers
Vouchers: consoles and game copies
A PS5 console or a GTA VI copy is issued as a voucher: an on-chain record owned by the winning wallet. Its owner can redeem it for the prize, sell it on the marketplace, or sell it back to the program, one at a time: the program itself keeps them apart.
The five states
UnredeemedListed for sale
The owner lists it for sale.
Listed for saleUnredeemed
It is sold (to its new owner) or the listing is cancelled.
UnredeemedReserved for redemption
The owner signs a redemption request: platform and region for a game copy, the destination country for a console.
Reserved for redemptionRedeemed
The fulfillment service confirms delivery.
Reserved for redemptionUnredeemed
The fulfillment service records a failure, or the owner cancels after 7 days without an answer.
UnredeemedSold back
The owner sells it back to the program.
A redeemed voucher stays redeemed, and one sold back is spent. A listed voucher cannot be redeemed or sold back until its listing is cancelled, and a reserved one cannot be listed or sold back until its redemption ends.
Both kinds follow the same rules. A console voucher and a game voucher are accounts of the same type, backed by the same vault. Each records its kind and the product locked for that kind in the round that awarded it.
What is public and what is not. Redeeming takes the owner's wallet signature on-chain, which also locks the voucher. For a game copy, the platform and account region are chosen at that moment and recorded on the voucher; for a console, the destination country. Anyone can read them. The program has no place for personal details, delivery addresses, phone numbers or game codes: they go privately to the fulfillment service with a message signed by the wallet, and the chain only holds a hash of the receipt. The game code, or the console's carrier and tracking number, is shown to the owner after a wallet signature.
Funding. When a voucher is awarded, its full cost moves into the voucher liability vault, at the SOL price locked for its round. It stays there until a redemption is confirmed, when it is released to the fulfillment wallet, or until the voucher is sold back. It is not re-valued when the SOL price moves, and there is no deadline for redeeming.
Fulfillment. Consoles and game copies are bought and delivered off-chain by an operator, the fulfillment service. Prizes are to be bought only through authorized purchasing channels: no browser automation and no shared retail accounts. Each redemption request carries a sequence number, which the fulfillment service uses as the key of the supplier order, so a retried order does not buy the prize twice. If an order cannot be completed, the failure is recorded on-chain with its reason and the voucher is unredeemed again, with its funding intact: you can redeem it with other options, sell it or sell it back. If the service neither confirms nor fails a request within 7 days, you can cancel it yourself.
Redeeming a console
A console is shipped to a delivery address. The owner chooses the country first, because it is the only part that goes on-chain, with the redemption request. The address, phone number and e-mail address follow, sent only to the fulfillment service. A console can be requested only for a country the service delivers to at that moment.
The countries a console can be delivered to come from the fulfillment service, which can change them at any time.
- Redeemable once by the wallet that owns the voucher at the time of the request.
- The destination country is recorded on-chain with the redemption request. The delivery address, phone number and e-mail address are sent only to the fulfillment service, with a message signed by the wallet, and never written on-chain.
- A console can be requested only for a country the fulfillment service delivers to at that moment.
- If the fulfillment service has neither confirmed nor failed a redemption 7 days after it was requested, the owner can cancel it; the voucher is then unredeemed again and keeps its reserve.
Redeeming a game copy
- Redeemable once by the wallet that owns the voucher at the time of the request.
- Platform and account region are chosen at redemption; availability depends on the supplier for that region.
- Only an unredeemed voucher can be redeemed, listed for sale or sold back: a listing has to be cancelled first, and a voucher with a pending redemption, a fulfilled one or one sold back can do none of these.
- If the fulfillment service has neither confirmed nor failed a redemption 7 days after it was requested, the owner can cancel it; the voucher is then unredeemed again and keeps its reserve.
Account regions offered at redemption: United States, Canada, United Kingdom, Germany, France, Spain, Italy, Netherlands, Poland, Australia, Japan, Brazil, Mexico. Availability depends on the supplier for each region.
Game copies: delivery by platform
PlayStation 5
Gift card possiblePlayStation does not generally allow gifting a specific digital game to another account. Where a game code cannot be sourced, you receive a PlayStation Store gift card for your account region that covers the game's price.
You are asked to accept this substitute before the request is sent. If only a gift card is available and you did not accept it, the request fails and the voucher is released.
Xbox Series X|S
Delivered as a digital game code or gift for your account region, subject to availability for that region.
PC
Delivered as a digital game code for a PC storefront, if and when the title is offered for PC in your region.
Delivery is an off-chain promise
10: Selling a voucher
Selling a voucher
The owner of an unredeemed voucher can sell it back to the program for a fixed amount of SOL, at once and without a buyer, or list it on the marketplace at a price in USDC.
Selling back
The amount is fixed when the prize is won. It is the voucher's reserve times the sell-back rate locked in the round that awarded it, rounded down, and it is recorded on the voucher. Nobody, the admin included, can change it afterwards, and a buyer on the marketplace gets the voucher with the same amount. The rest of the reserve goes back to the reward pool, where it funds later draws. Both come out of that voucher's own reserve, never out of the reward pool.
When. At any time and in any round phase, for an unredeemed voucher: a listed voucher must be unlisted first, and a pending redemption must end first. It takes one transaction signed by the owner and needs no buyer.
It cannot be undone. A voucher sold back is spent: it can no longer be redeemed, listed or sold. A voucher won while the rate was 0 can never be sold back; its ticket says so and offers no such action.
The admin can change the rate. A change applies only to vouchers awarded in rounds locked after it; vouchers already won keep their amount.
The marketplace
Listing. Only an unredeemed voucher can be listed. The seller sets the price in USDC and can cancel the listing at any time before it sells. While it is listed it cannot be redeemed or sold back. A console voucher can be listed only while the admin's setting for consoles allows it; switching that off does not affect a listing that already exists, which can still be bought or cancelled.
The fee is taken from the seller's proceeds: the buyer pays the listed price, the seller receives it minus the fee. The rate is read at the moment of the sale, and the program never allows more than 10%. Network fees are separate and paid by whoever sends the transaction.
Atomic settlement. The buyer's transaction moves the USDC and the ownership of the voucher in one step. The buyer states the price they expect, so a listing cannot be re-priced under them while the transaction is on its way.
No guarantee of a buyer or a price. The site does not set or suggest prices, and nobody is obliged to buy. Each listing shows what selling back would pay, so a buyer and a seller can compare. The choices of redemption belong to whoever redeems: a bought game copy can be redeemed for the platform and region its new owner chooses among those offered (PlayStation 5 or Xbox Series X|S; PC once the title is offered there), and a bought console for a country the fulfillment service delivers to. Browse the marketplace.
11: Where the money is
Where the money is
Five separate accounts owned by the program hold its SOL, and one more, the prize vault, holds its TTWO for prizes. Each is visible on-chain, and the program decides what can leave each one.
Where the prize money comes from
From revenue paid into the program, and the revenue is planned to come from trading in $GTL. The plan for the launch is a pool on Meteora that charges a fee of 2% on every buy and every sell of the token. Meteora keeps a fifth of every fee, so of the planned 2%, 1.6% of the traded amount would be the project's share. Once the token moves from Meteora's launch curve to its regular pool, the fee option tested so far varies with trading: in a test on a private copy of Meteora's programs, trades there paid between 2.0% and 2.4%. Until the token is launched there is no pool and no fee.
Nobody pays the fee to the lottery directly. Once the pool exists, the fee collector, an automated sender run by the operator, is to claim the project's share of the pool's collected fee shortly before each draw and pay it into the program through the program's revenue instruction, in the same transaction. The program splits every payment between the reward pool, the jackpot reserve and operations (below), adds it to its running total of revenue and records it in an event. The total so far is on the treasury page.
While TTWO prizes are switched on, a share of every claim buys TTWO. Of each fee claim, a share then goes to the operator's purchase wallet, a public address, instead of the program. It buys TTWO on the open market and sends it into the program's prize vault for TTWO prizes. So anyone can compare a claim with the payment into the program plus that transfer (see TTWO prizes, which says whether they are switched on on this network). Without a prize token, no share is kept back: every claim is paid into the program in full.
What can be checked, and what has to be trusted. Once the pool exists, its fee setting and the wallet named in it to claim the partner's share of the fee are public, and that wallet cannot be changed once Meteora's configuration for the pool is created. After the token moves to its regular pool, the share is earned by a position held as a token (an NFT), which its holder can transfer; a share for the pool's creator goes to whoever holds that role, which can be handed on. Every claim and every payment into the program is a public transaction. The revenue instruction is open to anyone, with any amount, so the program cannot tell where a payment came from, and it cannot make the collector pay in everything it claims (see What you have to trust). The lottery sells no tickets and takes nothing from holders' wallets.
Reward pool
For future drawsSpendable reward treasury. A configured share of it is budgeted per draw; the rest rolls over.
Can be moved out by: Only the lock, into the prize escrow.
Jackpot reserve
For future drawsLong-term reserve. With a fixed chance per round, a share of it joins a round's budget (the reserve boost).
Can be moved out by: Only the lock, as a boost candidate announced in advance.
Prize escrow
Holds a draw's budgetBudget locked for the draw in progress. Empty between draws.
Can be moved out by: Payouts to drawn winners; leftovers and forfeited prizes go back to the pool.
Voucher liability
Committed to existing winnersThe reserve behind every PS5 console and GTA VI copy that is won and not yet redeemed or sold back.
Can be moved out by: Per voucher: released to the fulfillment wallet when its redemption is confirmed, or split between its owner and the reward pool when it is sold back.
Operations
Not prize moneyInfrastructure and operating costs. The only vault the admin can take SOL out of.
Can be moved out by: The admin, to the operations wallet recorded in the program.
No instruction lets anyone take SOL out of the reward pool, the jackpot reserve or the prize escrow, the admin included, other than as described here. The voucher liability vault pays out only for a voucher whose owner signed for it: when a redemption the owner requested is confirmed (the fulfillment authority confirms it), or when the owner sells the voucher back. Both hold for the program as it is deployed; its upgrade authority can replace it (see What you have to trust).
Committed and uncommitted. The voucher liability vault holds money that already belongs to winners. The prize escrow holds the budget of a locked round: from the reveal it is owed to that round's winners, and what the prize schedule cannot place goes back to the pool. The reward pool and the jackpot reserve are what future draws can spend. The site always shows these apart: a vault's balance alone is not the amount available for new prizes.
What comes back to the pool. Unused budget at the reveal, forfeited prizes when the round is finalized, and the part of a voucher's reserve that its owner does not receive when selling it back. The program holds no $GTL at all, and holders' tokens are never prize money.
The prize vault. The program holds TTWO for prizes in one account of its own, the prize vault. Only TTWO prizes leave it: paid to a winner's wallet. A forfeited, expired or unused share stays in it for later rounds. The token's issuer can also freeze it or take tokens out of it (see TTWO prizes).
Revenue paid to the program is split as it arrives:
Reward pool
Set by the program's configuration
what draws are paid from
Jackpot reserve
Set by the program's configuration
long-term reserve
Operations
Set by the program's configuration
not prize money
At each lock, and after the draw:
Reward pool
Budget
a configured share moves at the lock
Prize escrow
This round
unused budget and forfeited prizes go back to the pool
Winners' wallets
SOL prizes
Voucher liability
Consoles, copies
released on delivery, or split when sold back
12: What you have to trust
What you have to trust
The program enforces the rules above. These are the parts it cannot enforce, and the people and systems you depend on for them.
ORAO's fulfillment authorities
A round's VRF output is the combination of signatures by ORAO's fulfillment authorities (three on mainnet, all of which must answer). The ORAO program checks that each signature is valid, not that it is the only one that key could have made, so the authority that answers last can steer the result, and any of them can withhold its answer, in which case the round is cancelled after the timeout. If ORAO runs more authorities than a request needs answers, whoever orders their transactions in a block can also choose which answers count. The same keys also answer on devnet, where anyone can ask them to sign any seed: that is why the lock-slot hash is part of the randomness.
The producer of the lock's block
Nobody chooses the hash of the lock slot, but the validator that produces that block influences it. A validator that sent the lock itself and already knew ORAO's output for its seed could try many variants of its own block. Nobody else can.
The price oracle
Pyth's SOL/USD price sets how many lamports the smallest prize, the copy cost and the console cost are, and with them how many consoles and copies a budget pays for. Whoever locks a round may use any fully verified price update inside the freshness window.
Whoever reads the wallets
A reading only ever sets an entry from the balance the program reads, so nobody can give a wallet more weight than it held at a reading, or take weight from a wallet that holds. What readings do not guarantee is that entries are up to date: the program cannot list holders or see a transfer. A wallet that bought counts only once someone reads it (the keeper scans the token's accounts every round), and a wallet that sold keeps its old weight until someone reads it. Such an out-of-date entry dilutes everyone else's chances in the draws it is part of, but it is not paid unless the counted tokens are in the winning wallet when the prize is paid.
The same tokens in several entries
Because anyone may choose when to read a wallet and when to lock, the same tokens can be made to count in more than one entry for a draw: move them between wallets, have each wallet read while the tokens are in it, and lock before the others are read again. Hold through the draw stops such an entry from being paid unless the tokens are back in the winning wallet at payment. The payment's own transaction cannot bring them there, but transactions placed next to it can, at the cost of really holding those tokens. The keeper reads every changed wallet before each lock, which narrows the first part to the moments it leaves; paying promptly does not narrow the second, because a winner can pay its own prize first.
The keeper's money
A reading costs its sender the network fee, and a new entry its rent (Set by the program's configuration). The smallest holding that counts limits how many entries dust balances can make the keeper pay for. Nothing obliges anyone to read a given wallet.
The admin's exclusion list
The admin decides which wallets are excluded (exchange, team and treasury wallets), in public, and only while a round is open. An excluded wallet counts as 0 from its next reading and is not paid a prize it wins before that reading. A wallet excluded after the keeper's last reading before a lock therefore stays in that draw with its weight, but forfeits whatever it wins there; the admin decides this before the draw, without knowing who will win.
The admin, within enforced limits
The admin sets the parameters, only while a round is open and only within the limits the program enforces; never the randomness program, the oracle or the token. A locked round keeps the prize rules it locked, and the sell-back rate applies only to vouchers awarded in rounds locked after a change, but the marketplace fee, the revenue split, the loyalty tiers, the smallest holding that counts and the pause of entries apply from the moment they change (see Questions). The admin can change at any time the fulfillment authority and the wallets that receive released voucher funds, payments from the operations vault and marketplace fees, can hand the admin role to another key, and controls the operations vault.
The $GTL token's issuer
The program reads balances and holds no $GTL, so the $GTL mint's freeze authority or a permanent delegate cannot take anything from the program. Like any transfer out of a wallet, they can make a winner's balance drop below what was counted, and so make a prize forfeit.
The TTWO issuer
The issuer can pause the token, freeze any account that holds it and take tokens back from any account, also after a prize has been paid. The lottery cannot undo or replace that. That includes the prize vault. While the token is paused or the vault is frozen, no TTWO budget is set aside and TTWO prizes are owed instead of paid; tokens taken from the vault leave it short, and no TTWO prize is paid until purchases cover it. None of this can stop a round.
The purchase wallet
The purchase wallet's key signs purchases and the return of unused SOL, nothing else. It has no power over the lottery program and does not own the prize vault; the lottery's own state account does. If that key leaked, what could be lost is the SOL waiting in the purchase wallet (at most a limit the operator sets, 10 SOL by default, plus the shares of claims made before the operator's bot notices) and the wallet's own SOL for fees. Nothing in the prize vault and nothing of the lottery's. Every purchase must give at least a floor worked out from an independent price reference, less a small tolerance (3%). The exchange's own quote is checked against that floor; it does not set it. If an executed purchase differs from its checks, or the SOL the purchase wallet holds for purchases goes down in a transaction that is not one of the bot's own purchases, the bot stops all purchases and keeps no more shares until the operator has looked at that transaction and cleared the stop. The program cannot make the operator buy TTWO, or buy with the whole share: anyone can compare each claim with what was paid into the program and what reached the prize vault.
The program's upgrade authority
The upgrade authority can replace the program. Until it is a multisig with a delay, or revoked, it stands above every rule on this page.
The fulfillment operator, for delivery
Consoles and game copies are bought and delivered by an operator, off-chain. The fulfillment authority can mark any pending redemption as fulfilled, which releases that voucher's reserve to the fulfillment wallet; the program cannot check that the prize really arrived. A redemption neither confirmed nor failed within 7 days can be cancelled by the owner, who may then sell the voucher back or on the marketplace; if the prize was in fact delivered, the operator bears that loss.
The fee collector and the launch settings
The pool's fee setting and the wallet named in it to claim the project's share are public, and every claim and every payment into the program is a public transaction, so anyone can compare what was claimed with what was paid in plus what the purchase wallet received for TTWO. The program cannot make the operator's collector pay in what it claims, or run at all: the key that claims the fee could send it anywhere else, and after the token moves to its regular pool the position that earns the share is an NFT its holder can transfer. It cannot tell revenue from the pool apart from any other payment either. The launch settings themselves (the fee rate, and who receives the project's share) are chosen by the people who launch the token, and can be checked only once the pool exists.
Keepers, for liveness only
Every step is permissionless. If nobody seals a locked round in time, it is cancelled after the timeout and entries stay frozen until then; if nobody sends the steps at all, rounds stall. No funds can be taken either way.
The admin key on this network
Every privileged action (setup, parameter changes, role changes, admin handover, payments from the operations vault, changes to the exclusion list) emits an event that anyone can read.
Set by the program's configuration
Not done yet
These have to be done before the public can use GTL. Until then it is a test preview, not a public offering: on devnet and other test networks, SOL and tokens have no market value and no real-world prizes are awarded.
- Not done: No independent security audit of the program or its math. The reviews so far were automated or by the same people who wrote the code.
- Not done: No legal review, and no gaming or lottery authorization for any jurisdiction. A token-weighted prize draw is regulated as gambling or a lottery in many places.
- Not done: No decision yet on whether ORAO alone is an acceptable source of randomness for the sums at stake.
- Not done: The admin and the upgrade authority are not yet a multisig with a delay.
- Not done: No supplier is contracted yet for delivering consoles or game copies.
13: Questions
Questions
Where does the prize money come from?
From revenue paid into the program. The plan is that this revenue is the project's share of a 2% fee on trades of $GTL in its pool on Meteora, which the operator's fee collector claims and pays in before each draw. The lottery sells no tickets and takes nothing from holders' wallets. While TTWO prizes are switched on, a share of every fee claim goes to the operator's purchase wallet instead, which buys TTWO for TTWO prizes. How it works, and what has to be trusted, is under Where the prize money comes from; what has been paid in so far is on the treasury page.
Do I have to do anything to take part?
No. Holding $GTL in your own wallet is the entry. The keeper reads every wallet whose balance changed before each draw. You can send the reading for your wallet yourself on My entry, which also shows what is counted, what is pending and your chance per prize.
Why do my new tokens not count in this round?
New tokens never count in the round in which a reading first sees them. They count from a later round, once they will have been held a full round interval by that round's draw, and once a reading in that round finds them still in the wallet. My entry shows when your pending tokens start to count.
Why is my entry smaller than what I hold?
Either some of your tokens do not count (in a pool, staked or lent, in another token account, below the minimum: see What does not count), some are still pending, or the entry is out of date and the next reading will bring it up to the wallet.
What happens if I sell after I win?
A prize is paid only if your wallet still holds the tokens counted for your entry when the prize is paid, or for a TTWO prize, when it is awarded. If it holds less, the prize is forfeited and goes back to the pool (see Hold through the draw). Once a prize is paid, it is yours: a voucher in your wallet, SOL, or TTWO (whose issuer can still take it back, see below).
When is a PS5 console in a round?
Only when that round's budget pays for one at the console cost converted at the round's SOL price. When it does not, the site says so and shows how far the budget is from the next console. Nothing on the site shows a console as a prize of a round that cannot pay for one.
Can the operator pick a winner?
No instruction lets anyone name a winner. Winners follow from the round's randomness and the weights frozen at the lock, and anyone can recompute them. The limits of that are listed under What you have to trust: ORAO's authorities, the block producer, and above all the upgrade authority.
Why did a round have no prizes?
Either it was skipped, because no entry had weight, or the budget could not pay one minimum prize and the lock would have set aside no TTWO budget, or it was cancelled, because its randomness could not be completed in time. In both cases the money stays in or goes back to the pool for later rounds.
What if I win a game copy for a platform I do not have?
A game voucher is not tied to a platform until it is redeemed: you choose the platform (PlayStation 5 or Xbox Series X|S; PC once the title is offered there) and the account region then. You can also sell it on the marketplace or sell it back to the program instead.
Are winnings guaranteed?
No. There are no fixed odds and no guaranteed return. An entry can go many rounds without a prize, a prize is forfeited if the counted tokens are not in the winning wallet when it is paid (a TTWO prize, when it is awarded), and a round can be skipped or cancelled. A round may have no TTWO prize.
Who pays network fees?
Whoever sends a transaction pays its fee. You pay for the readings you send yourself (and for a new entry its rent, returned to you when that entry closes), and for listings, purchases, redemptions and selling back. The keeper pays for its readings, the draw steps, the randomness fee and the round records, and, when it pays a console or copy prize, for the voucher account that creates. Every one of these steps is open to anyone, and whoever sends it pays: a winner who sends the payment of its own prize first pays for that voucher account. For TTWO prizes: When you win, the program opens a TTWO account in your wallet if there is none, and the prize bot (or whoever sends the payment) pays its rent. Once the account is empty you can close it and keep that SOL.
Are USD amounts at today's price?
No. USD figures for a round use the SOL price locked on-chain in that round, never a live market price. A voucher's funding is not re-valued when the price moves, and what selling it back pays is fixed on the voucher when it is won.
Can the rules change in the middle of a round?
Only while it is still open. The admin can change parameters only while a round is open, within the limits the program enforces, and never while one is locked. A round takes its prize rules from the configuration at its lock (budget share, prize limits, console and copy settings, sell-back rate, reserve boost, and the safety buffer and freshness limits for the SOL price), so a change made while a round is open applies to that round's lock and every later one. Other settings apply as soon as they change: the marketplace fee at each sale, the revenue split at each revenue payment, whether consoles may be listed at each listing, and the smallest holding that counts, the pause of entries, the loyalty tiers and the round interval at each reading (the interval also when the next draw time is set). The randomness timeout and the record retention are read when a round is cancelled or its record closed, so a new retention also applies to records already on-chain. A round also takes its TTWO rules from the configuration at its lock (the smallest and largest TTWO prize, how many, the claim window and how TTWO prizes are paid), with one exception: switching to claim mode also reaches TTWO prizes already owed.
Does winning or selling a voucher change my weight?
No. Weight comes only from the tokens counted in your entry and their holding age. Prizes, vouchers and their sales do not touch it. Selling $GTL does, at the next reading.
What is the TTWO prize?
TTWO is a token issued by Trek Nexus Markets Ltd under the Backpack Securities name. Its value follows the share price of Take-Two Interactive, which does not issue or endorse it. Some rounds have TTWO prizes, from a budget of their own: the program sends each one into the winner's wallet (in claim mode, if the operator turns it on, the winner receives it only by signing for it within its claim window), and how many there are is random within the range the site shows for the round. It is a prize drawn by chance, like every other prize. See TTWO prizes.
Is it a Take-Two share?
No. In a wallet of your own the token is a record on the blockchain only. Under the issuer's terms it gives you no share, no right against the issuer, no dividend and no vote. Only a Backpack Exchange user in a country Backpack serves can exchange it for the share, and only there. One token stands for the number of shares the issuer's multiplier says. Its value moves with Take-Two's share price, and it can be sold only where someone buys it. See What a TTWO prize is.
What if I am a United States person?
Whoever holds the token is bound by the issuer's terms, even if it arrived without their asking. The terms forbid passing it to United States persons and to people where holding it is unlawful. They make the holder answerable to the issuer for breaking them, send disputes to arbitration in the British Virgin Islands, and can be changed by the issuer. The lottery cannot tell who you are or where you live. If you are a United States person, or holding the token is unlawful where you live, turn TTWO prizes off for your wallet. That does not make anyone else's prize lawful, and the operator remains responsible for handing the token out. The switch is on My entry. See What a TTWO prize is.
Why did my round have no TTWO prize?
A round has TTWO prizes only when its lock sets aside a TTWO budget. It does not when the share of the prize vault's free tokens that a lock sets aside would be less than one smallest TTWO prize (nothing is bought while the token's market is closed), when the issuer has paused the token or frozen the prize vault, or when TTWO prizes are not switched on. A round may have no TTWO prize, in particular while markets are closed. Each round's page says which applied, where the site can read it.
Why is my prize "owed"?
Because the program could not pay it when it was awarded: for instance the issuer had paused the token, your TTWO account was frozen, the prize vault held less than it had set aside, or the round was in claim mode. Anyone can send it once nothing blocks it (in claim mode, only you, by signing for it), until its claim window ends; after that anyone may return it to the prize vault. My prizes shows why and until when (see Owed, paid later, or returned).
Can the token be taken back?
Yes. The issuer can pause the token, freeze any account that holds it and take tokens back from any account, also after a prize has been paid. The lottery cannot undo or replace that. See What a TTWO prize is.
Grand Theft Lotto is an independent project. It is not affiliated with, endorsed by or sponsored by Rockstar Games, Take-Two Interactive, Sony, Microsoft, Backpack or Trek Nexus Markets Ltd. Product names are used only to describe prizes.





