Journal and data formats

The two files the site reads.

status.json

Rewritten at every pass: updatedAt, live, chain, mint, devWallet, venue (curve or pool), dropPct, price, peak10min, defenseSol, claimedSol, boughtSol, burnedTokens, buys.

journal.json

The last 500 events, oldest first. Three kinds:

{ "t": 1791974044, "type": "claim", "claimed": "0.058676", "tx": "5x..." }

{ "t": 1791974171, "type": "buy", "spent": "0.029500", "tokens": "1006887429922",
  "venue": "curve", "priceBefore": 4.1e-8, "peak10min": 1.1e-7, "dropPct": 63.0, "tx": "3k..." }

{ "t": 1791974172, "type": "burn", "tokens": "1006887429922", "tx": "4q..." }

Checking an entry

Open the transaction on Solscan. A claim shows a collect-creator-fee instruction into the dev wallet. A buy shows a buy on the coin. A burn shows a burn of exactly the same amount.

state.json

The runner's own memory: the energy reserve count, totals, the price readings of the last 10 minutes and any burn still pending. It lets a restart carry on without forgetting a recent high.