$REACTOR · solana · autonomous liquidity engine

The machine works.
You watch it print.

An autonomous liquidity engine that claims its fees, harvests the market, and burns the proceeds — live, every minute.

machine room● rehearsal — engine not live
REACTOR core
cycle
0001
interval
60s
rehearsal burn counter
0.00M
boot sequence…
▼ scroll to enter the plant
contract address● pre-launch
TBA — the address will appear exactly here at launch

anything claiming to be $REACTOR before it shows up here is fake.

fault report

Why buyback tokens die

Three structural failures, one machine built to dodge all of them.

fault 01
Dead fees

Every launchpad trade pays ~0.3% to a creator vault. Most creators pocket it or ignore it — holders never see that value again.

fault 02
Circular burns

The usual burn is funded by the token's own volume. Volume fades, burn fades, attention fades. A zero-sum loop dressed up as tokenomics.

fault 03
Invisible agents

Even honest autonomous agents only expose a JSON endpoint. No spectacle, no reason to check back, no retention.

primary loop

The 60-second cycle

Seven stages, no human in any of them. This is the whole product.

CLAIMSweep the creator-fee vault into the machine wallet. ~0.3% of every trade accrues here.
SCANRank trending SOL-paired Meteora pools by volume ÷ depth. Pick randomly from the top 20 — randomness defeats front-running.
DEPLOYSOL goes in single-sided across ~34 bins. Principal becomes protocol-owned liquidity. It is never sold; it compounds.
HARVESTDLMM keeps swap fees separate from principal. The machine claims accrued fees lamport-exact, without unwinding anything.
BUYBACK100% of harvested SOL market-buys $REACTOR through the deepest route. Buyback always executes before new deploys.
INCINERATEBought tokens burn on-chain, on camera. The supply counter only moves one direction.
REPEATNext cycle in 60 seconds. The machine does not sleep.
thermodynamics

Where the money actually comes from

The one diagram that separates this machine from every burn token before it.

Self-referential (everyone else)
own volume
└─▶fee
└─▶buy own token

Pure recycling. Nothing new ever enters the system.

REACTOR's flow
own fees → SOL principal (kept)
└─▶other tokens' traders pay swap fees
└─▶external SOL → buy + burn

Two compounding curves: principal grows every claim, supply shrinks every burn — even in quiet weeks.

harvest model — interactivea model, not a promise
machine buys + burns / day
1.20 SOL
per 30 days
36 SOL
every lamport of it burned, none of it kept

harvest/day ≈ POL × turnover × fee share. POL only grows (creator fees are never sold), so the left slider drags itself rightward over time. Real figures ship with the live ledger — with tx hashes, not sliders.

observation deck

Three surfaces, one machine

Invisible agents get forgotten. This one is built to be watched.

THE MACHINE ROOMreactor.wtf

A live scene that runs the real cycle — intake pulls SOL, the rotor spins on deploy, the incinerator flares on every burn. Rendered from the same public API anyone can read. No wallet needed.

THE MACHINE SPEAKS@reactor_machine

The X and Telegram accounts are the machine's voice. Hourly digests plus instant posts on big events, always in persona.

