$GLIZZY
The front page is the short version. This is the long one: what a contest is, where your Choke comes from, and exactly what we can and cannot do.
A Roller opens every ten minutes on a fixed grid. Anyone holding a stake that has been in place for an hour can enter by paying the entry fee. One entry per address.
The grill holds thirty dogs. A dog goes down every three seconds, so a contest runs ninety seconds from first dog to last.
You eat until you decide to stop. Every dog adds to your score. Every dog also brings you closer to your Choke, which you cannot see. Cross it and you are out with nothing, regardless of how well you were doing.
Highest score among everyone still standing takes the Bun.
Your Choke is a number between 1 and 24 that decides how many dogs you can eat before you are finished.
It is derived, not rolled:
choke = keccak256(chainLink, yourValue, contestId, yourAddress) % 24
Four inputs. The chain link comes from a hash chain generated before the game was deployed. Your value is a number you supply when you enter. The contest ID and your address are public.
Nobody can influence it. We cannot, because the chain was fixed at deploy and we publish each link afterwards so you can prove it was. You cannot, because your value is committed when you enter, before you know anything.
Why 24 and not 30. The grill holds thirty. Chokes top out at twenty-four. Nobody can outlast the grill, which means every contest ends in a decision rather than a timer. It also means any score above twenty-four is public proof that somebody used their Dunk.
Before the game was deployed we generated a chain of 250,000 links, each one the hash of the next:
link[n] = keccak256(link[n+1])
We published the first link at deploy. Every contest consumes one link backwards and publishes it when the contest ends.
That means every published link can be hashed to produce the previous one. If it does, the link was fixed before the contest ran and could not have been chosen after seeing how people played. If it does not, we cheated, and you would be able to prove it in one line of code.
The chain is 250,000 deep, which at 144 contests a day is about four and a half years.
You stop by naming the dog you want to stop on. You can name the current dog or the one before it, and nothing further back.
The lookback exists because transactions are not instant. If you decide to stop on dog twenty and your transaction lands a moment late, you should score nineteen or twenty, not choke on twenty-one. Losing an entry to network timing is not a game mechanic.
It is bounded at one dog because an unbounded reach would break the contest. If you could name any earlier dog, you could watch yourself get eliminated and then claim the dog before it. Everyone would bank their exact Choke, nobody would ever choke, and the contest would become a lottery on who drew the highest number.
Once per contest you can Dunk, which resets your Choke meter to zero. It costs and it burns.
The decision is genuinely hard. Dunk early and you have spent it for almost nothing. Dunk late and you may not get the chance. There is no correct answer, because you cannot see the number you are managing.
Staking is a credential, not collateral. It is never at risk.
Hold 100,000 $GLIZZY staked and you are eligible for every contest, forever. Entering does not consume it. Losing does not cost it. It qualifies you and that is all it does.
Your stake goes live an hour after you make it. You can take it back instantly at any time, with no notice, no cooldown and no penalty — the only exception being while you are standing in a contest, which resolves in ninety seconds.
Why the hour. Without it, one holding could qualify an unlimited number of wallets by moving between them. The hour means each qualifying stake serves one address, and running ten lines against a single contest costs a million staked, held for an hour, fully exposed to the market the whole time.
Friction on the way in. None on the way out.
Raw scores land equal reasonably often, so the winner is decided by a rank derived from the same chain:
rank = keccak256(chainLink, contestId, "tiebreak", yourAddress)
Lowest rank among the tied top scorers takes the Bun. Fixed before the contest, unknowable during it, verifiable after.
It deliberately does not depend on transaction ordering. A tiebreak that rewards landing a transaction first is a tiebreak that bots always win.
Anyone. Settlement is a public function and whoever calls it is paid for the gas plus a margin.
This means contests settle whether or not we are online. There is no operator button, no cron job on a box somewhere, and no way for us to hold a result back by doing nothing.
The Bun is split 80% to the winner, 10% carried to the next Main Event, 5% burned, 2.5% to the Reserve, and 2.5% to the creator wallet.
Those numbers are constants in the contract. There is no function to change them. There never will be, because we did not write one.
60,000,000 $GLIZZY, transferred into the game contract at launch in a single public transaction.
It releases 1% of its remaining balance per day, spread across that day's Main Events. It takes in 2.5% of every Bun.
It is finite. At low activity it shrinks; at high activity it holds or grows. There is no admin withdrawal and no rescue path — the only way tokens leave is by being paid to players.
Every result can be recomputed from public data. Open the verifier, paste a contest number, and it recomputes every player's Choke from the published link and shows you whether it matches what the contract paid out.
The verifier is a single static page with no dependencies on us. If our site disappears, the contract and the published links remain, and the arithmetic is four lines.
Worth stating plainly rather than being found out.
We cannot change the split, change a Choke, choose which link a contest gets, pick a winner, take from a pot, or stop a contest settling. All of that is either constant in the contract or open to anyone.
We can stall. The link for a contest goes up after it runs, and if we never published one the contest would hang. That is not a way to take anything — if the link never appears, anyone can void the contest and everyone gets their entry and Dunk back. The count of voided contests is at the bottom of this page.
We do know every Choke in advance, because we hold the chain. That is inherent to the design, not a flaw in it. The creator address is barred from entering in the contract itself, permanently. That is a real constraint and not a complete one, since nothing stops a second address, which is why we are telling you rather than waiting for someone to work it out.
Read from the contract when this page loads. Nobody types this number in.