martbost
0a50d07658
The daily meter charged 100 credits for every day a campaign was shown, with no end date. It produced 74-day queues, and worse, each new campaign added 100/day of charges while adding no inventory: on 18 September, 15 campaigns were charged 1,500 credits against a platform that had produced 367 login impressions in its entire life. That had stopped being a pricing inefficiency and become members paying for delivery that did not exist. Now: 3,000 credits buys 30 days of unlimited impressions, charged once at purchase, with no delivery promise — the model Marty wanted, matching how ClickBaitPays sells theirs. The price is deliberately identical to 30 days at the old daily rate, so nobody pays more than before; they just get a known end instead of an open-ended drain. It reuses the `featured` shape, which was already a flat up-front buy that runs to `expires`. Both daily meters — MySQL and JSON — now skip any campaign with an expiry, so a slot can never be metered. The existing sweep closes it on day 30 and returns anything unspent. qa/login-slot.mjs, 9 checks, including that the slot price still equals 30 days at the old rate and that neither meter can touch a slot campaign. 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.