Commit Graph

3 Commits

Author SHA1 Message Date
martbost a8c4b8e664 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>
2026-08-14 12:23:49 -05:00
martbost af1ac403c5 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>
2026-08-14 11:56:25 -05:00
martbost d1aef1e3ff Add /contract — plain-language security review of the smart contract
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>
2026-08-14 10:51:34 -05:00