The Cloud Treasury
A fixed 2.5% of every trade routes into a public treasury address.
It buys measured positions in assets that clear a set of hard on-chain filters — never a
discretionary pick, never a single concentrated bet.
Base Network · Autonomous Redistribution
Cloud Seeding Protocol
Trade fees fund a public treasury. The treasury accumulates the assets with real momentum. When the threshold breaks, the entire basket is distributed on-chain to every holder — proportionally, automatically, and without a schedule anyone can front-run.
No Warning. No Calendar.
Hold $STORM. When the threshold breaks, the distribution finds your wallet automatically — no claiming, no staking, no forms.
Reading the barometer
The Protocol
$STORM has no quests, no points dashboard, no bridge requirement, and no snapshot you can game by showing up late. It routes a fixed share of its own trading fees into a treasury, lets that treasury accumulate, and then empties it into every holder at a moment nobody controls.
A fixed 2.5% of every trade routes into a public treasury address.
It buys measured positions in assets that clear a set of hard on-chain filters — never a
discretionary pick, never a single concentrated bet.
There is no date. Distribution fires the block the treasury crosses its threshold value — which depends on trading volume nobody can predict. That's the anti-front-run design: you cannot time an event that has no clock.
Every strike writes a permanent record: the basket, the holder count, the total value, and the transaction hash. Nothing is self-reported — you can reconstruct any past storm from the block explorer alone.
Live Simulation
A working model of the trigger mechanic. Real charge is read from the treasury contract — this runs the same logic on illustrative numbers.
The ring tracks treasury value against the strike threshold. Crossing 100% fires the distribution immediately — same block, no delay, no queue. Then the treasury empties and pressure starts rebuilding from zero.
Illustrative basket. Live strikes draw from whatever the treasury actually holds at trigger time.
System Design
Five components, one loop. Every arrow is a contract call you can trace on-chain — there is no off-chain step where a human decides anything.
Scanner Rules
Every candidate must clear all six filters before a single unit is bought. These are hard parameters, not guidelines — a token that fails any one of them is not purchasable by the contract.
Thin, manipulable markets are excluded outright. Momentum has to be real before the scanner will look at it.
The treasury must be able to exit its position without moving the market against itself or the holders receiving it.
Rules out same-day launches and the majority of rug patterns, which cluster heavily in the first week of a token's life.
No single token can dominate a basket. A bad pick damages one slice of a storm, never the whole distribution.
Every candidate is test-sold in simulation before purchase. Anything that can't be sold back is rejected automatically.
High-tax tokens would erode value in transit to holders, so they're excluded before they ever enter the basket.
No Hand-Waving
Two formulas govern everything. Both are deterministic — given the same chain state, anyone can compute the exact same result.
d(w) = consecutive days held without a net outbound transfer. Charge starts at 1.0×, gains 0.1× per day, and caps at 3.0× after 20 days. Any net sell resets d(w) to zero.
b(w) = wallet balance at the snapshot block. Your slice of a storm is your charge-weighted balance over the charge-weighted total supply held by eligible wallets. Excluded: LP pairs, the treasury, and burn addresses.
Execution Order
Four stages, running continuously — whether anyone is watching the gauge or not.
2.5% of each buy and sell is split off at the router and forwarded to the treasury address. No holder action, no approval, no opt-in — it's part of the transfer itself.
Candidates that clear all six filters are ranked by momentum, and the treasury takes measured positions capped at 15% each. Failing tokens are never purchasable.
Once treasury value crosses the trigger, the engine snapshots every eligible wallet in the same block. Nothing is announced beforehand because nothing is known beforehand.
The basket is distributed by charge-weighted share, the event is written to the log with its transaction hash, the treasury returns to zero, and pressure starts building again.
Loyalty, Not Speed
Every wallet carries a multiplier that climbs while it holds and resets the moment it sells. It exists for one reason: to make buying in right before a storm strictly worse than having been there all along.
Immutable Record
Every strike, permanently recorded. No storm can be quietly skipped, inflated after the fact, or edited once written.
Simulated cloud pressure right now: 0%
Sample records shown for layout. Live entries will each link to their transaction hash.
Verify, Don't Trust
Every claim below is checkable on the block explorer. If you can't verify it yourself, treat it as unproven — including from us.
Pool tokens are sent to the burn address at launch. There is no key that can withdraw the pool, because the ownership of it no longer exists.
No admin key, no proxy, no upgrade path. The parameters on this page are the parameters forever — they cannot be edited after deployment.
Total supply is fixed at deployment. mint() does not exist in the bytecode,
so supply inflation is impossible rather than merely promised against.
The treasury can buy filtered assets and distribute them. It has no withdraw-to-wallet path, so funds cannot be routed anywhere except to holders.
Zero tokens held back for the team. Every unit entered circulation through the same public pool as everyone else's.
Contract source is published and verified on the explorer. Read the distribution function yourself before you trust a word of this page.
Supply
A fixed supply, a burned pool, and a treasury seed whose only job is priming the first storms before fee flow takes over.
Roadmap
Each front either ships or it doesn't — and the storm log makes that impossible to fudge after the fact.
Fair launch on Base. Liquidity locked, LP burned, ownership renounced, zero team allocation.
First storms run transparently and in public so the mechanic is proven before automation.
On-chain loyalty accounting, hardened against wash-selling and snapshot-sniping around a strike.
Fully automated threshold contract — the engine buys and distributes with no lever left to pull.
The candidate list, filter results, and live treasury composition exposed as an open endpoint.
Holders vote the scanner's parameters. The last discretionary input becomes community-owned.
Questions