martbost 49a0778a53 Post-join sign-in actually works: live position lookup for a cold index, ordered calls, redirect no longer races the signature
#787 registered at 18:35 CT, 22 minutes after the first join-flow fix, and still had no profile. Two
causes, both fixed:

1. messages.verifyChallenge resolved the wallet through chain.memberIdByAccount, which reads the
   CACHED index. Seconds after a registration that wallet is not in it, so the signature was rejected
   with "No RM Circle position is registered to this wallet". It now accepts an idHint (the position
   id from the member's own registration receipt) and, on a cache miss, reads that id live from the
   contract via chain.verifyMember, minting only when the contract says this exact wallet owns it.
   That is a stronger proof than the cache, not a weaker one. Now async; the single call site awaits.

2. join-now.js fired the sign-in and a 4.5s redirect in parallel, so the page could navigate away
   while the wallet was still showing the signature prompt, and it did not wait for submit-id (which
   runs the live verifyMember server-side that seeds the index). It now awaits the report, passes the
   receipt id, and redirects only once the signature settles, with a 120s bailout.

qa/signin-fallback.mjs (7 assertions) proves the cold-index path with real secp256k1 signatures and
covers the abuse cases: a hint for a position the wallet does not own is refused, and a signature from
another wallet is refused. Existing suites still pass: profiles-unit 28, gate-e2e 47.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-16 18:49:33 -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%