martbost
415a5f3848
Marty (2026-09-19): partner codes keep working with no monthly cap, but the credits stop being a dump. A fifth is paid the day the code is redeemed, then a fifth on each day the member finishes their daily ad set, five days in all, and whatever is unclaimed 30 days after redemption is never paid. Same headline number for the partner to promote; paid only to people who show up. 49 of the 52 PARTNER redemptions were still sitting on 500+ unspent. Every redemption now records the site the ?promo= link was opened from (iap.promoref cookie set from the Referer at link-open), so a code's traffic can be attributed to the partner page it was supposed to come from. Member-funded codes charge the funder one installment at a time; a short funder leaves the installment due, not lost. Pre-drip redemptions were paid in full up front and are marked paid=credits at start-up, so nothing is paid twice. Covered by a module test (13 checks: per-day cadence, gaps, rounding, expiry, pre-drip rows, declined payer) and an end-to-end HTTP test on a local copy (9 checks). Co-Authored-By: Claude Fable 5.1 <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.