Launching on pons_v2 · Robinhood Chain
In Lisp, cons is the operator that builds a list by adding one cell to the front. It does not edit what is already there. CONS is a rebase protocol that works the same way. Every eight hours the supply takes one more cell, and every balance moves by the same proportion in the same block. Nobody is early to a rebase and nobody is late to one.
The read
A rebase is not an announcement. It is a state change on chain at a fixed time, applied to the whole supply at once. This is the shape of the record. The figures below are illustrative and the panel is not reading a live contract, because CONS has not launched yet.
Illustrative ledger. Not a live contract read.
The stake
Staking is one deposit and nothing else after it. You send CONS to the vault and receive sCONS, a receipt token that sits in your own wallet. From that moment every epoch applies to your sCONS balance directly. No claim, no harvest, no compounding button to remember, and no lock. Unstake whenever you want and the vault returns CONS one for one.
Staking opens when the contract goes live. You can connect now to check you are on Robinhood Chain and ready. Nothing is signed, nothing is spent, and no approval is requested.
What you hold after staking
Before you stake anything
CONS goes into the vault, the vault mints you sCONS one for one. It is your token, in your wallet, transferable like anything else on the chain.
Every eight hours the rebase multiplies every sCONS balance by the published factor. You sign nothing and you pay no gas. Your wallet simply reads a larger number.
Burn sCONS, get CONS back. No cooldown, no queue, no exit penalty, no notice period. A lock would make the numbers look better and it would not make them truer.
The caps
Season one pre-staking is capped twice, on purpose. There is a hard ceiling on the pool and a hard ceiling on any single wallet inside it. Both numbers are published before anyone stakes anything, and neither moves once the pool opens.
Pool capacity
88,000,000 $CONS, cappedPer wallet
2,800,000 $CONS maximumOne wallet cannot pre-stake past this, whatever it holds. Split it across addresses if you want to, we are not going to pretend that is impossible, but the cap is what keeps the published distribution honest for everyone reading it.
The pool, drawn to scale
Drawing the pool to scale.
When the pool is full
Pre-staking closes. It does not queue you, it does not take your tokens and hold them, and the cap does not quietly rise because demand was strong. Space only reopens when an existing staker unstakes, and because there is no lock, that can happen at any moment. This is the same rule Chainlink runs on its community pool, and it is the only version of a cap that means anything: a cap you move on a good day was never a cap.
The rebase
This is the part that decides whether a rebase protocol is real or theatre. Every rebase has to be paid for by something. If the protocol mints the tokens it hands out, it is diluting the very people it is paying and calling the result yield. CONS does the other thing. Every epoch is paid out of a reserve of CONS that was bought on the open market before it was ever owed.
Protocol revenue buys CONS on pons_v2 and puts it in the reserve. The buy happens on chain, in public, before any epoch is allowed to spend it.
Each rebase draws down that reserve rather than reaching for the mint. Nothing new is created, so nobody is quietly paying for their own rewards.
If the reserve runs dry the rebase pauses. It does not shrink quietly, it does not start printing, and it does not pretend. The runway is public the whole way down.
The same number, the opposite meaning
Illustrative, at an arbitrary rate, to show direction rather than magnitude. Minting pays stakers with supply taken from holders, so the slice shrinks even though the number climbs. Buying pays them with revenue, so the slice does not move. CONS buys.
Why this is the only question worth asking
A minted rebase and a bought rebase put the identical number in your wallet and mean the opposite thing. The first moves value from holders to stakers. The second spends revenue the protocol actually earned. You cannot tell them apart from the rate, because the rate looks the same either way. You can only tell them apart by where the tokens came from, which is why CONS publishes that instead of a headline percentage.
The loop
Revenue buys CONS, the reserve holds it before anything is owed, and at the epoch boundary the reserve pays every sCONS balance at once. Three stages, one loop, running live below. Notice that nothing eases across the boundary. The epoch fires as a step, because that is exactly what a rebase is.
The reserve
A rate is trivially easy to make large and tells you almost nothing. The reserve balance and the runway are the two numbers that decide whether a rate survives contact with next month, so those are the ones that belong on the front page.
Next epoch
The clock is real, it counts down to the next eight hour boundary in UTC. Nothing behind it is live yet, because CONS has not launched.
How the reserve works
No figure on this card is live. Every one of them goes on chain at launch, where you can check it yourself rather than take our word for it.
Proof of mechanism
This is the part most rebase sites leave out, so it is the part we put first. A rebase multiplies every balance by the same factor. Your number of tokens goes up. The slice of total supply you hold is exactly what it was before. Drag the dials and watch both at once.
Illustrative. The rate above is a dial, not a commitment. The rate CONS actually runs is published with the contract at launch.
Balance, stepped per epoch
A rebase is a step, not a slope. The line holds flat inside an epoch and moves at the boundary.
One epoch, start to finish
Eight hours pass. Nothing about your balance changes during it. Trading, transfers and everything else behave the way any ERC-20 on the chain behaves.
At the boundary the total supply is multiplied by the published factor. This is one state change affecting the whole supply, not a distribution sent wallet by wallet.
Because balances are held as shares rather than fixed counts, every wallet reads a larger number in the same block. No claim step. No transaction to sign. No gas to pay.
Cadence
Three rebases a day, every day, on the clock rather than on a mood. The bars below show the schedule shape, not recorded results.
Terms
Honest questions
No, and anyone telling you otherwise is selling something. A rebase changes how many tokens you hold, not what fraction of the supply you hold. If your balance grows by the same factor as everyone else's, your position is unchanged. What a rebase does is make the schedule public, mechanical and identical for every wallet.
No. Balances are held as shares, so the number your wallet displays changes when the supply changes. There is no claim transaction and no gas to pay for it.
It is fixed at launch and published with the contract. The dial in the demo above is there so you can see how the mechanism behaves at different rates. It is not a quote and it is not a promise.
On pons_v2, the launch venue on Robinhood Chain, from the moment it goes live. Robinhood Chain is an EVM Layer 2 built on the Arbitrum Orbit stack and gas is paid in ETH, so any wallet that supports the chain works.
There is no presale. Anything else about allocation will be stated on this page and on X at launch rather than hinted at now. Until the contract is public, treat every number on this site as illustrative.
When it opens
Any wallet that supports the chain will do. Gas is paid in ETH, so keep a small amount for fees.
The contract address goes up on X and on this page at the same moment. There is no early list and no private link. If you are sent one, it is not ours.
CONS is live on pons_v2 from launch. Check the address against the one published here before you buy anything.
No claim, no queue, no allowlist. The schedule is the product.