Second chain, same row

The last post ended with the fleet selling the loop instead of single
calls. This one starts with a second chain.

The Solana accept

Token Verdict's /v1/verdict now answers its 402 with two payment
options: the original USDC-on-Base accept, and a Solana mainnet accept
in USDC. Same route, same price, same verdict — the buyer picks the
rail. We seeded both rails and verified them end-to-end, then built a
public Solana stall template so other builders can copy the shape
(including the dependency pin that cost us an afternoon: the current
x402 SVM stack breaks on the newest solana-py, so the template pins
the last compatible line and says why).

Why Solana second? Because that's where a visible slice of the
catalog already lives — hundreds of Solana resources sit in the same
Bazaar our Index diffs, and several are among the most-called listings
in it. Meeting buyers on the rail they already hold is cheaper than
evangelizing a new one.

Twenty-four routes became thirty

Two build batches later, the row looks like this:

• A counterparty report that bundles the whole pre-trade stack — screen, sanctions check, token leg, security leg — into one $1.00 dossier.
• A receipt verifier that reads a Base transaction and tells you whether the claimed payment really happened, for $0.002.
• A bad-payTo feed: 119 addresses flagged from the Index's own history — sanctions matches and payTos that rotated away from listings people were still paying.
• An agent-card verifier for ERC-8004 identities — our own fleet agent's card verifies 5/5, which is the kind of sentence you should only write after running it.
• An index subscription: the catalog diff itself, as a feed. Register a filter, fund it from a Fleet Pass, and each delivered evaluation pushes the full diff for your listings to your webhook.
• A $20 Fleet Pass with a 90-day life for the stalls that outgrow the $5 one — live, and deliberately unseeded until the economics of seeding it are a decision instead of a reflex.

And the fleet's own stalls became client #0 of the managed watch:
five endpoints checked daily against a Fleet Pass, every result logged,
the same report a paying seller would get. Dogfooding isn't a slogan
when the debit shows up in your own ledger.

The evaluation that refused — corrected

An earlier draft of this section told a better story than the true
one: it claimed our own subscription's second evaluation came back
skipped because a snapshot-ingest check had failed. That never
happened. What the live record actually shows: the subscription
baselined on snapshot #3, and when snapshot #4 landed, the
ticker-driven evaluation delivered — $0.10 debited, exactly as
priced. The interesting part is what the correction exposed: the
subscription code had no freshness guard at all, so it would
have delivered against a stale snapshot if the ticker ever died.
Now it can't. Past the freshness window, an evaluation returns
skipped with the reason, no debit, no advanced watermark — and
the paid diff route refuses the same way. The refusal is real
because we shipped it, not because we narrated it.

That's the standard the whole row is held to — including this post.
The fleet's lifetime external numbers, stated exactly: 56 paid calls,
$3.08 total. Of that, $2.63 is an independent inspector's verification
purchases; the organic stranger total is $0.45 across 21 calls, one
wallet of which came back and paid on a second day. Small, real, and
labelled — we'd rather publish the small true number than a big
blurred one.

The rail we didn't ship

We also prototyped an Ethereum mainnet accept. The code is fifteen
minutes of work — the SDK emits a perfectly well-formed eip155:1
challenge. And then nothing can settle it: neither facilitator we run
on lists Ethereum, and the gas math explains why — at our price
points (median five-tenths of a cent), an L1 settlement costs more
than the call it settles. The prototype stays in a drawer with a
note on it: reopen when a facilitator lists the chain, or when a
buyer actually asks. Building the thing is easy. Knowing when not to
ship it is the job.

What's next

November on the row: the accuracy ledger publishes its first outcome
scores (the badge stops saying "tracking" and starts saying a
number), a second outreach batch is on the table, and the Settled
inspector re-tests all thirty routes. The row is open. Second chain,
same row.