Next close in
--:--
- Epoch
- -
- Closes today
- -
- Block height
- reading
- Blocks
- -
- Gas price
- reading
Block height straight from the RPC. Watch it move.
Pre-launch · Robinhood Chain
It gets hotter
the longer it burns.
Stake $FLAMES, take sFLAMES one for one, and every five minutes the staked balance grows in place. Stay staked and your share of each close climbs from 1.00x to 3.00x across 30 minutes, then holds there. Unstake and the flame drops back to a spark.
- Fixed APY
- 4,300%
- Epoch
- 5 min
- Per close
- 0.0036%
- Chain id
- 4663
Contract address
issuance pending
issuance pending
Published here and on X in the same minute, written into the site source, taken from nowhere else. If the two ever differ, one of them is a forgery.
The machine
The clock is already running.
Epochs close every five minutes, 288 times a day, aligned to UTC midnight, from a genesis of 2026-09-11 00:00 UTC. The countdown, the epoch number and the index come from those frozen parameters. The block height comes from Robinhood Chain, live, in your browser.
Index
1.00000
- Next rebase
- +0.0036%
- Index at genesis
- 1.00000
- Since genesis
- -
- Closes so far
- -
- Staked supply
- at launch
One sFLAMES is one staked FLAMES times the index. Arithmetic on the frozen rate until launch, then read from the contract.
Heat calculator
1.00x
- At the base rate
- -
- With the heat
- -
- Gain
- -
- Closes
- -
The heat line compounds the base rate times the wallet's own multiplier, close by close, which is what the contract does.
Wallet
no wallet found
- Address
- -
- ETH
- -
- FLAMES
- -
- sFLAMES staked
- -
- Your heat
- -
- Reserve holds
- -
- Chain
- Robinhood 4663
Staking opens when the contract address is published. Connect to read balances on chain 4663. Nothing on this page can move a token.
Real on this page.
Your browser reads the block height, the gas price and the client string from the Robinhood Chain RPC. The wallet card 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 parameters printed above, so they cannot drift from the numbers the contract ships with.
Read only until launch.
Every signing path lives in stake.js, and the page loads that file only once the staking contract address is published here. Until then app.js carries no signing method and no ERC-20 write selector, so the page cannot build a transaction even if you asked it to. Fetch app.js and grep it.
On chain, no custody.
Staking is an explicit transaction you approve in your own wallet, against the contract address published here. The contract holds no owner, no pause and no admin key, and the token address it pays in is fixed at deployment. Your position, your heat and the reserve are all readable on the explorer without asking anyone.
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 takes deposits from the first close.
- 01
Buy $FLAMES
Launches on pons.family, then routes to Uniswap. Any size, no gate. The contract address lands here and on X in the same minute.
- 02
Stake for sFLAMES
Your position is recorded one for one. The sFLAMES balance grows on its own at every close, it cannot be transferred away from you, and the multiplier starts climbing from 1.00x on the first epoch.
- 03
Keep it burning
Thirty minutes unbroken reaches 3.00x, three times the share a fresh stake takes at the same close, and it holds there. Any unstake, even a partial one, drops that wallet to 1.00x.
- 04
Bond at a discount
Optional. Sell ETH or USDC to the treasury and take $FLAMES back below market, vested over five days. Bonds are the only way reserves enter the treasury.
Receipts
One line every five minutes.
Every close prints a receipt: the epoch, the minute it closed, the index after it, the rebase it paid and the average multiplier across stakers. Until launch these lines come from the frozen parameters rather than a contract, and the heat column says so. From launch the epoch bot reads the contract and posts each one to X.
Computed from frozen parameters
- closes since genesis · epoch - open
| Epoch | Closed | Index after | Rebase | Avg heat |
|---|
Mechanism
Six moving parts. That is the whole protocol.
All six sit on chain and all six are boring on purpose. The one new idea is the fourth column of the ledger: how long you have been here.
01
Stake
Send $FLAMES to the contract, take sFLAMES one for one. The position compounds at the next close, not next week, and the multiplier starts its climb in the same minute.
02
Heat
Every staked wallet carries a multiplier. It opens at 1.00x and climbs in a straight line to 3.00x after 6 consecutive closes, which is 30 minutes, then holds there. Any unstake, even a partial one, drops that wallet to 1.00x.
03
Rebase
Every five minutes each staked balance grows by the fixed rate times its own heat, paid out of the reserve the contract holds. Nothing is minted, nothing to claim, nothing to sign.
04
The index
One sFLAMES is one staked $FLAMES times the index. The index carries the growth so no balance ever needs migrating, and the receipts print it after every close.
05
Treasury
Bonds will be the only way reserves enter it: sell ETH or USDC, take $FLAMES back at a discount over five days. Once bonds open, the treasury routes what it buys back into the staking reserve and publishes backing per token every epoch.
06
(3,3)
Two stakers beat one staker and one seller. The maths is old. Coordinating people is the hard part. From the first close after the address is published, the contract pays for it 288 times a day out of the reserve, and pays the ones who stay the most.
The heat
Stake once. The balance rewrites itself.
There is no claim button because there is nothing to claim. Rewards never get sent to you. They get added to what you already hold, 288 times a day, whether or not you are watching. The longer the flame burns, the more of every close it takes.
Heat multiplier over 30 minutes
Linear, never stepped. A wallet fifteen minutes in sits at 2.00x and compounds at exactly twice the rate of a wallet that staked one close ago. The reset hits the wallet, not the pool: everyone else keeps burning.
- 1 close
- +0.0036%
- 1 day at 1.00x
- +1.042%
- 30 minutes
- 1.000396x
- 30 days unbroken
- 2.5417x
- 1 year at 1.00x
- 44.0x
on the staked balance
across 288 closes
the walk to 3.00x, where it holds
at 3.00x from minute 30, pool at 1.00x
if the rate holds for 105,120 closes, before any multiplier
Caveat. Token count, not price. Only staked balances grow: the reserve pays the wallets that stay, and an unstaked balance stays exactly where it was. The heated figures assume the pool average stays at 1.00x. If everyone reaches 3.00x, every share is back to even and the base rate is what is left. Thirty minutes is a short walk, so expect most of the pool to be there.
Chain
Robinhood Chain, read live.
An Arbitrum Orbit rollup running the nitro client, gas paid in ETH. The client string and the block height in this card come from the RPC, not from a deck. $FLAMES launches on pons.family and routes to Uniswap from there.
- Network
- Robinhood Chain
- Chain id
- 4663 · 0x1237
- Stack
- Arbitrum Orbit · nitro
- Gas
- ETH
- Block height
- reading
- Launchpad
- pons.family, then Uniswap
- Explorer
- robinhoodchain.blockscout.com
- RPC
- rpc.mainnet.chain.robinhood.com
- Client
- reading
$FLAMES
One billion at genesis. Nothing is ever minted.
Supply at genesis
1,000,000,000
$FLAMES on Robinhood Chain. No presale, no private round, no tax on buys or sells. The token is issued by the launchpad with no mint function, so the supply is fixed at issuance and never grows. What stakers earn is paid out of the staking rewards reserve below. The figure above reads 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
Sent to the staking contract at launch. Every close is paid from it
15%
Treasury seed
The first layer of backing. The treasury publishes backing per token once bonds open
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: five minute epoch, 0.0036% per close, 1.00x to 3.00x over 30 minutes, one billion at genesis
step 01 - Shipped
Genesis clock started, 2026-09-11 00:00 UTC. The contract inherits this schedule
step 02 - Shipped
This site: live chain reads, wallet reads, calculator, receipts. Read only until launch
step 03 - Shipped
FlamesStaking written, 38 tests, blind verified. Not deployed, not audited
step 04 - Shipped
Launched on pons.family, 2026-09-12. Contract address published here and on X in the same minute
step 05 - Queued
Staking contract published, stake and unstake on from the first close after
step 06 - Queued
Epoch bot starts posting every close to X, rolled up hourly
step 07 - Queued
Bonds open, the treasury starts filling, backing per token published
step 08 - Queued
Routing to Uniswap
step 09
The machine posts its own receipts
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.
FAQ
Questions that keep coming up.
A rebase protocol on Robinhood Chain. You stake $FLAMES, you take sFLAMES one for one, and the staked balance compounds on its own every five minutes at a fixed rate. The twist is the heat multiplier: your share of each close grows the longer you stay staked, up to three times a fresh stake after 30 minutes.
The staking rewards reserve, and nothing else. Fifteen percent of the one billion at genesis goes to the staking contract and every close is paid from it. Nothing is minted. Anyone can top the reserve up, because fundReserve takes $FLAMES from any address. If it ever runs short, an unstake pays out what the reserve actually holds and the contract posts the shortfall rather than reverting.
Each staked wallet carries a multiplier that opens at 1.00x on its first epoch and climbs in a straight line to 3.00x after 6 consecutive closes, which is 30 minutes, and holds there. Each wallet compounds at the base rate times its own multiplier, paid from the rewards reserve. A wallet at 2.00x grows twice as fast as one at 1.00x.
Any unstake from that wallet, even a partial one. The wallet drops to 1.00x and starts climbing again from the next close. Nobody else moves. Adding to a stake does not reset it: the multiplier averages by principal, so a small early stake cannot buy a large late one a head start.
No. There is no claim transaction and no compounding button. The index updates at every close and your sFLAMES balance moves with it, in your wallet, without a transaction from you.
Before launch it is arithmetic: the frozen rate compounded over the number of closes since the genesis clock started, and that date is printed on the page. It is 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 which one you are looking at.
Not today, and you do not have to take that on trust. Connecting asks for account access and reads balances, which is all it does. Fetch app.js and search it for an ERC-20 write selector or any signing method. There are none. Once the staking contract address is published, the page loads stake.js and staking becomes an explicit transaction your own wallet shows you and you approve, against that address.
The staking contract is deployed against the token address, and the token does not exist until issuance. Until that address is published here the buttons stay visible and disabled with the reason next to them, rather than hidden, so you can see exactly what state this is in. When the address lands, the page loads the stake path and every action becomes a transaction you approve in your own wallet.
No. Flames runs independently and holds no affiliation with either. The rebase mechanic is public and people have implemented it many times. This is a new implementation of it, with a loyalty weighting, on a new chain.
Stake once.
Stay lit.
Watch the clock for a few minutes before you decide anything. It is counting real closes, right now, on the schedule the contract inherits.
contractissuance pending