martbost
1b41823745
The live feed sat silent from 17:58 UTC on 24 September: seven hours of
registrations, upgrades and payouts unannounced. Two faults, one storm.
First, publicnode cut its getLogs range below the 9,000 blocks the tail asked
for ("invalid block range params"), so the tail failed on its own. Second, the
daily snapshot was due. It is ~3,600 calls; it failed part-way on publicnode's
per-IP limit (the site, the IAP app and the cron watchers all share core's one
IP), snapshotAt never advanced, and the next tick started it again from
scratch. Because the snapshot ran BEFORE the tail, every failing attempt also
stopped every live event. 1rpc, the only fallback, had exhausted its free
allowance. The retries were the storm that starved everything else on the IP,
the IAP burner included.
Now: chunk 2000 (measured on publicnode and tenderly), four providers rotated
per call instead of camping on the last one that worked (all four measured
from core; polygon-rpc.com, ankr, blastapi and blockpi refuse), the snapshot
paced at 200 ms per member so it stays under every limit, and a failed
snapshot backs off 30 minutes while the tail runs regardless. A snapshot can
be late; it can no longer make the feed lie by omission.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
RM Circle Premium — Crypto Team Build Sponsor Router
A small deployable Node/Express app with:
/— evergreen advertising/bridge page/start— dynamic onboarding page with the current team sponsor/admin— password-protected sponsor queue manager- JSON-file persistence suitable for a Docker volume
Core workflow
- Traffic lands on the evergreen bridge page.
- Visitors click Get Started.
/startreads the active sponsor from the server and builds the RM Circle referral link dynamically.- In
/admin, increment a sponsor's direct count as joins are verified. - When a sponsor reaches 2, click Qualified.
- The next waiting sponsor becomes active immediately—no HTML or ad changes required.
Default seeded queue
The seed data reflects the working Crypto Team Build priority list at build time:
- ID 30 — Orlando (active)
- ID 36 — Mad Dog
- ID 35 — Michael Camire
- ID 32 — Melissa
- ID 34 — Janie
You can change, reorder, add, or delete sponsors in /admin.
Local run
cp .env.example .env
# edit .env and set a strong ADMIN_PASSWORD + SESSION_SECRET
set -a && . ./.env && set +a
npm start
Open:
http://localhost:3000/http://localhost:3000/starthttp://localhost:3000/admin
Docker / Coolify
This project includes a zero-dependency Node server, Dockerfile, and docker-compose.yml. No npm package download is required.
Coolify recommendation
- Create a new application from this source/repository.
- Use the Dockerfile or Compose deployment.
- Add environment variables:
ADMIN_PASSWORD— strong unique passwordSESSION_SECRET— long random stringNODE_ENV=productionDATA_DIR=/app/data
- Persist
/app/datausing a volume. - Point your domain/subdomain at port
3000through Coolify's normal proxy/domain configuration. - Open
/admin, sign in, and verify the queue before sending traffic.
Sponsor referral URL
The default base is:
https://app.thermcircle.com?ref=
The app appends the current sponsor ID, for example:
https://app.thermcircle.com?ref=30
Change the base URL at any time in Admin → Public Page Settings without editing code.
Important operational behavior
The app intentionally does not auto-qualify sponsors based on clicks or blockchain activity. A team admin verifies the actual placement and clicks Qualified. This prevents an ad click or abandoned transaction from rotating the sponsor queue incorrectly.
Safety and compliance notes
The public pages include risk language, avoid guaranteed-income claims, and remind users never to disclose a MetaMask Secret Recovery Phrase. The onboarding page points to the official MetaMask website and identifies Polygon Mainnet as chain ID 137 with POL as the native gas token.
This app does not custody crypto, request wallet seed phrases, execute transactions, or store private keys.