Add "What if the creators disappear?" reassurance (verified on-chain)

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>

public/chat.js

@@ -30,6 +30,8 @@
      a:()=>`A position is <strong>qualified</strong> once it has 2 directs. The team recommendation: retire your link at that point and help your 2 get <em>their</em> 2 using their own links — that's the only thing that qualifies them. And if someone happens to join through your link after 2/2, it's a bonus, not a problem: the entry reward still pays your position and they spill downward, adding depth to your leg. Just remember spillover never qualifies the people below — their own directs do.`},
     {k:['safe','scam','rug','rug pull','security','audit','trust','legit','contract code','smart contract','can they change','steal'],
      a:()=>`Fair question — don't take anyone's word for it. We reviewed the complete verified source of the RM Circle smart contract and published a plain-language breakdown at <a href="/contract">rmcircle.saasy.top/contract</a>: the code can never change (no upgrade mechanism exists), member money never sits in the contract (every payment distributes in the same transaction), prices and payout rules are locked forever, and the operator's powers are limited to a short, honest list. Every claim links to the blockchain so you can verify it yourself. Code security isn't an income guarantee though — results depend on real participation, and POL's value moves.`},
+    {k:['disappear','disappears','creator','creators','abandon','abandoned','walk away','goes away','shut down','shuts down','still work','keep running','keeps running','autonomous','dies','lost keys','without them','stop working','turned off','if they leave','what if they','forever','over time'],
+     a:()=>`Great question — and we checked it on-chain, not just in theory. The contract needs <strong>no one</strong> to keep it running: joins, upgrades, placement and every payout are fully automatic — no button anyone has to press, no expiry. If the creators walked away, lost their keys, or vanished, member payments keep flowing exactly as coded. We also verified that the founder, development and fee wallets are <strong>ordinary wallets, not programs</strong> — an ordinary wallet always accepts an incoming payment even if its key is lost forever, so a dead admin wallet can't jam a single member payment (at worst the project's <em>own</em> fee sits there uncollected). And the contract holds no stored balance — every payment is delivered in the same transaction. Full write-up in section 6 of <a href="/contract">rmcircle.saasy.top/contract</a>.`},
     {k:['spillover','spill over','spill','under me but not qualified','people under me','not my direct','passed over','missed payment','skipped','why am i not qualified'],
      a:()=>`<strong>Spillover</strong> happens when someone's sponsor already has both matrix slots full — the smart contract then places the new member in the next open slot further down, which can be under YOU. Spillover fills your matrix and sets up future upgrade payments to your position, but it does <strong>not</strong> count toward your qualification: only people who join using <em>your</em> ID are your directs. That's why you can see 2 under you and still show 1/2. And important: upgrade payments only stop at positions that are qualified (2 directs) AND at the required level — otherwise the payment passes you by to the next eligible upline. Check your position on your <a href="/my">Member Dashboard</a> — spillover placements are tagged there.`},
     {k:['how do i get paid','how do i earn','commission','commissions','how payments work','how does the money','payout','payouts','pay flow','when do i get paid','how do i make money','income','two ways','how you get paid'],

public/contract.html

@@ -20,6 +20,8 @@
 
 <div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">5. Where "missed" payments go.</h2><p style="color:var(--muted);line-height:1.65;margin:0">When an upgrade payment finds no eligible upline within 16 levels (or reaches the root), it goes to the project's fee wallet rather than vanishing. That's the strongest built-in reason to <strong style="color:var(--text)">get your 2 directs and keep your level current</strong> — eligible positions catch payments; ineligible positions watch them pass by. The <a href="/my" style="color:var(--teal)">Member Dashboard</a> shows exactly this happening in real time.</p></div>
 
+<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">6. What if the creators disappear?</h2><p style="color:var(--muted);line-height:1.65;margin:0 0 10px">A fair question about any on-chain program: if the people who launched it walked away, lost their keys, or simply vanished — does it quietly break over time? For this contract the answer is <strong style="color:var(--text)">no, and we verified it directly on the blockchain</strong> — not just in theory.</p><p style="color:var(--muted);line-height:1.65;margin:0 0 10px"><strong style="color:var(--text)">Nothing needs an admin to keep running.</strong> Joins, upgrades, matrix placement, and every payout are fully automatic. There is no periodic "keepalive," no button anyone has to press to keep payments flowing, and no expiry date anywhere in the code. Whether the creator is present or gone changes nothing about what members receive.</p><p style="color:var(--muted);line-height:1.65;margin:0 0 10px"><strong style="color:var(--text)">A lost or abandoned admin wallet can't jam the machine.</strong> Every payout requires its recipient to accept the coins, so we checked what those admin wallets actually are: the founder, development, and fee-receiver wallets are all <strong style="color:var(--text)">ordinary wallets, not programs.</strong> An ordinary wallet <em>always</em> accepts an incoming payment — even if its key is lost forever and no human is behind it. So even in the worst case, the coins simply arrive and sit there uncollected; the member on the other side of that transaction still gets paid, every time. The only thing that could ever go uncollected is the project's <em>own</em> fee — never a member's earnings.</p><p style="color:var(--muted);line-height:1.65;margin:0">And if the owner's key were lost, the four limited powers from section 4 would simply <strong style="color:var(--text)">freeze in place</strong> forever — the fee percentage and wallet addresses could never change again. Members would never notice, because members never depended on those powers. The contract also keeps <strong style="color:var(--text)">no stored balance</strong> — every payment is delivered in the same transaction it arrives in — so there's nothing sitting inside that could be stranded. In short: this system's survival does not depend on any person staying reachable.</p></div>
+
 <div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">Check it yourself — please.</h2><ul style="color:var(--muted);line-height:1.8;margin:0;padding-left:20px"><li><a href="https://polygonscan.com/address/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF#code" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">The contract on Polygonscan ↗</a> — every transaction, ever, public — now with the verified, readable source under the Contract tab.</li><li><a href="https://repo.sourcify.dev/contracts/full_match/137/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF/" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">The verified source code ↗</a> — the exact code that's running, independently verified.</li><li><a href="/#proof" style="color:var(--teal)">The live payment feed</a> — every payout on this site links to its blockchain transaction.</li><li>Ask any developer you trust to read the source against this page. It's ~400 lines.</li></ul></div>
 
 <div class="callout warning"><strong>What this page is not:</strong> code security is not an income guarantee. This review says the <em>rules can't change underneath you</em> — it does not promise the program grows, that positions fill, or that POL holds its value. Results depend on real participation and duplication, and POL's market price moves. Never use funds you can't afford to lose.</div>

server.js

@@ -41,6 +41,7 @@ FACTS:
 - PAY FLOW (full diagram at https://rmcircle.saasy.top/how-pay-works): TWO income streams. (1) Entry rewards — when a direct joins under a member's link, that member gets the entry reward (~326 POL at Premium) and keeps it, on EVERY direct (not just the first two). (2) Upgrade payments — each person below you pays you ONCE, at the single level matching how far below you they sit: someone 1 layer down pays you at their Ascensus upgrade, 2 layers down at Fabrica, 3 at Culmen, 4 at Apex, and so on. To catch each one you must be at that level yourself AND qualified — so stay one level ahead of your team's deepest active layer. This is why a member can be "skipped" on a payment: it was reserved for the position at the matching depth, or they weren't leveled up in time.
 - TIERS: Premium (the tier the whole team builds at, ${c.premiumEntryPol || 362} POL entry) pays and earns FULL amounts; Standard costs about half and pays/earns HALF at every level. A smaller-than-expected payment almost always came from a Standard-tier position below. Tier is fixed at registration and CANNOT be changed later (upgrading advances your LEVEL, not your tier). Always recommend joining Premium and having recruits do the same. Amount comparison at /how-pay-works.
 - MEMBER DASHBOARD & ALERTS: each member has a live dashboard at https://rmcircle.saasy.top/my (enter your ID) showing position, team, payments, pipeline (incoming money forming below), spillover tags, and qualification badges. Members can turn on opt-in EMAIL ALERTS there (notified when paid, and when they need to upgrade to catch incoming pay). A member's personal invite page to share is https://rmcircle.saasy.top/join/<their-id>.
+- RESILIENCE ("what if the creators disappear / owner loses keys / it falls apart over time"): the contract is autonomous and immutable — NO admin action, heartbeat, or living operator is required for joins, upgrades, matrix placement, or payouts; there is no pause switch and no expiry. Verified on-chain that the founder, development, and fee-receiver wallets are ordinary wallets (EOAs), NOT smart contracts — an ordinary wallet always accepts incoming POL even if its key is lost forever, so a dead or abandoned admin wallet cannot block any member payment (only the project's OWN uncollected fee would sit idle). The contract stores no balance (every payment is delivered in the same transaction). If the owner's key were lost, only the four limited admin powers freeze in place; members are unaffected. Details in section 6 of https://rmcircle.saasy.top/contract.
 - Current team sponsor: ${a ? `ID ${a.id}${c.showSponsorName && a.name ? ` (${a.name})` : ''}, ${a.directs}/2 directs` : 'shown on the start page'}. ${waiting} placement(s) waiting. Placements rotate as positions qualify — always verify on https://rmcircle.saasy.top/start right before joining.
 - Site pages: https://rmcircle.saasy.top/ (strategy overview + roadmap + live team stats), https://rmcircle.saasy.top/start (current sponsor + join steps), https://rmcircle.saasy.top/training (4 videos + spillover article), https://rmcircle.saasy.top/how-pay-works (the two income streams shown as a pay-flow diagram + Premium/Standard tier comparison), https://rmcircle.saasy.top/contract (plain-language security review of the verified smart contract — code can't change, no pooled funds, locked rules, honest list of operator powers), https://rmcircle.saasy.top/my (member dashboard), https://rmcircle.saasy.top/disclaimer (affiliate/earnings/risk disclosures).
 - Telegram group for live team help: ${c.telegramUrl || 'https://t.me/cryptoteambuild'}