Pre-launch · Robinhood Chain Live · Robinhood Chain

It gets bigger
the longer it rolls.

A rebase on Robinhood Chain with one twist: time counts. Stake $SNOW, receive sSNOW one for one, and every six minutes the balance grows in place. Keep it staked and your share of every close climbs from 1.00x to 3.00x over thirty days. Unstake, and the ball starts again at 1.00x.

3,861%Fixed APY
6 minEpoch
0.0042%Per close
4663Chain id
Contract addressNot yet published
CA: coming at launch

Published here and on X at the same moment, baked into the page rather than written in by script. If the address on X and the address here ever differ, one of them is a copy.

Contract addressVerify before you buy
__CA__
The machine

The clock is already running.

Epochs close every six minutes, 240 times a day, aligned to UTC midnight, from a genesis of 2026-09-06 00:00 UTC. The countdown, the epoch number and the index are computed from those frozen parameters. The block height is read from Robinhood Chain, live, from your browser.

Next close in
--:--
Epoch0000
Closes today000 / 240
Block height
Blocks
Gas price

Block height straight from the RPC. Watch it move.

Index
1.00000
Next rebase+0.0042%
Index at genesis1.00000
Since genesis+0.000%
Closes so far0 closes
Staked supplypending

One sSNOW is always one staked SNOW times the index. Computed from the frozen rate until launch, then read from the contract.

Roll calculator
1.00x
0 days
SNOW
At the base rate100,000
With the roll100,000
Gain+0.00%
Closes0 closes

Arithmetic on the frozen rate. The roll line assumes the pool average stays at 1.00x; your real share depends on everyone else's multiplier too.

Wallet
not connected
Address-
ETH-
SNOW-
sSNOW staked-
ChainRobinhood · 4663

Staking opens at launch. Connect to read balances on chain 4663; nothing on this page can move a token.

Real on this page. Block height, gas price and the client string are read from the Robinhood Chain RPC in your browser. The wallet connects over EIP-1193 and reads balances with eth_call. The countdown, the epoch number, the index, the receipts and the calculator are arithmetic on the frozen parameters printed above, so they cannot drift from the numbers the contract ships with.
Design intent, until launch. Anything that needs the staking contract: the staked supply, the average multiplier on each receipt, the sSNOW balance and the stake and unstake buttons. They are shown disabled with the reason written next to them. This page contains no signing call and neither ERC-20 write selector. Fetch app.js and grep it.
How to stake

Buy, stake, walk away.

Two steps and one option. No whitelist, no allocation form, no role to farm. The pool opens to everyone at launch and the staking contract accepts deposits from the first close.

01

Buy $SNOW

Launches on pons.family, then routes to Uniswap. Anyone can buy any size. The contract address is published here and on X at the same moment.

02

Stake for sSNOW

Minted one for one. Your balance grows on its own at every close, and your multiplier starts climbing from 1.00x on the first epoch.

03

Keep it rolling

Thirty days unbroken takes you to 3.00x, three times the share of a fresh stake at every close. Any unstake, even partial, resets that wallet to 1.00x.

04

Bond at a discount

Optional. Sell ETH or USDC to the treasury and receive $SNOW below market, vested over five days. Bonds are the only way reserves enter the treasury.

snow@robinhood-chain: ~/stake
$ swap 0.25 ETH -> SNOW
  filled on pools.trade
$ stake --all
- balance      1,000.000 SNOW   idle
+ balance      1,000.000 sSNOW  compounding
+ multiplier   1.00x  (3.00x after 30 days)
+ next rebase  +0.0042%
+ next close   --:--
+ action req.  none
$ 
Receipts

One line every six minutes.

Every close gets a receipt: the epoch, when it closed, the index after it, the rebase it paid and the average multiplier across stakers. Until launch these lines are computed from the frozen parameters, not read from a contract, and the multiplier column says so. From launch the epoch bot reads the contract and posts each one to X.

Computed from frozen parameters 0 closes since genesis · epoch 0000 open
EpochClosedIndex afterRebaseAvg mult
  • Receipts fill in from the frozen schedule once the script runs. Epoch 0000 opened at 2026-09-06 00:00 UTC.
Mechanism

Six moving parts. That is the whole protocol.

Every one of them is on chain, and every one of them is boring on purpose. The only new idea is the fourth column of the ledger: how long you have been here.

01

Stake

Lock $SNOW, receive sSNOW one for one. The position starts compounding at the next close, not next week, and the multiplier starts its climb the same moment.

02

Roll

Every staked wallet carries a multiplier. It starts at 1.00x and climbs in a straight line to 3.00x after 7,200 consecutive closes, which is thirty days. Any unstake, even partial, resets that wallet to 1.00x.

03

Rebase

Every six minutes the contract mints into the staking pool at the fixed rate and splits it across stakers pro rata by balance times multiplier. Nothing to claim, nothing to sign.

04

The index

One sSNOW is always one staked $SNOW times the index. The index carries the growth so your balance never needs migrating, and the receipts print it after every close.

05

Treasury

Bonds are the only way reserves enter it: sell ETH or USDC, take $SNOW back at a discount over five days. Backing per token is published every epoch and never marketed up.

06

(3,3)

Two stakers beat one staker and one seller. The maths is old; the coordination is the hard part. Snowball pays for it 240 times a day, and pays the ones who stay the most.

The roll

Stake once. The balance rewrites itself.

There is no claim button because there is nothing to claim. Rewards are not sent to you. They are added to what you already hold, 240 times a day, whether or not you are watching. And the longer the ball rolls, the more of every close it picks up.

