martbost
869eee809e
The 600-member milestone went out as plain text into the shared payments topic and Marty scrolled straight past it. Every hundred now posts a picture. The cards are pre-rendered for the whole ladder (600 through 10,000) and carry no live figures on purpose: a number baked into an image rendered weeks early is wrong by the time the mark is reached, so the numbers stay in the caption. The send falls back to plain text if the card for a mark is missing or the caption runs past Telegram's 1024. Separately: a target listed in snapshotTargets with no chat id was skipped without a word, so the "feed" half of every milestone and every daily snapshot has been going nowhere for weeks while the log said it sent. It now warns. telegramChatId is still unset, so feed is still dark until Marty says where it should point, but at least it says so. 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.