Tide__CA__
The tide comes in every six hours.
Every trade pays a fee. At each tide, 00:00, 06:00, 12:00 and 18:00 UTC, a slice of those fees becomes the pot and one holder wallet wins it, drawn by the hash of the block that closed the tide and weighted by how much it holds. Four winners a day, paid on chain. Nothing to stake, nothing to claim.
Reading Robinhood Chain over JSON-RPC, live, from your browser. No backend, no key.
Wall time to the next tide, UTC. When it turns, the tide script sweeps the fees, claims the creator share from the escrow, runs the draw on the closing block and pays the winner. Three transactions, all in the table below.
Every tide, a line in the table.
One line per tide, like an almanac. The block that closed each tide is found on Robinhood Chain by timestamp. The winner and the amount come from the pot wallet's own transactions on chain. When a tide comes in while you are here, the line is written in front of you.
- #—next
00:00:00——
Hold it. The tide does the rest.
You never send tokens anywhere. Trading pays fees, the tide turns them into a pot, and the block hash decides who gets it. Every step is a transaction on Robinhood Chain that anyone can open.
- Tides per day
- 4
- Closing times, UTC
- 00:00 · 06:00 · 12:00 · 18:00
- The pot
- a slice of the fees
- Eligible from
- 100,000 TIDE
The pot is a slice of the creator fees that have accrued since the last tide, so a busy six hours pays more than a quiet one. It is never a fixed number and this page never prints one.
hash = blockhash(block that closed the tide) x = uint(hash) mod sum(balance of every eligible wallet) walk the eligible wallets in address order, each as wide as its balance at that block winner = the wallet where x lands
Nobody can choose a block hash, and balances are read from the chain's own transfer logs at that block. Same inputs, same wallet, on any machine.
Trade
Every buy and sell on the pons_v2 curve pays a creator fee. It accrues on the curve as people trade.
The tide turns
At 00, 06, 12 or 18 UTC the tide script wakes. It sweeps the fees on the curve and claims the creator share from the pons escrow into the pot wallet.
The block
The last block before the tide is the closing block. Its hash is the only randomness, and nobody chose it.
The line
Every wallet holding at least 100,000 TIDE at that block is laid on a line, each as wide as its balance, in address order.
The draw
The hash, read as a number, lands somewhere on the line. That wallet wins. Hold more and you are wider.
The payout
A slice of the fees goes to the winner in one transaction from the pot wallet. Sweep, claim, pay: three hashes in the table.
Rerun any tide yourself.
This panel does exactly what the tide script does, from the same chain data: it reads the block hash, replays the token's transfer logs into balances at that block, lays out the line and finds where the hash lands. Before launch, paste any pons_v2 token to watch the engine work. Nothing is paid from here.
Reads the block, replays transfers, walks the line. A token with a long history takes a minute the first time and seconds after.
- Block hash
- Eligible wallets
- Winner
- Width
Excluded from every draw: the curve, the pot wallet, the escrow, the burn address and the team's wallets, listed in the script and in this page's source.
Connect, and the page reads your wallet off the chain.
Not a mockup. Connecting requests account access and nothing else. The balance and transaction count come straight from Robinhood Chain over JSON-RPC in your own browser, and your width of the line is computed from the same replay the draw uses.
No wallet connected. Connect one on Robinhood Chain and this panel fills with what the chain says about it.
MetaMask or any EIP-1193 wallet. If the wallet has never seen chain 4663 the page offers to add it, with the public RPC and explorer, and nothing else.
- Account
- —
- ETH balance
- —
- Transactions sent
- —
- TIDE balance
- —
- eth_requestAccounts
- asks for your address
- eth_getBalance
- reads ETH
- eth_getTransactionCount
- reads the nonce
- eth_call balanceOf
- reads TIDE, at launch
- Send a transaction
- absent
- Ask for a signature
- absent
- Request an approval
- absent
A pre-launch site asking for a signature is what a drainer looks like. This one cannot, and you can check the script rather than take that on trust.
Read this part first.
Everything on this page is either live now or a transaction from launch onward. There is no model and no design intent. This table is the state of the project and it is updated before anything else.
| Thing | State | What that means | |
|---|---|---|---|
| Block height, gas, client string | Live | Read from Robinhood Chain over JSON-RPC in your browser, several times a second. | |
| The tide clock and the block that closed each tide | Live | Wall time to the next tide, UTC. Each closing block is found on chain by timestamp. | |
| The draw engine | Live | Runs in your browser now, on any pons_v2 token, from transfer logs and the block hash. Identical to the tide script. | |
| Wallet connect and balance reads | Live | EIP-1193 direct. Your ETH balance and transaction count are read from chain 4663 the moment you connect. | |
| The token | At launch | Live | A fixed-supply ERC-20 launched through pons_v2. One billion units to a bonding curve, no presale, no team allocation. Its address is published here and on X at the same moment. |
| The pot wallet, the sweep, the claim, the payout | At launch | Live | One wallet, watched live on this page. Every tide it sweeps the curve, claims from the pons escrow and pays the winner. Three transactions per tide, each in the table. |
| The size of the pot | Varies | A slice of the creator fees accrued since the last tide. It depends on how much was traded, it is never fixed, and this page never prints a promised number. |
Fixed supply, stated plainly.
TIDE 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.
At 00, 06, 12 and 18 UTC. One winner each, drawn by the block hash, paid on chain.
The creator fee on every trade is what fills the pot. A slice of it goes back to one holder every tide.
TIDE. 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. Live chain reads, the tide clock, the closing block of every tide, and the draw engine running in your browser on any pons_v2 token.
Next
Token launch on pons_v2. The contract address appears here and on X at the same moment, baked into the served HTML.
Then
The first tide after launch. Sweep, claim, draw, pay, with all three hashes in the table and the winner posted on X.
Later
Every tide receipt archived on the page with its three hashes, and the pot script published so anyone can run the same draw.
Straight answers.
Do I need to stake or deposit anything?+
No. You hold TIDE in your own wallet. If it holds at least 100,000 TIDE at the block that closes a tide, it is on the line for that draw. Nothing to deposit, nothing to lock, nothing to collect.
How big is the pot?+
A slice of the creator fees that accrued since the last tide. It depends entirely on how much was traded in those six hours, so it is never a fixed number and this page never promises one. The pot wallet's balance is shown live.
How is the winner chosen?+
By the hash of the block that closed the tide, read as a number and taken modulo the total balance of every eligible wallet. The wallets are laid on a line in address order, each as wide as its balance, and the number lands on one of them. Rerun it in the draw panel above.
Can the team rig it?+
Not the draw. The block hash is produced by the chain, the balances come from the chain's own transfer logs, and the whole computation runs in your browser from public data. What the team does control is the payout transaction, which is why every tide's three hashes are in the table for you to open.
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.
Why six hours?+
Because a pot needs time to fill and a rhythm needs to be one you can remember. Four draws a day at the same four times, so you can set a watch by it, and so it is not mistaken for the eight-minute, four-hour or eight-hour machines already on this chain.
How do I know the address is real?+
It is published in a pinned post on X and on this page at the same moment, baked into the served HTML rather than written in by script. Nowhere before that, nowhere else after. Any address you see anywhere else is a copy.
One wallet, every six hours.
Run the draw on any token, read your own wallet, and watch the clock for a while before you decide anything. The engine is real, the pot is a slice of real fees, and nothing on this page can move a thing.
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.