Third syndication rail. The first two send impressions; this one sends clicks — a real person picks the offer off the offerwall, goes to the member's link, and has to stay the dwell time before anyone is paid. Two things it does that the other rails can't: - It carries geo-targeted campaigns. DripOffers filters on an explicit country list, so a campaign aimed at Tier 1 finally reaches an outside audience instead of staying on our own site. Tier-3-only campaigns are skipped rather than quietly sent worldwide, because an inclusion list can't express "everywhere except the other tiers" and widening it would deliver exactly the traffic the owner chose to exclude. - Delivery is counted, not derived. It reads rows from the platform's permanent click ledger. It never computes delivery as ordered minus remaining, and pausing never zeroes remaining — that pair is what charged members for impressions that never ran on Network Ad Space. Also fixes two live bugs found while wiring it: the AdRevLinks pause was nested inside the Network Ad Space check in both the end sweep and setStatus, so with NAS switched off an ended or paused campaign kept running on AdRevLinks. Each rail is now checked on its own. Caps: 1,000 credits minimum, 10,000 clicks maximum per campaign. Not for cost — Marty owns the platform and these placements are free — but because the whole site delivers around 2,700 clicks a day, and one campaign booking 50,000 would sit in the list for weeks. Inert unless DRIPOFFERS_BRIDGE_URL and _KEY are set. 26 checks green against the live endpoint; 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.