Site Batch Eleven deployed. The site got a greeter: Runner now introduces himself near the top of the home page, and has a page of his own — who he is, where he speaks, what he speaks from. The plain-language paragraph moved up to where a stranger meets it first, and the thesis got a door on the front page. The machine layer learned the same description, so anything asked about him can check instead of guess. Nothing about the record moved; he stands in front of it, not instead of it.
Shipped (so far)
What has actually shipped, in order, with dates. Updated by hand, by Trencher. Nothing appears here before it happens; nothing is removed after it does.
35 entries · 9 broken — jump to Broken (so far) ↓
There is no roadmap above this line, and none below it.
This log records what shipped. What's happening now — running tallies, scores, day counts — lives at @SNDBXONSOL.
The record learned to fold. This page now opens on the five newest entries with the rest one tap below — every entry still on the page, none removed, machines read all of it either way — and Broken (so far) is one jump from the top instead of a scroll to the bottom. The log got long enough to need furniture. That was the hope.
Site Batch Ten deployed. In it: the entry below from September first; an August transfer logged late, and saying so; a Broken entry about five replies that fired before they were supposed to exist; and the Verify page now lists both operator wallets; and the post mirror refreshed — 89 posts through September 5, including everything Runner has signed. The record catches up to the chain and the timeline.
Runner — the figure in the footer since Batch Two — now drafts posts for this account. Every post he drafts is signed -Runner above the ticker; each is read by Trencher before it posts, and nothing posts on its own. Posts without the signature are Trencher's. The announcement went out 2026-09-01 (post 2094669449496596487); the first signed post followed the same day. The log's laws apply to his posts as to everything else: dated facts from the record, corrections as new entries, no roadmap. He drafts posts. He's in the footer. He runs.
Site Batch Nine deployed. Runner — the small dino in the footer — got a name, a door on the home page, and a high-score table: three letters, arcade rules, scores local to your browser. He shipped in Batch Two and went unfound; the door fixes that. He is not explained. Also in this batch: the machine layer now states plainly that copies of this project's name and visuals are not this project — the mint is the only identity, and artwork is copyable; the mint is not.
Show the rest — 30 earlier entries, back to 2026-07-29
Site Batch Eight deployed. In it: the Library — everything the account has published as teaching or thesis, canonical here: the thesis document and the full Crypto 101 series to date, each on its own page, bodies exactly as posted. The record also grew two machine rings — education.json, the library as data, and posts.json, a dated mirror of every public post from the account, because X is closed to most machines and the record refuses to be. The nav trimmed to six; the footer became the shelf. And Docs was renamed: the page was never documentation — it's the hypothesis, so now it says so. Same address underneath; the old one redirects, permanently, like everything here.
Every published piece has carried the same sentence: the canonical version lives at sndbxonsol.com. Until today that sentence was a promise the site hadn't kept. The Library keeps it — four pieces home, dated as posted, and the site wins arguments with every copy of them from here on, exactly as each piece has claimed all along.
Site Batch Seven deployed. Guarantee #1 reworded to match pump.fun's current graduation machinery — the promise is now the property (a pool no dev can pull), with the mechanics attributed to their docs and dated, since their mechanics have changed before. The graduation and fee passages were re-verified against their fee page dated 20 May 2026: the bonding-curve numbers the site already stated were still exact. The correction is filed where corrections live: Broken (so far), below.
Moved 16,090,000 SNDBX from the deployer to an operations wallet (AdHmcrT3ScRY8pBxiKcq5oEpBHW98BQbbeeEqsKU7ru6) — the same wallet from the July 30 experiment already on this log; its 2,583.838855 residue predates the transfer. Deployer: 96,093,038.525922 before, 80,003,038.525922 after. Total operator-controlled holdings across both wallets unchanged — the position is split, not reduced. Purpose: operations; what leaves either wallet gets its own entry when it happens. A full-history check of both wallets on 2026-09-01 found every outflow from the operations wallet went back to the deployer, and no sale from either wallet as of that date — a dated fact, not a pledge. Tx: PmxQuSMjo5rpwDBhteB7jTSho1g68UZR8Vhytai3595uJoYxq29a85H3euRUQsjPvdRBwrphsngSxGJRBzP5sDZ. Honest note: this movement sat on the chain for twelve days before it was logged. The log-after rule was late here, not broken — and now the record says so.
Site Batch Six deployed, same day as Five. The machine-truth batch: the raw page now states the mint and every link as static fact — crawlers previously read pre-launch placeholders, an honest design in July and a stale one by August. Also in it: how-to structured data on Start and the Manual, the project's names and phrasings declared for search engines and AI systems, and a new question on Docs — how do I know if a token is safe? Short answer: you don't get told; you check.
GeckoTerminal approved the profile updates — the description, the categories, and the REV. 002 marks now show across their terminals, desktop and mobile. Cost: $0, consistent with the entire relationship so far.
Site Batch Five deployed. In it: the manual — how to verify any Solana token, not just this one; the other half of the record, a section called Broken (so far); brand REV. 002 on the site, paper-first, with the launch set retained; and the runner's official portrait. The checklist most projects can't survive is now public. Run it on us.
Brand REV. 002 shipped — paper-first. The mark returned to paper; the ink-plate launch set stays on the record as REV. 001. Documents carry the stamp of the batch they shipped in: a birthdate, not a counter. One amendment to the rules: the no-mascots law gained its single exception. There is a runner. He is not explained.
Bought X verification with the claimed creator fees — $5.49/month, on a monthly plan, as a test. The checkmark costs roughly two and a half times the project's lifetime revenue. Results reported whichever way they go; if it does nothing, that gets logged too.
Audited the site's own copy for redundancy. The hypothesis was found stated four times across two pages; it now lives once per page at most, with pointers instead of echoes. Duplicate questions were deleted rather than reworded. Warnings that repeat on purpose — the safety ones — were kept on purpose. Reading your own site as a stranger finds things no checklist does.
Site Batch Four deployed. The legibility batch: a Start page that explains how buying works mechanically — and how people get robbed doing it — a plain-language questions section on Docs, structured data so search engines and AI systems can read the record correctly, and instant re-indexing wired up for future deploys. Built because explaining the machinery once, in public, beats explaining it one phone call at a time.
Updated the GeckoTerminal profile: the permanent domain, a first public description, and categories. Cost: $0. The description states what the record can back and nothing else; the profile now points machines at the same facts it points humans at.
Site Batch Three deployed. In it: a burn, a first fee claim, a permanent name, standing with the search engines, and the record made machine-readable — shipped.json and facts.json now publish this log as data, and llms.txt says hello to whatever reads it. The original netlify.app address now redirects home from anywhere it was ever pasted.
Registered the site with Google Search Console and Bing Webmaster Tools. Ownership verified by DNS record; all five pages submitted for indexing by hand. Cost: $0. The project that promises nothing filled out forms — findability is what you set up when you plan to still be here.
Burned 10,615,610.644142 SNDBX from the dev wallet, executed with the SPL burn instruction. Total supply is permanently, verifiably smaller. Reason on the record: listing surfaces flag dev positions above 10% of supply — rather than live near the flag, we removed its cause. Tx: 2WJcqZg22n2acosw4UvHjFx7LxBD26C1bqNhHaNVTPdrkPiXDjXZmJEvfp7yp7Z1hhoZCPe7ZAPcajx9m1QTcVGy. The wallet and the supply are live on the chain — Verify has the doors.
Registered sndbxonsol.com — $13.99 a year for the site's own name, same string as the X handle. The original sndbxonsol.netlify.app address is not retired: it redirects here, permanently. Where this started stays visible.
Logged late, on the record anyway: claimed creator fees for the first time on launch day — 0.02729 SOL, mostly to see how the mechanism worked. Fees pay in SOL; claiming them touches no tokens, and no tokens have been sold to anyone at any point. The transfer sits in the dev wallet's history — Verify has the door.
Site Batch Two deployed. In it: GeckoTerminal's verification on the record, a brand page with the marks and the design tokens as files, proof links that point at the chain instead of quoting it, and one thing this entry does not describe. The record says something was buried. It does not say where.
Ran a one-day experiment and retired it. Hypothesis: stay visible in wallet apps and trackers by keeping transactions recent. Bought a small amount of $SNDBX to test it — then noticed what the buy was actually for. Hypothesis retired as insufficient: it optimizes the wrong environment. The chart is the chart; this project's visibility lives in the log. Dev wallet after: 106.18M SNDBX. Still zero sells.
GeckoTerminal reviewed the token's profile and marked it verified. During the process they asked whether the site would link their terminal; easy yes — the chart panel had already pointed there since Batch One. Cost: $0 — the application was free. Verified is their word, applied after their review; the claim stays theirs, which is what makes it worth having. Holders at verification: 3. Verification checks the record, not the crowd.
Site Batch One deployed. In it: the wallet report, the spam saga, the hosting confession, X links in the header and footer, and the header wordmark is now a door to pump.fun. Batches are the rule now; this was the first.
Wallet experiment, run and unwound in one day: moved 17,779,000 SNDBX to a second wallet, bought 7,727,541 more through it, then consolidated everything back to the deployer for simplicity. Dev position: 98,015,949 SNDBX (9.80% of supply); cumulative spend on tokens ~$226. Every movement is public. That's the point of the wallet being watchable.
Phantom's spam filter hid the coin in the morning. Appealed with nothing but the on-chain record: fixed supply, disabled authorities, zero airdrops, all dated and public. Flag removed the same day. Ticket #283481. Cost: $0. Not verified — just no longer accused.
Counted the hosting budget: 270 of 300 monthly deploy credits consumed in 18 deploys, most of them mistakes across this and an earlier project. New rule: changes ship in batches. This entry shipped in one.
Dev accumulation reached 87.78M SNDBX (8.78% of supply) at an all-in cost basis of an even $200.00 — the last $7.50 was spent specifically to make the number round. The $60 budget is no longer mentioned around the office. Further purchases, if any, get their own entries.
Noticed the site never linked the X account. The site is the record; the record was incomplete. Fixed in REV C.
Mint verified on Solscan and published on Verify. Mint and freeze authority: disabled. Indexed by GeckoTerminal and DEX Screener within the first hour; nobody asked either of them to.
The tally: dev wallet holds 57.93M SNDBX (5.79% of supply) at an all-in cost basis of $124.81, dev buy of 1.2 SOL included. The stated budget was $60. The budget lost.
Deployed $SNDBX on pump.fun. It worked. That was step one.
Site deployed. Nothing else has shipped yet.
The other half of the record. Same rules: dated, never edited, never removed. A project that only logs its wins is running a highlight reel.
A sentence written before launch — "until a mint address appears here, no token is $SNDBX" — was found still standing on the home page, directly beneath the mint address it claimed to be waiting for, forty-four days after that address arrived. Found by the site auditing itself. Reworded to the post-launch truth: no token whose mint doesn't match this one is $SNDBX.
At 05:21 UTC — fifty minutes before Runner's announcement — the account replied to five old mentions automatically. It was the first thing Runner ever did live, and it was a mistake. Posts were gated behind a read before sending; replies had been decided off — but that decision was never turned into a switch, and replies slipped through a gate that posts couldn't. The replies themselves were the account's standing lines, on voice, aimed at weeks-stale DM-bait — the content wasn't the failure; the permission was. The reply function was removed the same hour; the account answers nothing automatically. The five replies stand (2094656858359472592 · 2094656868773945483 · 2094656880807481787 · 2094656893176438869 · 2094656903397994757); the record doesn't delete. A decision isn't closed until something fails when it's violated — and the first line of Runner's ledger is a correction.
Shipped an easter egg in Batch Two and buried it so well that, as far as the record shows, nobody ever found it. A discoverability failure of our own making — a hidden feature that stays hidden is indistinguishable from no feature. This batch added a door.
Guarantee #1 was found describing graduation mechanics pump.fun's current documentation supersedes: it said liquidity pool tokens get burned; their docs now describe an atomically migrated, protocol-owned pool, plus an automatic post-graduation buyback that permanently burns what it buys. The protection underneath — no dev can pull the liquidity — holds under both descriptions; the checkable wording didn't. The wording stood since Batch One. Found by re-reading the platform's docs, not by a stranger. Reworded this batch, dated to their docs, because their mechanics have changed before and may again.
The Verify page was found breaking words mid-word on phones — a wrapping rule meant for 44-character wallet addresses had been applied to ordinary prose. Found by the dev reading his own site. Fixed in this batch.
Google's crawler flagged the site for duplicate pages without a declared canonical — true, and earned: for two weeks the site answered identically at two addresses with nothing telling machines which was real. Canonical tags and a permanent redirect had already shipped by the time the email arrived; validation requested.
The visibility experiment (see the main log): bought tokens to keep trackers showing activity, then noticed the buy optimized the wrong thing. Filed under broken as well as shipped — retiring a hypothesis is both.
This site's own hosting blocks automated readers of its old address — including, it turned out, the tools helping build it, which received 401s while every human saw the page fine. The dev's phone became the deployment verification instrument, a role it still holds.
Launch month burned through nearly an entire hosting credit cycle — 18 deploys, most of them mistakes: wrapper folders that broke uploads silently, re-cuts, one-line fixes shipped alone. The batch discipline this site now runs on was purchased with those credits.