martbost
b061053ccf
today() was a UTC day, which rolls over at 7 PM Central. Sign in at 6:55 PM and again at 7:05 PM and those were two different days, so the once-per-day sign-in bonus paid twice, ten minutes apart. On the live ledger 83 of the first 364 sign-in bonuses landed less than 24 hours after the previous one, one pair 24 minutes apart, worth 618 credits. The same boundary governs the daily-credit claim, the claim streak, each campaign's daily spend cap and the login-ad daily meter, all of which could turn over twice in one Central evening. ctDay() puts every member-facing daily rule on America/Chicago, which tracks CST/CDT on its own. Reporting slices elsewhere are left alone rather than re-bucketing chart history. The bonus also records login_ts now and refuses to pay again inside 20 hours, whatever the day string says. 20 rather than 24 so signing in at the same time each morning never skips. Safe to deploy between midnight and 7 PM Central, when the two day strings agree. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
InstantAdPay — site
Membership advertising with immutable on-chain settlement. Zero-dependency Node server (RM Circle pattern): static pages + JSON API + SSE ledger.
Architecture
server.js— http server: pages,/api/*,/join/<id>sponsor links, SSE feedchain.js— contract reader + persistent event indexer (free public RPCs)auth.js— SIWE wallet sign-in (EIP-4361), sessions in the volumeaccounts.js— site-side records only (free members, last-touch sponsor attribution, handles). The CHAIN is the source of truth for money/credits.public/— landing, live ledger, member area; no client libraries
Chain flip (rehearsal → mainnet)
Everything chain-specific lives in data/config.json (volume):
{contract, chainId, chainName, explorer, rpcs, deployBlock}.
Defaults point at the Amoy rehearsal deployment. Launch = deploy the
mainnet contract, wipe accounts.json/sessions.json/chain-index.json,
PATCH /api/admin/chain with the mainnet values, set rehearsal:false via
/api/admin/site. Same code, different config.
Run
PORT=3100 node server.js # DATA_DIR defaults to ./data
Admin API auth: Authorization: Bearer $ADMIN_PASSWORD.
Spec: ../CONTRACT-SPEC.md (v1.0.3-frozen). Contracts: ../contracts/.
Chatbot knowledge is part of every change
chatbot.js answers members two ways: CANNED regex answers and systemPrompt() for the AI. Any
change that a member could ask about (a new pane, a rule, a price, a limit, a fix they noticed) is not
done until both are updated in the same commit, and KNOWLEDGE_DATE in chatbot.js is bumped. The QA
runner (bash qa/run.sh public) fails when a release note on the live site is newer than that date.