Roll multiplier over thirty days 3.00x2.00x1.00x day 0day 15day 30 unstake here back to 1.00x

Linear, not stepped. A wallet at day 15 sits at 2.00x and earns exactly twice the share of a wallet that staked this morning. The reset applies to the wallet, not the pool: everyone else keeps rolling.

1 close+0.0042%on the staked balance
1 day+1.013%across 240 closes
30 days1.353xat 1.00x the whole way
30 days rolled2.05xclimbing to 3.00x, pool at 1.00x
1 year39.6xif the rate holds for 87,600 closes, before any multiplier

Caveat. Token count, not price. Only staked balances grow, so an unstaked holder is diluted at the same rate. The rolled figure assumes the pool average stays at 1.00x; if everyone rolls to 3.00x, everyone's share is back to even and the base rate is what is left.

Chain

Robinhood Chain, read live.

An Arbitrum Orbit rollup running the nitro client, with gas paid in ETH. The client string and the block height in this card come from the RPC, not from a deck. $SNOW launches on pons.family and routes to Uniswap from there.

NetworkRobinhood Chain
Chain id4663 · 0x1237
StackArbitrum Orbit · nitro
GasETH
Block height
Launchpadpons.family, then Uniswap
RPCrpc.mainnet.chain.robinhood.com
$SNOW

One billion at genesis. The rebase is the only mint.

Supply at genesis
1,000,000,000

$SNOW on Robinhood Chain. No presale, no private round, no tax on buys or sells. After genesis the only thing that creates $SNOW is the rebase, 240 times a day, into the staking pool. The figure above is read from the token contract with totalSupply once there is one to read.

Liquidity and public market

Open pool on pons.family at launch, then Uniswap

58%
Staking rewards reserve

Seeds the first closes before bonds fill the treasury

15%
Treasury seed

The first layer of backing, published per token every epoch

10%
Team

12 month linear vest, nothing unlocked at launch

12%
Ecosystem

Integrations, audit, market making

5%
Changelog

Shipped in public, in order.

Shipped

Parameters frozen: 6 minute epoch, 0.0042% per close, 1.00x to 3.00x over 30 days, one billion at genesis

step 01
Shipped

Genesis clock started, 2026-09-06 00:00 UTC. The contract inherits this schedule

step 02
Shipped

This site: live chain reads, wallet reads, calculator, receipts. Read only by design

step 03
Queued

Launch on pons.family. Contract address published here and on X at the same moment

step 04
Queued

Staking contract published, stake and unstake turn on, sSNOW reads go live

step 05
Queued

Epoch bot starts posting every close to X, rolled up hourly

step 06
Queued

Bonds open, treasury starts filling, backing per token published

step 07
Queued

Routing to Uniswap

step 08
The machine posts its own receipts epoch 0241 closedindex 1.01212 / staked pending
avg multiplier pending / treasury 0.00
next close in 06:00 epoch 0242 closedindex 1.01217 / staked pending
avg multiplier pending / treasury 0.00
next close in 06:00 epoch 0243 closedindex 1.01222 / staked pending
avg multiplier pending / treasury 0.00
next close in 06:00

The shape of a receipt. The index figures are what the frozen rate produces at those epochs; the pending fields are the ones only the contract can fill. If the protocol has a bad epoch, the bot posts that too. Follow @snowballrebase.

FAQ

Questions that keep coming up.

What is Snowball Rebase?+

A rebase protocol on Robinhood Chain. You stake $SNOW, you receive sSNOW one for one, and the staked balance compounds automatically every six minutes at a fixed rate. The twist is the roll multiplier: your share of each close grows the longer you stay staked, up to three times a fresh stake after thirty days.

Where does the yield come from?+

New supply. The contract mints into the staking pool at every close. Holders who stake keep their share of supply. Holders who do not stake give theirs up. Holders who stay staked take a growing share of what is minted. That is the entire game.

How does the roll multiplier work?+

Each staked wallet carries a multiplier that starts at 1.00x on its first epoch and climbs in a straight line to 3.00x after 7,200 consecutive closes, which is thirty days. Each close's mint is split across stakers pro rata by balance times multiplier. A wallet at 2.00x earns twice the share of an equal balance at 1.00x.

What resets it?+

Any unstake from that wallet, even a partial one. The wallet goes back to 1.00x and starts climbing again from the next close. Nobody else is affected. Adding to a stake does not reset it.

Do I need to claim or restake?+

No. There is no claim transaction and no compounding button. The index updates at every close and your sSNOW balance moves with it, in your wallet, without a transaction from you.

Is the index on this page real?+

Before launch it is arithmetic: the frozen rate compounded over the number of closes since the genesis clock started, which is stated on the page. It is exactly what the contract will report if it inherits the schedule as planned. After launch the page reads it from the contract and the receipts say so.

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 app.js and search it for the ERC-20 write selectors or any signing method; there are none. When the staking contract exists, staking will be an explicit transaction you approve in your own wallet, against an address published here first.

Why can I not stake yet?+

Because the staking contract is not published yet. A stake button with no contract behind it could only send your tokens to a plain wallet with nothing on chain obliging anyone to give them back. The buttons are visible and disabled with the reason next to them, rather than hidden, so you can see exactly what state this is in.

Is this affiliated with OlympusDAO or with Robinhood?+

No. Snowball Rebase is independent and unaffiliated with either. The rebase mechanic is public and has been implemented many times. This is a new implementation of it, with a loyalty weighting, on a new chain.

The Snowball Rebase mark

Stake once.
Keep rolling.

Watch the clock for a few minutes before you decide anything. It is counting real closes, right now, on a schedule the contract will inherit.

How to 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.