From a8c4b8e664ed0146a30e546d61849425ee0c9bc4 Mon Sep 17 00:00:00 2001 From: martbost Date: Fri, 14 Aug 2026 12:23:49 -0500 Subject: [PATCH] =?UTF-8?q?Contract=20now=20verified=20on=20Polygonscan=20?= =?UTF-8?q?too=20=E2=80=94=20update=20/contract?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- public/contract.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/public/contract.html b/public/contract.html index aa624a0..21189c9 100644 --- a/public/contract.html +++ b/public/contract.html @@ -10,7 +10,7 @@
Contract0x33Bd…2DAF ↗
NetworkPolygon Mainnet
Source verified (Sourcify)Exact match ↗
-

1. The code can never change.

Some crypto projects use "upgradeable" contracts — the operator can swap in new code after you've joined, changing the rules underneath you. This contract has none of that machinery. 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 exact bytecode match, the code we reviewed is provably the code that's running — not a copy, not a claim.

"But Polygonscan says it's not verified?" Sharp eye — there are two separate verification registries, and they don't share data. The source was published to Sourcify ↗, the open-source registry, which confirmed an exact match 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.

+

1. The code can never change.

Some crypto projects use "upgradeable" contracts — the operator can swap in new code after you've joined, changing the rules underneath you. This contract has none of that machinery. 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 exact bytecode match, the code we reviewed is provably the code that's running — not a copy, not a claim.

Verified on both major registries. The source is published and exact-match verified in two independent places: Sourcify ↗ (the open-source registry, verified the day of deployment) and Polygonscan ↗ (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.

2. Member money never sits in the contract.

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 in the same transaction — 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 payment proof feed: money in, money out, same block.

@@ -20,7 +20,7 @@

5. Where "missed" payments go.

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 get your 2 directs and keep your level current — eligible positions catch payments; ineligible positions watch them pass by. The Member Dashboard shows exactly this happening in real time.

-

Check it yourself — please.

+

Check it yourself — please.

What this page is not: code security is not an income guarantee. This review says the rules can't change underneath you — 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.