Per Marty: (1) added a real, on-chain-verifiable worked example — user
#46's actual payments climbing generation by generation with exact
amounts (entry 163.12 + 1st upgrade 310.70 → Gen1 #30; 2nd 621.40 →
Gen2 #24; 3rd 1,242.80 → Gen3 #21), names omitted; (2) a "deeper =
later but bigger" principle scene; (3) an "it all flows up to you" org
pyramid capstone that works at every level. Now 10 scenes ~3.4 min.
Re-encoded over the same /v/ filename.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Per Marty's field observation (Orlando #30 / Neville #46,#49 see direct
payments flowing but don't grasp the upgrade ORDER): reworked into 7
scenes adding (1) a generations ladder — each generation pays you at a
DIFFERENT upgrade (Gen1→1st→Ascensus ... Gen4→4th→Apex), and (2) a
pass-up routing chain — the payment travels UP, skips the wrong-gen /
unqualified positions, and lands on the first one that's qualified +
leveled. Re-encoded over the same /v/ filename.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New ~96s teaching video in Marty's voice for confused team members who
expect rewards but aren't getting them. Clarifies the two mechanisms:
direct rewards (only from people who join on YOUR link — spillover
doesn't pay you) vs upgrade pass-ups (travel up, skip you unless you're
qualified + leveled). Includes a 3-point self-diagnosis. Hosted at an
unlisted /v/ path; CTA rmcircle.team.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New chain.getOrgRouting(rootId, ownerIds) simulates the contract's
_payUpline routing for every member below the org root on their NEXT
upgrade, classifying where the POL lands: your positions, a teammate
in-org (healthy), an outsider above the org (true LEAK), or fees.
Surfaced on /api/admin/income and rendered as a panel in "My Positions
— Income": 4-stat summary + expandable list of payments escaping the
org. Distinguishes real leaks (money leaving the team) from teammates
earning — which the old upgrade-needs alert conflated.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The two cards had different body-text lengths, so the CTA pills sat at
different heights. Made .card a flex column and pushed .pill to the
bottom (margin-top:auto), so both buttons align. Re-encoded over the
same /v/ filename.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Marty switched the domain from rmcircleteambuild.com to rmcircle.team
(bought at NameSilo). Updated v3 (spoken URL + end caption) and v1
(on-screen URL + scene-6 voiceover). Both re-encoded over their existing
/v/ filenames so shared links stay stable. Site/tweet CTAs remain on
rmcircle.saasy.top until DNS is live tomorrow.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Dot pyramid (4 gens) on the left; 8-level ladder on the right with real
amounts through Apex and Fastigium/Vertex/Corona ascending (↑) so it's
complete without headlining ~40K POL. Panel raised above the caption
band so all 8 rows + the "not a promise of income" note stay clear.
Combined cut re-encoded over the same /v/ filename.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Domain lands tomorrow; both domains will serve the site (old kept live
indefinitely). v3 combined cut: spoken URL + clean end caption now read
rmcircleteambuild.com. v1 designed-scenes: on-screen URL + regenerated
scene-6 voiceover updated to the new domain (kept its original wording).
Both re-encoded over their existing /v/ filenames so shared links are
stable. Tweet CTA + site links stay on rmcircle.saasy.top until the new
domain is live tomorrow.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The spoken URL is still spelled for clarity, but the caption now collapses
"r m circle dot saasy dot top" into one gold rmcircle.saasy.top line
(no fragments). Re-encoded over the same /v/ filename so the link is stable.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New primary cut: site-scroll b-roll + word-synced captions, with a
full-screen matrix-expansion animation (YOU→2→4→8→16) during the pay
section showing per-level POL (Ascensus 621, Fabrica 1,243, Culmen
2,486, Apex 4,971) with an honest "contract rule, not a promise" note.
Crypto Team Build Network framing throughout. Web-optimized (~11MB).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Site-scroll b-roll + word-synced TikTok captions, voiced with ElevenLabs
timestamps. Reframed around the Crypto Team Build Network (watermark +
narration + CTA); RM Circle named as the co-op we build in. Web-optimized
(faststart, ~14MB). Unlisted /v/ path.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Per Marty: Crypto Team Build Network is OUR team; The RM Circle is the
third-party co-op we build in, not our brand. CTA changed from "Join
The RM Circle team build" to "Join the Crypto Team Build Network", and
hashtags now lead with #CryptoTeamBuild (then #TheRMCircle as the
program tag). Payout facts unchanged. Longest render 278/280.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
66s 1080p promo (HyperFrames + ElevenLabs VO), placed at an unguessable
/v/ path for Marty to preview on any device. Served with existing mp4
mime + HTTP range support (iOS-friendly). Not linked from the site.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Each join/upgrade yields exactly one payment, so one tweet tells the
whole story. Upgrade tweets already named the upgrader + recipient;
referral tweets now name the joining member (evt.fromId) too, e.g.
"Member #129 just joined and Member #30 instantly earned 326.2 POL".
All templates verified <=280.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Hashtag #RMCircle -> #TheRMCircle and CTA "Join The RM Circle team
build" to match the brand (thermcircle.com). Longest render 273/280.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
CTA line now reads "Join the RM Circle team build 👉" and hashtags lead
with #RMCircle #CryptoTeamBuild. All templates verified <=280 (longest
270). Branding is in every tweet, not just implied by a hashtag.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Blotato counts the raw URL length toward the 280 limit (no t.co
shortening), so the long UTM CTA overflowed. Shortened default CTA to
?utm_source=x and added a guard in render(): drop hashtags, then trim
body, so a tweet can never exceed 280. Verified a real test post to
@cryptoteambuild returns HTTP 201.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New tweet.js posts a tweet to X via Blotato each time the indexer emits
a NEW team payout. Org-gated to the #21 organization; fires on all
payout types. Ships DISABLED (config.tweetEnabled default off / env
TWEET_ON_PAYOUT), so nothing posts until explicitly turned on.
Safety: dedupes by tx key (persisted to DATA_DIR/tweeted-payouts.json)
so restarts never re-post; a min-gap queue keeps bursts under Blotato's
30/min limit; API key read from env BLOTATO_API_KEY or DATA_DIR key
file, never committed or logged. Varied emoji/hashtag templates with a
CTA (+UTM) to the main page; deterministic template pick avoids X
duplicate-content rejection. Admin config allowlist gains tweetEnabled,
tweetCtaUrl, tweetHashtags, blotatoTwitterId.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The feed showed only the latest 12 of 136 recorded payouts. Now:
- chain.getPayoutsPublic(offset,limit) returns a page of the full
reversed history plus total/offset/limit/hasMore (limit capped 100).
- /api/public/payouts accepts ?offset & ?limit (defaults 0/40, so the
live poll + toast detection are unchanged).
- payouts.js keeps a deduped store keyed by payout key; the live poll
refreshes the recent page while "Show more" pulls older pages 12 at a
time (with slight overlap so a newly-arrived payout can't open a gap),
and "Show fewer" collapses back. Verified in-browser: 12 → 48 → 136
rows, button flips to "Show fewer", collapses to 12, 0 console errors.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Home page: new reassurance band between the live payment feed and the
final CTA — surfaces the three doubts (rules can't change, money never
sits in the contract, keeps running if creators vanish) and routes
skeptics to /contract.
CSP fix (the real find): style-src was 'self' with no 'unsafe-inline',
so the browser was silently dropping EVERY inline style="" attribute
site-wide — the attribute stayed in the DOM but never applied. This is
why the earlier margin fix only worked once moved to a class, and why
the new card rendered left-aligned with a teal eyebrow. Added
'unsafe-inline' to style-src only (script-src stays locked to 'self').
Verified via computed styles + full-page screenshots: home, /contract,
/how-pay-works now render as authored.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Answers the durability question: the contract is autonomous and
immutable (no admin heartbeat, no pause, no expiry), and the four
admin wallets are plain EOAs — read live from contract storage and
confirmed via eth_getCode — so a lost/abandoned admin wallet can
never reject or jam a member payment; at worst the project's own fee
sits uncollected. No stored balance means nothing can be stranded.
- contract.html: new section 6 card
- chat.js: matching canned answer (creators-disappear keywords)
- server.js: RESILIENCE fact added to the AI system prompt
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
chat.js: new canned answers for how-you-get-paid (two streams + depth-
matched levels), Premium vs Standard tier, and the member dashboard/
alerts. server.js AI system prompt: added PAY FLOW, TIERS, and MEMBER
DASHBOARD facts, and refreshed the site-pages list (/how-pay-works,
/my, /disclaimer, spillover article). Both chat modes now answer the
questions this session surfaced (skips, standard tier, dashboards).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Preempts the "why did an amount come in smaller?" question (hit live with
Standard-tier #46): a clear card with a Premium/Standard amount table,
that tier is permanent (upgrading advances level not tier), and the team
play of joining Premium so the whole leg pays full value.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Visual explainer of the two income streams: entry rewards you keep, and
the depth-matched upgrade ladder (each layer pays you once, at the one
level matching its depth) as an SVG flow diagram. Route + CSS added;
linked from training body and all footers. Educational, on-chain-factual
framing with disclaimer link.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
/my/:id and /join/:id are now served with server-injected, per-member
Open Graph + Twitter Card tags (social scrapers don't run JS, so the
per-ID meta must be in the static HTML). Strips any baked-in og/twitter
tags and injects a fresh ID-specific set — title/description reference
the member #, branded og-card.jpg image, canonical per-ID og:url. Bare
/my and /join paths unchanged.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Make .team-stat a centered flex column and force the .num to full-width
centered text — the big numbers were rendering left-aligned. Verified
0px off-center across all four tiles.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The grid-3 inline margin-top:32px computed to 0 (collapsed against the
grid team-stats container), leaving the two rows touching. Use a class
margin-bottom:34px on .team-stats instead — verified 34px gap locally.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Bump the stat-tile grid gap 16→22px and the gap to the mechanics cards
24→32px so the boxes breathe.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Public /api/public/org-stats (from config.orgRootId, default 21) feeds a
prominent home-page band: share of the whole network, team size,
generations deep, and on-chain POL to the team — populated by bridge.js,
section hides itself if stats aren't ready. Paired with three mechanics
cards (spillover fills your matrix, depth pays as it climbs, the rotation
qualifies you) that make the "winning team" case honestly, plus the risk
caveat ("most participants may not profit") and a disclaimer link.
Live: 51.1% of members, 48 in the org, 10 generations, 25,423 POL.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New chain.getOrgShare(rootId) + /api/admin/org-share endpoint compute an
org's share of the whole contract by both member count and total POL
paid, from in-memory state. Admin card (default root 21, saved to
config.orgRootId, auto-loads) shows the two headline percentages, a bar,
and the member/POL breakdown. Verified: #21 org = 51.1% of members,
49.5% of POL.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Extended the "2 → 4 → 8 → 16 → 32" visual to the full doubling
2→4→8→16→32→64→128→256 (510 positions), keeping the 30-position first
milestone in the caption. Matrix is now data-driven (data-n) with
icons capped at 12 + a "+" for deeper generations so 256 stays compact;
compact icon styling + horizontal scroll safety.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A rotation joiner submits their ID after the rotation may have advanced
(esp. with auto-advance: the direct who completes a sponsor's 2/2 joined
under it, but the queue has already moved on). Keying "rotation" off the
currently-active sponsor mislabeled them "leg" (hit live: Harvey #92
under #36 after #36 qualified). Now: rotation if the on-chain referrer
is a queue sponsor that is active OR qualified (was/is worked); a
still-waiting or non-queue referrer stays a leg join, preserving the
original #49/#56-under-#46 fix. Auto-enqueue now parents the new
position to the actual on-chain referrer, not the current active.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Reverses the earlier manual-Qualify design (Marty 2026-08-15): when the
auto-count brings a queue sponsor to 2/2 directs, the sponsor is now
auto-qualified and normalizeStatuses activates the next waiting position
— same as clicking Qualify, but automatic. Previously it stopped at 2/2
"active" and waited for a manual click, which left the rotation looking
stuck (hit live with #36 Mad Dog). #36 qualified manually to catch up;
rotation advanced to #34 Janie.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- /disclaimer: independent-resource, affiliate, earnings, risk, and
not-advice disclosures; linked from all footers.
- Self-service alerts: members opt in with their email on /my/:id to get
"you've been paid" + "upgrade needed" emails for their own position
(same watcher as the owner alerts, extended). Signed unsubscribe link
(/unsubscribe?id=&t=HMAC), on-chain-registration check, rate-limited,
masked-email status, confirmation email.
- Admin login: timing-safe compare + per-IP lockout (8 fails -> 15 min,
escalating). Previously unlimited/brute-forceable.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New owner upgrade watcher: every 5 min it checks config.ownerIds against
the chain state and, when a leg member is ONE upgrade from paying a
position that isn't eligible yet (below the required level, or not
qualified), emails config.ownerAlertEmail + pings Telegram — "upgrade
#24 to Fabrica, #61 is one upgrade from paying you 2,486 POL." Deduped
per (position, level) in owner-alerts.json, re-fires if the situation
recurs. Same warning renders inline in the admin "My Positions" panel
(upgradeNeeds in the income endpoint). New ownerAlertEmail settings
field. Detection logic unit-tested.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Aggregates every on-chain payment received by a set of owned IDs
(defaults to 21,24,25, saved to config.ownerIds and prefilled/auto-loaded
next time). Shows grand total + per-position totals and a merged,
newest-first ledger (to / from / entry-or-upgrade level / amount) via a
focused chain.getIncome read and an admin-gated /api/admin/income
endpoint. Verified: 5,064.43 POL across 21/24/25, 11 payments.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Generates a chat-ready, per-member explainer of the upgrade/generation
payment structure — the recurring "will I miss upgrades?" question
answered from that member's real position: their spot, the one rule
(each layer pays you once at one level), their ladder with amounts and
which layers they're already eligible for, an honest "you miss it only
if you fall behind" note, and a calibrated next move (no false urgency —
distinguishes a layer that's close from one still climbing). One click
copies it for pasting into Telegram/chat; works for any member by ID.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Source submitted and Exact Match confirmed on Polygonscan (TRUSTCorona,
Solidity 0.8.28) via the CDP-assisted flow. The two-registry explainer
becomes a both-registries-verified statement.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A team member checked Polygonscan and saw unverified bytecode while the
page claims verified source. Both true: the source is exact-match
verified on Sourcify; Polygonscan is a separate registry nobody
submitted to. The page now explains the two-registry situation, that
the displayed bytecode is identical, and that Polygonscan publication
is in progress.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Makes the depth-matched payment routing visible per member: walks their
subtree and shows who is ONE upgrade away from paying them (member at
depth D whose level equals D — their next upgrade routes to this
position first), the exact amounts from the contract's cost tables
(exposed via the member API), eligibility warnings (needs 2 directs /
needs level X), a ready-now total, and whether it covers their own next
upgrade. Members building toward their pay-you level are counted, with
the takeaway line "helping your leg upgrade IS your income."
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Shareable page from the 2026-08-13 source review: code immutability
(no proxy/delegatecall/selfdestruct, Sourcify exact match), same-tx
distribution (no pooled funds), locked prices and fee constants, the
honest list of owner powers with the 50% entry-fee cap, where unmatched
pass-ups go, and verify-yourself links. Linked from all public footers,
the payment-proof note, and the chatbot (canned + AI prompt).
Also: passed-over lists now exclude structurally-skipped uplines — a
level-N payment never checks the first N-1 uplines, so listing them as
"not eligible" was misleading.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
When a queue member's MemberUpgraded event lands, their Level in the
rotation queue updates automatically (same op as the admin dropdown),
with a Telegram note. Current queue trued up against the chain: four
entries corrected (30, 35, 46 up to Ascensus; 56 down to Scintilla —
it had been set optimistically).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The chain-only BFS pick could promote structurally-next but inactive
positions (#21's dashboard said #38 — not in the queue, likely inactive —
while the team rotation was working #36). Next-in-line now prefers the
active rotation sponsor when they're in the member's leg and unqualified,
then the first chain-order queue participant, falling back to the pure
structural pick for legs outside the queue.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A verified rotation join (@chriskelly8, ID 73 under #36) still required
a manual "add to queue" step from the Telegram message and got missed.
Rotation-path submissions now insert themselves into the sponsor queue
as waiting positions (name from the submission, level from chain,
parent = active sponsor, dedupe-guarded), and the Telegram alert reports
the queue position instead of asking for action. #73 was added manually
to catch up.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
/my/<id> links circulate (address-bar shares, pre-/join links), and a
cold prospect landing there saw stats with no story. First-time viewers
of a position now get a banner: two-sentence RM Circle summary, a
"Read your invitation from this member" CTA into /join/<id>, a strategy
link, and the risk line. Hidden for repeat viewers of the same position
(likely the member) and dismissible per session.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Prospects who clicked a member's shared /my link landed on a bare stats
dashboard with no explanation of the program. New /join/<id> page carries the
full bridge-page story (video, strategy, matrix, live on-chain payout proof)
personalized to one sponsor: their live position stats as proof, their ID
pinned on the dApp join button, and the submit-your-ID form locked to them
(source invite-<id>). Dashboard share buttons + QR codes now hand out the
invite page; /my stays the member dashboard. Invalid/unregistered invite ids
fall back to the /start rotation. Tracked as new 'join' event with an admin
traffic column.
Also: the chain indexer now auto-increments a rotation sponsor's directs when
a registration names them as referrer (same op as the admin ⊕), announcing it
on Telegram. At 2/2 it alerts to Qualify instead of auto-rotating — moving
the team focus stays a human decision.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two leg-build members submitted the /start form thinking it was required,
polluting rotation bookkeeping. Rather than two forms, the server now
classifies every submission by on-chain truth: referrer == active
rotation sponsor -> "rotation" (Telegram says +1 direct, add to queue);
anyone else -> "leg" (correct sponsor credited, "no rotation action
needed"). The member dashboard gains its own "Just joined under this
position?" form so leg builders have a proper landing spot; /start
feedback explains each path to the submitter; admin submissions table
shows a rotation/leg chip. Verified against live data: ID 65 claiming
sponsor 36 correctly classified leg under #62.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Marty's final framing: the teachable rule stays "get your 2, retire
your link, help your 2" — but a late signup on a qualified link is
presented everywhere as a welcome bonus (full entry reward + depth via
spillover), never a rule violation. Applied consistently across the
strategy page, start callout, chatbot (canned + AI prompt), training
article, and both share-card notes.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Remove the last "shallow legs" claim and reword "retires your link" —
a qualified link keeps working and spills depth; it just stops being
the team's focus.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
martbost