Contract now verified on Polygonscan too — update /contract

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>

public/contract.html

@@ -10,7 +10,7 @@
 
 <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 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">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)">Verified on both major registries.</strong> The source is published and exact-match verified in two independent places: <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, verified the day of deployment) and <a href="https://polygonscan.com/address/0x33BdAEEfd6d17D80aE53816c916dFb26c4fB2DAF#code" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">Polygonscan ↗</a> (Exact Match, contract name TRUSTCorona, Solidity 0.8.28). Two registries, independently confirming the same thing: the readable source you can inspect is byte-for-byte the code that's running.</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>
 
@@ -20,7 +20,7 @@
 
 <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">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" target="_blank" rel="noopener noreferrer" style="color:var(--teal)">The contract on Polygonscan ↗</a> — every transaction, ever, public.</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="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>