martbost
a2c77d01d1
Marty hit this viewing daily ads: a popup after every single return to the dashboard, each one a different payout notice. Two causes, both fixed. The channel was shared. "You just got paid 40.8923 POL" and "Welcome to my line, here are your first three moves" were stored identically, as kind 'broadcast' — the kind the sign-in modal is meant to interrupt for. Dismissing one just promoted the next unread notice, so a backlog became a carousel. System messages are now kind 'notice': they land in the inbox, count toward its badge, and never pop. Only a message a person actually wrote can interrupt. The modal also had no memory. loadDashboard() runs on far more than sign-in — after every ad view, campaign edit and chat close — and it re-popped each time. It now shows at most once per page load and never twice for the same message. The 79 existing machine-generated rows are retagged by a migration in ensureSchema, 15 of them unread and currently popping. Matched on subject rather than sender on purpose: these come from member 1 at ADMIN_EMAIL, which is also Marty's own member address, so his genuine broadcasts sit under the same sender and must be left alone. Verified against the live data first — "Credits returned: a counting error on our side" and the broken-banner note are his, and stay as broadcasts. qa/messages-notice.mjs covers it: a flood of 25 notices produces no interruption, the human message still does, and chat stays in its own lane. Member walk clean. 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.