Only the rebase rolls.
Never the stake.
Stake LUCK once. Every four hours the protocol rebases, and how big that rebase is gets read out of the closing block hash. Two leaves is a thin epoch. Seven leaves pays a hundred times. Your staked balance never falls, because there is no band on the table that can contract it, and the whole table is published below.
__CA__
Reading Robinhood Chain over JSON-RPC, live, from your browser
The Draw is already running.
The protocol rebases every four hours. The Draw below runs the very same resolver against every block instead, so the distribution is watchable in a minute rather than a week. Nothing is staked here and nothing is at risk. Sit on this section for a while and you will watch the table underneath come true.
Sampled from the chain head about twice a second, so this is a sample of blocks rather than every block. Over a short session the average multiplier will sit well away from ×0.996. That is variance, and it is the entire point.
Published in full, before launch.
Most of this meta never prints this. Here it is, generated at runtime from the same constant the resolver reads, so the page physically cannot show you odds the mechanism does not use. Change one, and both move together. The column on the right is what each band pays on the stake you set in the terminal below.
| Band | Name | Chance | Rebase | Pays you |
|---|---|---|---|---|
| Loading the table from the same constant the resolver uses… | ||||
Drawn on a log scale on purpose. On a linear axis the jackpot band is one part in five thousand and vanishes entirely, which would flatter the protocol. The rare bands are the ones people are actually here for, so they stay legible next to the common ones.
Set a stake. Watch the epoch close.
Everything in this panel is arithmetic on the table above, your slider and one stated base rate of — per epoch. Nothing here is on chain, nothing is placed, and the stake button stays off until an audited pool contract exists to place it into.
Averages over very many epochs, not what any single rebase returns. Only — of rolls land above ×1.00, so most epochs pay under the base rate and the average is carried by bands you will rarely see. The stake itself never moves.
| Band | Chance | Rebase | Pays |
|---|
Check any roll by hand.
Take any block hash from the explorer and run these seven lines. You will get the same band the protocol got. No server in the loop, no seed held back, and nothing to take our word for.
r = parseInt(blockHash.slice(-8), 16) % 10000
r < 3000 → 2 leaf ×0.20
r < 7000 → 3 leaf ×0.75
r < 9200 → 4 leaf ×1.40
r < 9900 → 5 leaf ×3.00
r < 9998 → 6 leaf ×10.00
otherwise → 7 leaf ×100.00
Where this is not good enough yet
A block hash is produced by whoever produces the block. For the Draw above, which has nothing at stake, that is fine, and it is exactly why the Draw has nothing at stake. For a contract holding real value it is not good enough: a sequencer that dislikes a result can withhold or reorder a block.
So the pool contract will resolve against a commit and reveal, or a verifiable random function, and never a raw block hash. That work is not done. Until it is, the stake button stays off, and this page says so rather than shipping the button and hoping nobody looks.
The stake cannot contract
Every multiplier on the table is positive. The worst band on it is a thin epoch, not a loss. That is a property of the numbers, which are printed, rather than a promise in the copy.
Nothing here can move a token
This page requests account access and reads balances. It never asks for a signature, an approval or a transaction. Fetch the script and grep it for the write selectors yourself; the count comes back zero.
The odds come from the code
The table, the expected multiplier and the reserve are all computed at runtime from the same constant the resolver reads, so the published numbers cannot drift from the ones in use.
The reserve is stated
The average epoch pays ×0.996 of the base rate. The missing — is retained as protocol reserve, and it is what funds the seven leaf band. A reserve nobody mentions is the thing people go looking for.
Fixed supply, stated plainly.
LUCK on Robinhood Chain. Supply is fixed at launch and the figure above is read from the token contract with totalSupply once there is one to read. Before launch it is the intended number and nothing more.
Six rebases a day. Not six hours, not eight, so it is not mistaken for anything already running on this chain.
No buy or sell tax. The protocol keeps the stated reserve and nothing else.
LUCK. Four letters, and the same word as the domain and the handle.
Robinhood Chain, id 4663, an Arbitrum Orbit rollup. The client string in the strip above is read live.
Shipping in public, without dates.
Now
This page. The Draw live on real block hashes, the odds published in full, the wallet layer read only.
Next
Token launch. The contract address appears here and on X at the same moment, baked into the served HTML.
Then
The pool contract, with commit-reveal or VRF randomness, audited before it takes a single deposit.
Later
Roll history you can query, per wallet records, and a public address for the reserve.
Straight answers.
Can I lose my stake?+
Not to the roll. Every multiplier on the table is positive, so the worst outcome is a rebase of ×0.20 rather than a contraction. The stake stays staked at its full size. You can of course still lose money the ordinary way, by the token being worth less than you paid for it, and no mechanism on this page changes that.
Is this gambling?+
The size of your reward is decided by chance, so the honest answer is that it has a wager inside it. What it is not is a wager on your deposit: nothing on the table can take the stake itself. That distinction is the whole design, and it is why the worst band is ×0.20 rather than a negative rebase.
Can this page move my tokens?+
No, and you do not have to take that on trust. Connecting requests account access and reads balances, which is all it does. Fetch the script and search it for the ERC-20 write selectors or any signing method; there are none. When a pool contract exists, staking will be an explicit transaction you approve in your own wallet, against an address published here first.
Why publish the odds at all?+
Because a mechanism whose odds you cannot see is one you have no reason to trust, and because it costs us nothing to be checkable. The table is generated from the same constant the resolver reads, so it cannot quietly disagree with the code.
What is the reserve for?+
It funds the rare bands. A seven leaf epoch pays a hundred times the base rate and that has to come from somewhere. The expected multiplier is ×0.996, so the protocol retains — of each epoch's emission, and that is the entire difference.
Why can I not stake yet?+
Because there is no pool contract. A stake button with no pool behind it could only send your tokens to a plain wallet, with nothing on chain obliging anyone to give them back. That is not an unfinished feature, so it is not shipped. The button is visible and disabled with the reason next to it, rather than hidden, so you can see exactly what state this is in.
Is a block hash safe randomness?+
Not for money, no. Whoever produces a block can decline to publish one they dislike. That is fine for the Draw running above, which has nothing at stake, and it is not fine for a contract holding real value. The pool will use commit-reveal or a VRF instead. See the fairness section.
Is the base rate real?+
It is a stated placeholder. — per epoch is the number the terminal computes with, and it is written here rather than implied so that it can be checked against whatever the contract ships with. If it changes, it changes here first.
The odds are on the table.
Literally.
Watch the Draw for a few minutes before you decide anything. It is running on real blocks, right now, with nothing at stake.
contract __CA_SHORT__No contract address yet. When there is one it is published here and on X at the same moment, and it will be in the page source rather than written in by script.