martbost 4982897613 Fix missing "who joined / what they unlocked" alongside payout alerts
Marty saw a payout land in the team topic with no registration event beside
it. Confirmed on-chain: #254 registered at 12:49 and the referral payout to
#237 fired at 12:49 — the payout announced, the registration did not. #254 is
inside the org, so the team filter was not the cause.

The bug: registered/upgraded were emitted only when the member was NEW to our
state, or when their stored level was lower than the log said. That conflates
"is this member new to us?" with "have we announced this event?". A snapshot
reads member storage straight from the contract, so if one lands between
someone registering and us scanning that block, the member is already on file
and the announcement is silently skipped — while the payout it triggered goes
out regardless. Exactly the asymmetry reported.

Now keyed on the on-chain event itself (tx + type + id), so each announces
exactly once no matter which code path notices it first. The scan window
still bounds it — we only look past lastBlock — so it cannot replay history.
The set self-trims at 4000 keys.

Also fixed while here: the upgraded event never set `level`, only `newLevel`,
while every consumer reads evt.level. The unlock text only worked because it
could fall back to resolving the level by NAME.

Payout announcements are deliberately untouched: their dedupe depends on
snapshot rows having no tx, so keying them this way risks announcing historic
payouts to everyone.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-29 07:57:11 -05:00

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

  1. Traffic lands on the evergreen bridge page.
  2. Visitors click Get Started.
  3. /start reads the active sponsor from the server and builds the RM Circle referral link dynamically.
  4. In /admin, increment a sponsor's direct count as joins are verified.
  5. When a sponsor reaches 2, click Qualified.
  6. 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:

  1. ID 30 — Orlando (active)
  2. ID 36 — Mad Dog
  3. ID 35 — Michael Camire
  4. ID 32 — Melissa
  5. 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/start
  • http://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

  1. Create a new application from this source/repository.
  2. Use the Dockerfile or Compose deployment.
  3. Add environment variables:
    • ADMIN_PASSWORD — strong unique password
    • SESSION_SECRET — long random string
    • NODE_ENV=production
    • DATA_DIR=/app/data
  4. Persist /app/data using a volume.
  5. Point your domain/subdomain at port 3000 through Coolify's normal proxy/domain configuration.
  6. 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.

S
Description
RM Circle Premium - evergreen bridge page + dynamic Crypto Team Build sponsor router
Readme 715 MiB
Languages
JavaScript 65.9%
HTML 33.9%
Shell 0.2%