REACTOR Docs

REACTOR is an autonomous liquidity engine on Solana. Every 60 seconds it claims its own creator fees, deploys them single-sided into trending Meteora DLMM pools, harvests the swap fees those positions accrue from other tokens' volume, market-buys $REACTOR, and burns the lot — publicly, with a transaction hash for every step.

The machine keeps nothing. Claimed fees become protocol-owned liquidity that is never sold. Harvested fees are burned in full. There is no treasury, no staking vault, and no distribution to anyone.

① CLAIM      sweep the creator-fee vault (~0.3%/trade accrues)
② SCAN       rank SOL-paired DLMM pools by vol/depth, random from top 20
③ DEPLOY     SOL single-sided across ~34 bins → protocol-owned liquidity
④ HARVEST    claim accrued swap fees (kept separate from principal)
⑤ BUYBACK    100% of harvest buys $REACTOR via the deepest route
⑥ INCINERATE burn on-chain, on camera
⑦ REPEAT     60 seconds later

Buybacks always execute before new deployments, so income and principal never mix. Randomized pool selection from the top 20 defeats attempts to front-run the machine's entries.

Typical buyback tokens fund the burn from their own trading volume — a loop that dies when volume dies. REACTOR's burn is funded by swap fees that OTHER tokens' traders pay in pools where the machine's SOL sits. New value enters from outside every cycle.

• ▸Principal curve: protocol-owned liquidity grows with every claim and is never sold, so harvests trend up even at flat $REACTOR volume.
• ▸Supply curve: every burn is permanent; circulating supply moves in one direction only.

Supply

1,000,000,000 — fixed, no mint authority

Launch

PumpFun fair launch; 0% team, 0% presale, 0% VC

Dev buy

2–3 SOL on the public curve, pre-stated, wallet published

Graduation

~85 SOL bonding curve (SOL-denominated; USD floats with SOL price)

Creator fees

100% → protocol-owned liquidity, never sold

Harvest

100% → buyback → burn

Deliberately absent: distributions, staking, and pay-for-boost. Value accrues through supply destruction only. Holder tiers are cosmetic and access-based — they never change any holder's economics.

Any holder can burn at least 100,000 $REACTOR to put the machine into OVERDRIVE for one hour: amber lighting, faster rotor, a thank-you by name in the machine's next post, and a permanent engraving on the plaque wall.

OVERDRIVE changes no math, no odds, and nobody's economics. It is a supply sink and a status flex — nothing else.

GET /api/v1/state      uptime · totals · machine state · next milestone
GET /api/v1/cycles     paginated cycle ledger with tx signatures
GET /api/v1/positions  open DLMM positions, per-pool detail
GET /api/v1/ledger     cumulative totals + daily rollups
GET /api/v1/pools      current eligible pool set
GET /api/v1/me/:addr   read-only holder lookup

• ▸All amounts are integer strings (lamports / raw token units) — no floats.
• ▸Responses are { data, meta }, cached 10 seconds, no auth, read-only.
• ▸Every figure carries a transaction signature. If it can't be verified on the explorer, the API doesn't return it.

• ▸The signer is a hot wallet by design — it must sign every minute. It holds only protocol capital: no user funds, no deposits, ever.
• ▸The key lives in runtime environment only — never in a repo, never in an image layer.
• ▸The site never requests a wallet signature. The /me lookup is paste-an-address, read-only.
• ▸Failures are disclosed, not hidden: a DEGRADED machine state is public the moment it happens.

• ▸Single-sided DLMM positions still carry inventory risk when price crosses the machine's bins. Exposure caps (max 15% of liquidity per pool) and public position dashboards mitigate, not eliminate, this.
• ▸The launchpad's fee structure is upstream of the machine and can change.
• ▸Early cycles harvest small amounts — the first milestone is deliberately low (10 SOL) so progress is visible in week one.
• ▸$REACTOR is an experiment, not an investment product. Nothing here is financial advice. The machine's history is verifiable; its future is not promised.