Address the "Polygonscan says not verified" objection on /contract

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>

public/contract.html

@@ -8,9 +8,9 @@
 <section class="section"><div class="wrap" style="max-width:880px">
 <div class="section-head"><div class="eyebrow">Plain-language code review</div><h1 style="font-size:clamp(32px,5vw,50px);margin:8px 0 10px">Can the bottom fall out of this? <span class="gold">We read the code.</span></h1><p>Every payment in the RM Circle runs through one smart contract on the Polygon blockchain. We reviewed its complete, verified source line by line. Here's what it says — in plain language, with links so you can check every claim yourself. Nobody has to take our word for anything.</p></div>
 
-<div class="facts" style="grid-template-columns:repeat(3,1fr);margin:18px 0 26px"><div class="fact"><small>Contract</small><strong style="font-size:13px"><a href="https://polygonscan.com/address/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">0x33Bd…2DAF ↗</a></strong></div><div class="fact"><small>Network</small><strong>Polygon Mainnet</strong></div><div class="fact"><small>Source verified</small><strong style="font-size:13px"><a href="https://repo.sourcify.dev/contracts/full_match/137/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF/" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">Exact match ↗</a></strong></div></div>
+<div class="facts" style="grid-template-columns:repeat(3,1fr);margin:18px 0 26px"><div class="fact"><small>Contract</small><strong style="font-size:13px"><a href="https://polygonscan.com/address/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">0x33Bd…2DAF ↗</a></strong></div><div class="fact"><small>Network</small><strong>Polygon Mainnet</strong></div><div class="fact"><small>Source verified (Sourcify)</small><strong style="font-size:13px"><a href="https://repo.sourcify.dev/contracts/full_match/137/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF/" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">Exact match ↗</a></strong></div></div>
 
-<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">1. The code can never change.</h2><p style="color:var(--muted);line-height:1.65;margin:0">Some crypto projects use "upgradeable" contracts — the operator can swap in new code after you've joined, changing the rules underneath you. <strong style="color:var(--text)">This contract has none of that machinery.</strong> No proxy, no delegatecall, no self-destruct — the three mechanisms that allow post-launch changes are simply absent from the code. What was deployed on May 27, 2026 is what runs today and what will run in ten years. And because the source is verified as an <em>exact bytecode match</em>, the code we reviewed is provably the code that's running — not a copy, not a claim.</p></div>
+<div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">1. The code can never change.</h2><p style="color:var(--muted);line-height:1.65;margin:0 0 10px">Some crypto projects use "upgradeable" contracts — the operator can swap in new code after you've joined, changing the rules underneath you. <strong style="color:var(--text)">This contract has none of that machinery.</strong> No proxy, no delegatecall, no self-destruct — the three mechanisms that allow post-launch changes are simply absent from the code. What was deployed on May 27, 2026 is what runs today and what will run in ten years. And because the source is verified as an <em>exact bytecode match</em>, the code we reviewed is provably the code that's running — not a copy, not a claim.</p><p style="color:var(--muted);line-height:1.65;margin:0"><strong style="color:var(--text)">"But Polygonscan says it's not verified?"</strong> Sharp eye — there are two separate verification registries, and they don't share data. The source was published to <a href="https://repo.sourcify.dev/contracts/full_match/137/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF/" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">Sourcify ↗</a>, the open-source registry, which confirmed an <em>exact match</em> against both the deployed bytecode and the creation bytecode (Solidity 0.8.28, verified 2026-05-27). Polygonscan runs its own registry, and nobody has submitted the source there yet — so it shows raw bytecode. That's a paperwork gap, not a code gap: the bytecode Polygonscan displays is byte-for-byte the same bytecode Sourcify matched, and anyone can compare the two. Publishing the same source on Polygonscan is possible for anyone with the source file (not just the creator) — it's in progress for this contract.</p></div>
 
 <div class="card" style="margin-bottom:16px"><h2 style="margin:0 0 10px">2. Member money never sits in the contract.</h2><p style="color:var(--muted);line-height:1.65;margin:0">There is no pool, no vault, no balance an operator could run away with. When someone joins or upgrades, the contract splits and delivers every coin <strong style="color:var(--text)">in the same transaction</strong> — sponsor reward, upline payment, fees — straight to member wallets. If any single transfer fails, the whole transaction reverses and nobody pays anything. You can watch this happen live on the <a href="/#proof" style="color:var(--teal)">payment proof feed</a>: money in, money out, same block.</p></div>