The OreOS manual
Every rule of the hourly race, written down. If this page and the contracts ever disagree, the contracts win, and this page is fixed.
Status: pre-launch. Nothing described here is deployed yet. Numbers on this page are rules and models until launch.
start here
What OreOS is
OreOS is an operating system in your browser that runs one proof-of-work race every hour on Robinhood Chain. Miners hash; the heaviest hash found in the hour takes that hour's block, paid in ETH from the coin's own trading fees.
- Blocks are ETH, sent by a contract to the reward address. There are no points and no balances on a server.
- Every hash is checked on chain. The contract recomputes it before it counts.
- No new coins are ever minted: blocks come from the creator fee of $OREOS trades.
- Locked $OREOS adds weight to a wallet's hashes, never more than +3 bits.
rules
Hourly race
Windows
A window is one UTC hour, from hh:00:00 to hh:59:59. Its seed is the hash of the first chain block of that hour, so nobody can know it, or start mining it, before the hour begins.
What every miner hashes
sha256( seed[32] ‖ rewardTo[20] ‖ window[8] ‖ pad[4] ‖ nonce[8] ) = 72 bytes
The reward address sits inside the message. A nonce found for one address is worthless to any other, so copying a pending transaction gains nothing, and anyone may send a record on a miner's behalf.
Submitting a record
- 1A miner finds a hash heavier than the window's current record.
- 2It calls submit(nonce, rewardTo). The contract recomputes the hash with the SHA-256 precompile.
- 3The hash must have at least 24 leading zero bits, and must be heavier than the record. Otherwise the call reverts and the sender pays the network fee.
- 4The new record is stored and announced in an event.
Closing the hour
- 1After hh:59:59, anyone can call settle(window). The first submit() of the next window settles the previous one too.
- 2The record holder receives 99% of the block; whoever settles receives 1%.
- 3A block is 5% of the Block Pool at the moment it settles.
- 4No record of 24 bits or more in a window: no block. The pool keeps it for the hours that follow.
math
Weight, and the exact rule
weight = leading zero bits of the hash + bonus bits (0 to 3)
The heavier weight holds the record. On equal weight, the smaller 256-bit hash value is heavier, so ties never stand.
Your expected share of blocks
your hashes × 2^(your bonus bits) / Σ every miner's hashes × 2^(their bonus bits)
- 24 zero bits
- one hash in 16.8 million
- 32 zero bits
- one hash in 4.3 billion
- 40 zero bits
- one hash in 1.1 trillion
- 48 zero bits
- one hash in 281 trillion
The heaviest hash after N tries sits near log2(N) bits. A gaming GPU in a browser tab at about 2 GH/s reaches about 43 bits in an hour; a top GPU on the native miner at about 20 GH/s, about 46; a whole network at 500 GH/s, about 51.
The Assay on the landing page runs these formulas for any hashrate, bonus and volume. It is a model of the rules, not a forecast.
fees
Strongbox
The Strongbox is the Vault contract, and the creator-fee recipient of $OREOS on the launchpad. Fees arrive in ETH: 70% of the launchpad's 1% curve fee plus the 2% creator tax, about 2.7% of every trade.
- pull() claims accrued fees from the launchpad's fee escrow. Anyone may call it; settle() calls it too.
- Every pull is split 80 / 10 / 10 in the same transaction.
- With inflow F per hour, the pool settles near 20 × F, and each block near F.
- burn() lowers total supply on chain. Nothing is parked at a dead address.
- Ops is paid only to the published ops address, with a memo kept in the event.
token utility
Lock-to-boost
- 1,000,000+ $OREOS locked
- +1 bit · same as 2× hashrate · Prospector
- 5,000,000+ $OREOS locked
- +2 bits · same as 4× hashrate · Foreman
- 20,000,000+ $OREOS locked
- +3 bits · same as 8× hashrate · Engineer
- A lock counts from the next window after it lands.
- Minimum lock: 7 days. requestUnlock() ends the bonus at once; withdraw() works 7 days later.
- The bonus stops at +3 bits. Coins weigh hashes; they never replace them.
- Holding without mining pays nothing. A lock is never a share of fees.
how to
Mining: tab, rig, phone
In a browser tab
- 1Open the OS and connect a wallet. It becomes the reward address.
- 2miner.exe makes a session key in this browser. Top it up once with about 0.001 ETH; it pays the network fee for each record, so no wallet pop-up per record.
- 3Press Start. The OS uses WebGPU when the browser has it, CPU threads when it does not, with an intensity slider.
On a rig
The native miner is open source, with CUDA, Metal and OpenCL builds. It reads each window's seed from the chain and sends its own records with its own session key. Same contract, same rules.
Landing-page demo
miner.exe on the landing page runs a real SHA-256 search over the same 72-byte message, for five seconds, on one CPU thread, against a demo seed. Nothing is submitted anywhere.
A session key holds a little ETH in your browser. Anyone with access to that browser can use it. Keep the amount small.
on chain
Contracts
- HourRace
- windows, submit(), settle(), records
- OreVault (the Strongbox)
- pull(), the 80 / 10 / 10 split, burn(), ops payments
- OreLock
- lock(), requestUnlock(), withdraw(), bonus(address, window)
- $OREOS
- the launchpad's standard token, with a public burn()
- No owner and no pause in HourRace, OreVault or OreLock. Their parameters are constants.
- Changing the split would need a new Vault, announced and timelocked; the old split keeps running until then.
- Addresses are published here and on the landing page at launch, and nowhere else.
The launchpad's owner can change any coin's fee recipient after a 3-day timelock. The docs will show the live recipient, and the OS raises a banner if it ever changes.
facts
Token
- Name / ticker
- OreOS / $OREOS
- Chain
- Robinhood Chain (EVM, chainId 4663)
- Supply
- 1,000,000,000, fixed at launch
- Launch
- 100% through the launchpad's bonding curve
- Presale, private round, team allocation
- none
- Graduation
- at 4.2 ETH of curve reserve, into a pool
- Creator tax
- 2%, paid to the Strongbox
- Emissions
- none, ever
The team buys on the open curve like anyone else.
records
Hall, badges, seasons
- Heaviest hash ever, with its address, window and digest.
- Heaviest today and this week; most blocks this season; longest streak of consecutive windows.
- First Block
- took a block for the first time
- Overtime
- a record set in the last 60 seconds that stood
- Deep Vein
- a record of 48+ zero bits
- Night Shift
- a block between 00:00 and 06:00 UTC
- Clean Sweep
- three blocks in a row
- Comeback
- took the record after another address held it for 45+ minutes
A season is one calendar month (UTC). Boards reset each season; the all-time Hall never does. Lock tiers vote on one season rule from a short list. Money rules are never on the ballot.
anti-gaming
Ways to cheat, and why they fail
- Copy someone's nonce
- worthless: the reward address is inside the hash
- Mine a window early
- impossible: the seed is the window's first chain block
- Lock at the last second
- a lock only counts from the next window
- Flood the contract
- below 24 bits or not heavier: reverted, sender pays the fee
- Split into many wallets
- no gain: weight comes from hashes
- Outbid at hh:59
- the chain's sequencer orders by arrival, not by fee
- Fake a device name
- device names are shown for fun and decide nothing
survey
Roadmap
Phase 1 · weeks 0-3 · now
- Contracts tested on a mainnet fork over 200 simulated windows
- Browser miner (WebGPU + CPU), native miner v0.1
- The OS: miner, race, strongbox, lock, hall, docs
- Launch with the Strongbox as the creator-fee recipient
Phase 2 · months 1-2
- Tab Pool: browser miners pooled, paid per share
- Native miner on Metal and OpenCL
- Badges, seasons, block cards
Phase 3 · months 2-4
- Daily Heavy: one 24-hour window with its own pool
- Stock blocks (option): a block paid in a tokenized stock, if the route holds up in testing
Phase 4 · months 6-12
- Race Kit: any new coin can run its own hourly race
- Partner races inside the OreOS desktop
- A public race data API
said out loud
Risks
- Rented GPUs and big rigs will take most blocks. That is how proof of work behaves; the Tab Pool is the answer for laptops and phones.
- Block size follows trading volume. A quiet coin makes small blocks.
- Mining uses electricity and wears hardware. Most hours, most miners take nothing.
- The launchpad's owner can change a coin's fee recipient after a timelock.
- Nothing is deployed yet. Contracts can have bugs; they are tested on a fork before launch.
faq
Questions
Do I need $OREOS to mine?
No. Anyone can mine and take blocks at base weight. A lock only adds bonus bits.
Where does the ETH come from?
From the creator fee of $OREOS trades on the launchpad, which goes to the Strongbox. No trades, no new ETH.
Why the heaviest hash and not the first?
A first-past-a-target race needs a difficulty that retunes as miners come and go. A heaviest-in-the-hour race needs none, sends few transactions, and keeps one block per hour no matter how many miners show up.
Can a phone take a block?
Yes, in proportion to its share of the hour's weighted hashes. Rarely, and for real. The Tab Pool in Phase 2 turns rare blocks into a steady trickle.
What if nobody mines in an hour?
No record of 24 bits or more means no block. The ETH stays in the pool for the hours that follow.
Can the team take the Strongbox?
No contract holds an owner key over funds. Ops receives 10% of each pull, to one published address, and every payment is on chain with a memo.
OreOS is experimental software. Mining uses electricity and wears hardware. Blocks depend on trading volume and on everyone else's hashrate: most hours, most miners take nothing. Nothing here is financial, investment, legal or tax advice. $OREOS is a utility token: a lock adds weight to the hashes of the wallet that holds it. It confers no ownership, profit share or claim on the Vault, on any entity or on any asset. Burns are a protocol mechanism, not a payment to holders. Community project, not affiliated with Robinhood, any launchpad, exchange or social network.