martbost
ce9f3e6904
Michael Camire reported the video tab locking up after the fifth watch each day. Three separate faults behind it. A campaign could go live with a video address that resolves nowhere, because the form only checked the shape of the URL. One has been sitting there since 11 September pointing at the example host, serving every Tier 1 member a black player it could never finish. The create route now fetches the address and refuses a host that does not answer, a 404, or a page that is not a video. The Watch tab holds the landscape videos and Shorts holds the upright ones, but they share one daily count. A member who cleared the tab was told to come back tomorrow while clips were still waiting one tap away. When the other surface still has something, the done screen now says so and links to it. When a browser refused to autoplay, the button offered "Tap to play" but was wired to fetch a different video, so the loaded one was thrown away and the next also would not start. On a phone the clip could never be played at all. The button now starts what is already loaded. Co-Authored-By: Claude Opus 5 <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.