Ring the bell
…Permissionless keeper call. Claims the pool fees and fires all five routes in one transaction.
Next window—
Min claim—
connect a wallet to ring it
AUTONOMOUS TREASURY · ROBINHOOD CHAIN TESTNET
WE HARVEST EVERY FEE.
Harvex picks up every toll the pool pays and sticks it somewhere useful — 40% buy & burn, 40% stock reserve, 10% dev ops, 5% liquidity, 5% pure chaos. The weights live in bytecode. Nobody decides. Nobody refunds.
Harvested to date—
$HARVEST burned—
Live supply—
reading chain…
The Split
Every harvest cracks the pot into five fixed routes. The numbers below are live from the vault ledger.
40%
Buy & Burn
market buys, then fire
— · —
40%
Stock Reserve
nine equity orbits
— · —
10%
Dev Ops
timelocked treasury
— · —
5%
Liquidity
paired & seeded back
— · —
5%
Chaos
one-way trip, burned
— · —
Playground
Live testnet, same bytecode that flies on mainnet. Anyone can keep the wheel turning.
Swap
main poolEst. out—
no wallet
Sticky notes
vault log- loading events…
The Field
40% of every harvest is planted into nine perpetual stock positions — half swap, half LP, guarded by feed-staleness and drift checks. Testnet runs on simulated feeds; mainnet plugs into real Robinhood Equities prices.
| Ticker | Feed price | Status | Position pool |
|---|
Guards
Autonomy without fuses is just liability. Six of them, each independently testable.
G/01TWAP drift gate
Before any pool trade, spot must sit within ±3% of the 30-minute TWAP. Manipulation inside the window is refused, not punished.
G/02Feed staleness & pause
Stock routes skip any asset whose oracle is older than 15 minutes, paused, or negative. Skips are events, not errors.
G/03Pool impact cap
No single route moves more than 0.5% of a pool per execution. Oversized amounts batch across future harvests.
G/04Rollback isolation
Routes run as external self-calls under try/catch with a 4M gas cap. A failing route leaves its funds pending — never takes the harvest down.
G/05Timelocked custody
Fee-recipient and dev-treasury changes need a request/confirm delay — 24 hours on mainnet. The world watches the intention first.
G/06Self-auditing ledger
INV-1 asserts claimed = keeper + pending + paid after every harvest. INV-4 asserts the vault holds zero $HARVEST when the dust settles.
Sticky questions
What exactly is Harvex?
An autonomous treasury token. $HARVEST trades on a pool; the pool fees are periodically claimed by a vault contract and split along five hardcoded routes — buy & burn, stock reserves, dev ops, liquidity, chaos. No human in the loop, no off-chain infrastructure: the whole flywheel is bytecode.
Who can call harvest?
Anyone, from any wallet. The caller receives 0.25% of the claim plus rounding dust as a keeper reward. Harvests are rate-limited by a cooldown — 60 seconds on testnet, one hour planned for mainnet.
What happens if a route fails mid-harvest?
Nothing catastrophic — by design. Each route executes as an isolated external call wrapped in try/catch under a gas cap. If it reverts (stale feed, drift gate, thin pool), the amount stays
pending for that route and every other orbit completes normally. The failed amount retries next harvest.Are the stock positions real?
On testnet they're simulated — mock feeds push plausible prices for SPY, NVDA, TSLA and six others so you can watch the routing work end to end. On mainnet the same code consumes real Robinhood Equities price feeds and real position tokens.
Why does 5% go to "Chaos"?
A treasury that can only do sensible things is a treasury that can be modeled, front-run and farmed. The chaos orbit buys a volatile side asset and burns it — deliberately inefficient value that keeps the system from becoming a deterministic payoff matrix.
Can the weights or destinations be changed later?
Not by any key we hold. The split lives in the vault's bytecode as constants. The owner role can rotate operational parameters (cooldowns, caps, asset list) — all timelock-protected and visible on-chain — but re-weighting would require deploying an entirely new protocol nobody is obliged to follow.
When mainnet?
After the external audit completes and timelocks are extended to production values. Watch @harvexdotfun — the launch announcement is the only signal worth trusting.