CHAOTROPY · THE ON-CHAIN ENTROPY ENGINE · SOLANA DEVNET
Chaos, put to work.
Chaotropy is an autonomous fee engine on Solana. Every $CHAO swap on the main pool pays a toll; the toll accumulates inside the vault as free energy; anyone can discharge it — one permissionless strike every 60 seconds. Each strike settles 40/40/10/5/5 across burn, stocks, ops, depth and chaos. No keys. No votes. No backend.
Energy discharged · all time · USDC
01THE ENGINE
Disorder, routed
A swap pays its toll
Every $CHAO swap on the main pool pays a 4.2% toll; a quarter of it — 1.05% — accrues to the protocol inside the pool, owed to the vault. Between strikes the energy only accumulates. Nothing leaks, nothing is scheduled.
Anyone discharges it
harvestClaim() is permissionless — any wallet, from anywhere, no allowlist.
The caller pockets 0.25% of the claim plus rounding dust as a keeper reward.
A cooldown rate-limits the engine: 60 seconds on devnet.
The split executes
40 / 40 / 10 / 5 / 5 — hardcoded constants, not settings. Minimum claim, per-route minimums and integer dust guards keep the arithmetic honest to the last base unit.
Every route runs alone
Guards validate before a lamport moves; each route runs as its own instruction. A stale feed or thin pool soft-skips — that route's share stays pending, the strike never halts, and the ledger records every skip.
02FLUX
The entropy ledger
03THE SPLIT
Five routes. One law.
R/1 · BURNBuy & burn
The heaviest route buys $CHAO back on the open pool and burns it in the same strike. Supply only ever falls through this route — every strike tightens the float.
04THE ESTATE
Nine stocks, held by bytecode
| ticker | feed price | status | pool |
|---|
05TELEMETRY
The engine, measured
06SAFEGUARDS
Walls, not promises
TWAP drift gate
Before any pool trade, spot must sit within ±3% of the 30-minute TWAP. Manipulation inside the window is refused, not punished.
Feed staleness & pause
Stock routes skip any asset whose oracle is older than 15 minutes, paused, or negative. Skips are ledger events, not errors.
Pool impact cap
No single route moves more than 0.5% of a pool per execution. Oversized amounts batch across future strikes.
Soft-skip isolation
Guards validate first, then each route runs as its own instruction. A failing route
emits RouteFailed and holds its funds pending — never takes the strike down.
Timelocked custody
Fee-recipient and dev-treasury changes need a request/confirm delay — 60 seconds in this devnet edition. The world watches the intention first.
Self-auditing ledger
INV-1 asserts claimed = keeper + pending + paid after every strike. INV-4 asserts the vault holds zero $CHAO when the dust settles.
07QUESTIONS
The fine print
Q1What exactly is Chaotropy?
Q2Why "Chaotropy"?
Q3Who can call the strike?
Q4What happens if a route fails mid-strike?
RouteFailed entry lands on the ledger, the amount
stays pending for that route, and every other route completes normally.
The failed amount retries next strike.Q5Are the stock positions real?
Q6Why does 5% go to "chaos"?
Q7Can the weights or destinations be changed later?
Q8When mainnet?
The energy is accumulating.
Every strike, every route, every skip lands on-chain where anyone can read it. Open the console and run the discharge yourself — follow the account for the launch signal, read the program for everything else.
- announcement channelx.com/chaotropyfun
- home of the enginechaotropy.fun
- the split · fixed40 / 40 / 10 / 5 / 5
- keeper reward0.25% + dust
- cooldown · devnet60 seconds
- keys heldnone that matter