THE LEDGER/api/v1/*

state · cycles · positions · ledger. Every number carries a transaction signature. If it can't be clicked through to the explorer, it isn't displayed.

control desk
no wallet required to watch
machine states
statetriggervisual
RUNNINGnormal cyclessteady cyan glow
OVERDRIVEholder overclock burnamber flare, faster rotor
SURGEharvest > 1 SOL in one cyclecore flash + instant post
EVOLVINGmilestone crosseda new module bolts on
DEGRADEDvenue/RPC errorsdimmed lights, public banner — never hidden
fuel spec

What the token is — and is deliberately not

without $REACTOR
  • Watch the machine (always free)
  • Read the full ledger + API
  • No stake in supply destruction
  • No name in the room
holding $REACTOR
  • Your volume feeds the intake — the machine runs harder
  • Every burn permanently reduces what circulates
  • Overclock rights: burn to trigger OVERDRIVE + plaque
  • Holder tiers: cosmetics, crew presence, skin votes
deliberately absent
No distributions

machine output is burned, never paid out — cleaner story, cleaner compliance

No staking vault

nothing to lock, nothing to drain

No pay-for-boost

tokens can't buy a bigger harvest; the machine treats all supply the same

crew tiers — cosmetics and access, never power
tierholdingperks
OBSERVER0Full machine room + ledger · Public API access
TECHNICIAN0.05%+Name on shift cards · Cyan plate in the crew list
ENGINEER0.25%+Amber plate + custom crew tag · Vote on machine skins per milestone
CORE CREW1%+Permanent plaque on the machine plinth · First access to fleet slots (Phase 4)
contract facts
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 → AMM pool (SOL-denominated; USD floats)
First cycle
within the hour of graduation
Creator fees
100% → protocol-owned liquidity. Never sold, never withdrawn
Harvest
100% → buyback → burn. The machine keeps nothing
incinerator
the incinerator

Every harvest ends here, publicly. The supply counter only ever goes down.

intake manifold

Three streams, one destination

Everything the machine touches ends as protocol-owned liquidity or smoke.

01live at launch
Creator fees

~0.3% of every $REACTOR trade routes to the machine wallet and deploys as protocol-owned liquidity. This is principal, not spend — it compounds forever.

02live at launch
Swap-fee harvest

Fees accrued to the machine's DLMM positions from other tokens' volume. 100% buys and burns $REACTOR. The machine keeps nothing.

03phase 4
Machine-as-a-Service

Client tokens rent worker engines for their own fees. A 10–20% service fee on each client harvest routes to the $REACTOR incinerator.

team economics, stated openly
  • Dev buys 2–3 SOL at fair launch, same curve as everyone
  • No team allocation, no fee skim, no treasury drain
  • Ops cost (~$50–100/mo) paid out of pocket, never a protocol claim
  • Upside = the same supply math every holder gets
assembly bay

The machine evolves

Milestones are cumulative SOL harvested. The roadmap is rendered in metal, not threads.

v1
launch
IGNITION

bare engine block, one intake, one duct

v2
10 SOL harvested
MODULE 2

second intake + visible fee gauge

v3
50 SOL
MODULE 3

incinerator upgrade — wall-sized burn counter

v4
250 SOL
MODULE 4

catwalks + crew name plates + skin votes

v5
1000 SOL
THE FACTORY

floor expands — fleet bays visible

Overclock console
  • Burn ≥ 100,000 $REACTOR to trigger OVERDRIVE for one hour
  • Amber flare, faster rotor, klaxon lighting — pure spectacle
  • The machine thanks you by plaque name in its next post
  • Your name engraves on the plaque wall, permanently

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

factory floor
v5 — the factory

Endgame: a fleet of worker machines running other tokens' fees, each one feeding the same incinerator.

engineering deck

Inside the engine

Six subsystems around one signer, writing one public ledger.

subsystems
claimer
creator-fee vault sweep
scout
pool ranking + random pick
deployer
single-sided DLMM bins
harvester
lamport-exact fee claims
burner
route → buyback → burn ix
scribe
writes the public ledger
engine → ledger db → public api → room + bot
invariants
  • One signer, server-side only — never in an image or repo
  • Buyback executes before new deploys, every cycle
  • Max 15% of POL in any single pool
  • Errors degrade loudly — DEGRADED state is public, never hidden
  • Ledger rows are written only after on-chain confirmation
attack vs defense
Camp the machine's next pool entrySelection is random from the top 20 — nothing to camp
Sandwich the buybackAggregator routing, many small buys — thin surface
Spam overclockBurn-gated: spam costs real supply
Fake tier statusTiers read on-chain balances at snapshot
Phish via the siteThe site never requests a signature. /me is paste-an-address, read-only
build schedule

Roadmap

PHASE 1● current
IGNITION
weeks 1–2
  • Engine daemon + live test
  • Public API v1
  • Machine room LP
  • Persona bot on X + TG
  • Fair launch → cycle #1
PHASE 2
SPECTACLE
weeks 3–6
  • Milestone evolutions
  • Daily shift report cards
  • Overclock console + plaque wall
  • Holder tiers + crew list
PHASE 3
RESILIENCE
months 2–3
  • Multi-venue worker adapters
  • Rebalance + exit rules, public inventory dashboards
  • Cold-sweep policy, published wallets
PHASE 4
THE FACTORY
months 3–6
  • Machine-as-a-Service fleet
  • Client harvest fees → incinerator
  • Factory floor UI + fleet dashboard
logbook

Decisions on the record

decisionwhy
100% of harvest → buyback → burn"The machine keeps nothing" is the brand
60-second cycleproven cadence, fast enough to be a spectacle
Hourly digest + instant eventsper-cycle posting is spam; a digest gets awaited
Overclock in MVPcheapest mechanic that turns holders into participants
Dev buy 2–3 SOL, pre-statedskin in the game without whale optics
Milestones 10/50/250/1000 SOLfirst evolution must land in week 1
No distributions to holdersvalue via burn only — cleaner on every axis
Paste-address, never connecta site that never asks for a signature can't drain anyone
gauges we watch
  • Uptime % (target: never below 99)
  • Cumulative supply burned %
  • Harvest/day trend (SOL)
  • POL size (SOL)
  • Room DAU + median watch time
  • Shift-card reposts/day
gauges we ignore
  • Price predictions
  • Influencer count
  • Discord member totals
  • Anything without a tx hash
inspection report

The honest take

Machines that hide their gauges melt down. Here are ours, both dials.

holds pressure
  • Burns funded by external volume — works even in quiet weeks
  • Every claim verifiable on-chain since cycle #1
  • POL head start compounds against any later fork
  • The spectacle layer is months of craft a forker won't do
known stress points
  • DLMM positions carry inventory risk — single-sided is not risk-free, and we publish the exposure
  • Launchpad fee structure can change upstream
  • The signer is a hot wallet by design — mitigated, isolated, disclosed
  • Cold start: early harvests are small; the first milestone is set low on purpose
shift change never comes

Your favorite token has a team. Ours has an uptime counter.