← Opacus8 decisions on this page
Audit log
Every state-changing event for Opacus: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.
- #1reviewby reviewerreviewer2026-11-01 13:57:13ZScore: 35 → 35 (no score change)The page is cautious and its claims about the homepage and Meta's library check out. The one real error is that the mint is written in lowercase, which is not a valid Solana address because addresses are case-sensitive. As a result, the page wrongly says it could not confirm that the mint matches the site's contract address, when the two match apart from letter case. No on-chain verification was performed by the page or by this review.anchoranchored
- chain
- ●mainnet-betaslot 464,117,047
- sig
2u3kWySYjE6w…DCuQ8f9Lexplorer ↗- hash
9E6FKp776mBG…aWmBeh9gsha256 → base58
verifying row…full verify ↗canonical bytes (1282 B) ▸
{"actor":"reviewer","artifact_identity":"63733a5a6a819b89adbcd1d78efab5af","decided_at":"2026-11-01T13:57:13.894Z","decision":"review","disputed_pct":0.3,"findings_hash":"5ieME1QbKYRPxiTB1ZpJXBgeAq2gDQBbWiVRzzsjrygb","investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":35,"omissions":{"material":0,"total":1},"page_content_hash":"8382620d7d5c786dd9595db7abba263d18093ccf5da1d57de24624920c280783","page_slug":"opacus","prev_score":35,"reason":"The page is cautious and its claims about the homepage and Meta's library check out. The one real error is that the mint is written in lowercase, which is not a valid Solana address because addresses are case-sensitive. As a result, the page wrongly says it could not confirm that the mint matches the site's contract address, when the two match apart from letter case. No on-chain verification was performed by the page or by this review.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":1,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 9d814756-c648-44db-a554-8e6cfea1009b - #2review reviseby judgejudge2026-11-01 13:57:14ZScore: 35 → 23 (-12)Counting claim_findings, 3 of 10 are disputed or unverifiable (claim_findings[1] and [2] disputed, [3] unverifiable), which is 30%, on the line between the minor and significant bands. Both disputed findings share one cause: the page prints the token mint in lowercase, which is not a valid Solana address, and so wrongly says it could not confirm the mint matches the site's contract address, when the two match apart from letter case. The rest of the page checks out against the homepage and Meta's own sources, the subject is still operating, and the only omission (the app link) is minor, so the page stays in the minor band at the top of its penalty range. The high-priority gap, that no on-chain analysis of the mint was done, is a further reason to revise rather than approve.anchoranchored
- chain
- ●mainnet-betaslot 464,117,052
- sig
281Q7F4x93Vb…AsCNwwfyexplorer ↗- hash
82cFp97S2ubQ…9QAPCXjpsha256 → base58
verifying row…full verify ↗canonical bytes (1526 B) ▸
{"actor":"judge","artifact_identity":"63733a5a6a819b89adbcd1d78efab5af","band_override":null,"decided_at":"2026-11-01T13:57:13.894Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3,"investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":23,"page_slug":"opacus","prev_score":35,"reason":"Counting claim_findings, 3 of 10 are disputed or unverifiable (claim_findings[1] and [2] disputed, [3] unverifiable), which is 30%, on the line between the minor and significant bands. Both disputed findings share one cause: the page prints the token mint in lowercase, which is not a valid Solana address, and so wrongly says it could not confirm the mint matches the site's contract address, when the two match apart from letter case. The rest of the page checks out against the homepage and Meta's own sources, the subject is still operating, and the only omission (the app link) is minor, so the page stays in the minor band at the top of its penalty range. The high-priority gap, that no on-chain analysis of the mint was done, is a further reason to revise rather than approve.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"score_limit":{"applied":-12,"limited":true,"proposed":-15,"rule":"second_opinion_agreed","second":-12},"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 3693aab7-4238-4aaf-a319-97bec97d4959 - #3reviewby reviewerreviewer2026-11-01 21:35:32ZScore: 23 → 23 (no score change)The page is largely accurate about the library (dates, repo stats, license, PyPI release) and cautiously declines to assert any token exists. One factual error: CVE-2020-28477 affects versions before 0.12.0 and is rated High, not low-severity and not tracked against 0.12.0. The final timeline entry is internal process commentary that cannot be verified externally.anchoranchored
- chain
- ●mainnet-betaslot 464,245,381
- sig
3WAYBYEqbWW3…YqD9YxzFexplorer ↗- hash
HnZbMbkPMbhj…mGS8Ncgqsha256 → base58
verifying row…full verify ↗canonical bytes (1175 B) ▸
{"actor":"reviewer","artifact_identity":"5a612a1e43e9550195a7f0b809c709e4","decided_at":"2026-11-01T21:35:32.356Z","decision":"review","disputed_pct":0.3333,"findings_hash":"E6bquQYL6WeNR2tjjWJ7hLyV8jfZy5BzWWjQQVwPD1sQ","investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":23,"page_content_hash":"bef381ff8e9968a746d0db419ba5c06576717c6c341845935c2ada94e9f8f617","page_slug":"opacus","prev_score":23,"reason":"The page is largely accurate about the library (dates, repo stats, license, PyPI release) and cautiously declines to assert any token exists. One factual error: CVE-2020-28477 affects versions before 0.12.0 and is rated High, not low-severity and not tracked against 0.12.0. The final timeline entry is internal process commentary that cannot be verified externally.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 53a48e02-d240-4a4f-b717-402495c16312 - #4review reviseby judgejudge2026-11-01 21:35:32ZScore: 23 → 8 (-15)Of 6 claims checked, 1 was disputed (claim_findings[3]) and 1 could not be verified (claim_findings[5]), giving a 33% disputed rate, which falls in the significant-issues band. The disputed item is the CVE-2020-28477 description: the cited source says versions before 0.12.0 are affected and rates it High (CVSS 7.5), while the page calls it low-severity and tied to 0.12.0. The unverifiable item is a timeline entry about an internal AVOID.NET review that cites an unrelated URL and does not belong in a public entity timeline. The core claims about the library (launch date, repo statistics, license, PyPI release, no token link) were confirmed, so the penalty is set at the mild end of the band.anchoranchored
- chain
- ●mainnet-betaslot 464,245,385
- sig
Ta9BZcHWMECo…W3uDgp1Sexplorer ↗- hash
9y19ppfGwN9f…TgXXNHfqsha256 → base58
verifying row…full verify ↗canonical bytes (1339 B) ▸
{"actor":"judge","artifact_identity":"5a612a1e43e9550195a7f0b809c709e4","band_override":null,"decided_at":"2026-11-01T21:35:32.356Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":8,"page_slug":"opacus","prev_score":23,"reason":"Of 6 claims checked, 1 was disputed (claim_findings[3]) and 1 could not be verified (claim_findings[5]), giving a 33% disputed rate, which falls in the significant-issues band. The disputed item is the CVE-2020-28477 description: the cited source says versions before 0.12.0 are affected and rates it High (CVSS 7.5), while the page calls it low-severity and tied to 0.12.0. The unverifiable item is a timeline entry about an internal AVOID.NET review that cites an unrelated URL and does not belong in a public entity timeline. The core claims about the library (launch date, repo statistics, license, PyPI release, no token link) were confirmed, so the penalty is set at the mild end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-15,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 9d010686-c7ac-4c59-aead-a8825779ffb4 - #5reviewby reviewerreviewer2026-11-02 14:48:08ZScore: 8 → 8 (no score change)The factual claims about the token are modest and match the Live Coin Watch listing: the address, the supply figures, and no trading data. The Meta library date is confirmed. The page is mostly careful, hedged negative-finding prose. Weak points are that 'no links' slightly overstates the listing, which carries a Solscan link, that the opacus.ai reference and 'years before' are unsupported, and that the token's current status could not be established.anchoranchored
- chain
- ●mainnet-betaslot 464,534,481
- sig
ZagijfECVwy6…Zwo6qL2Jexplorer ↗- hash
9AnoA11RsJ2f…Lq9r42RBsha256 → base58
verifying row…full verify ↗canonical bytes (1260 B) ▸
{"actor":"reviewer","artifact_identity":"3542a6ae87b0bf64a31470f57948e479","decided_at":"2026-11-02T14:48:08.641Z","decision":"review","disputed_pct":0.2857,"findings_hash":"8qKC1wKFHG1n33cCxVxXwganjHtnwK8jBqQKdphSAYt8","investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":8,"page_content_hash":"d6e92ee676da428ec0d855004d06f500eec2a240d2c6778e8bdc1760eae6f1b9","page_slug":"opacus","prev_score":8,"reason":"The factual claims about the token are modest and match the Live Coin Watch listing: the address, the supply figures, and no trading data. The Meta library date is confirmed. The page is mostly careful, hedged negative-finding prose. Weak points are that 'no links' slightly overstates the listing, which carries a Solscan link, that the opacus.ai reference and 'years before' are unsupported, and that the token's current status could not be established.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":5,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision e30b8977-49b6-400f-b333-61ab56df2828 - #6review reviseby judgejudge2026-11-02 14:48:08ZScore: 8 → 27 (+19)Two of seven reviewed claims could not be verified (claim_findings[3] and claim_findings[5]), and none were disputed, giving roughly 29% disputed or unverifiable, which falls in the minor-issues band. The core token facts (address, supply figures, no trading data, Meta library date) were confirmed against the cited sources. The weaker points are that 'no links' slightly overstates the Live Coin Watch listing (claim_findings[2]), that the opacus.ai reference is unchecked (claim_findings[6]), and that 'years before' lacks a token creation date. A high-priority gap remains: there is no on-chain analysis of holders, mint authority or creator wallet. The reviewer's confidence is moderate, so the penalty is kept modest.anchoranchored
- chain
- ●mainnet-betaslot 464,534,487
- sig
GRsTYxrwY7fx…JHWNoCs5explorer ↗- hash
CPMMg1d7QoYh…AeSCf45ysha256 → base58
verifying row…full verify ↗canonical bytes (1429 B) ▸
{"actor":"judge","artifact_identity":"3542a6ae87b0bf64a31470f57948e479","band_override":null,"decided_at":"2026-11-02T14:48:08.641Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":27,"page_slug":"opacus","prev_score":8,"reason":"Two of seven reviewed claims could not be verified (claim_findings[3] and claim_findings[5]), and none were disputed, giving roughly 29% disputed or unverifiable, which falls in the minor-issues band. The core token facts (address, supply figures, no trading data, Meta library date) were confirmed against the cited sources. The weaker points are that 'no links' slightly overstates the Live Coin Watch listing (claim_findings[2]), that the opacus.ai reference is unchecked (claim_findings[6]), and that 'years before' lacks a token creation date. A high-priority gap remains: there is no on-chain analysis of holders, mint authority or creator wallet. The reviewer's confidence is moderate, so the penalty is kept modest.","replaces_fact_checks":{"score_before_fact_checks":35,"undone":2},"reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":19,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 3bfc78d2-94c2-40bf-83d1-32d7336f8c6f - #7reviewby reviewerreviewer2026-11-17 21:17:19ZScore: 27 → 27 (no score change)The checked factual claims (DexScreener market figures, Live Coin Watch supply figures, website content, Meta library date, PyPI version) match live sources. The page hedges appropriately about unknowns. Main weakness is the lack of on-chain data. No shutdown or other status contradiction found.anchoranchored
- chain
- ●mainnet-betaslot 470,681,225
- sig
ahePacVb8tvV…yoz8Pxrrexplorer ↗- hash
21KbyR5bgj8j…EbGviFFfsha256 → base58
verifying row…full verify ↗canonical bytes (1100 B) ▸
{"actor":"reviewer","artifact_identity":"88d2b80e3c04a9c0923afcf8c1b7a82f","decided_at":"2026-11-17T21:17:19.061Z","decision":"review","disputed_pct":0,"findings_hash":"FfwCYUfDiBRs5CXXX857ATbREMFqEiwztdQpwztxb93E","investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":27,"page_content_hash":"72a8126032c5c55e2c11f72696eb7c8c702e913b6183d57d9ca247ac4e293d0e","page_slug":"opacus","prev_score":27,"reason":"The checked factual claims (DexScreener market figures, Live Coin Watch supply figures, website content, Meta library date, PyPI version) match live sources. The page hedges appropriately about unknowns. Main weakness is the lack of on-chain data. No shutdown or other status contradiction found.","reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":0,"sequence_num":7,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision 0becdfd5-c700-46f8-96a7-192a56700e90 - #8review approveby judgejudge2026-11-17 21:17:19ZScore: 27 → 35 (+8)All seven checked claims (claim_findings[0-6]) were confirmed against live sources, including the DexScreener market figures, Live Coin Watch supply figures, website content, the Meta AI release date and the PyPI version, so disputed_pct is 0%. The review found no omissions and the token is still operating, so nothing the page leaves out changes the picture. The one high-priority coverage gap, on-chain holder, deployer, liquidity lock and authority data, is already disclosed on the page, which says on-chain data was not obtained, so it is treated as a suggestion to expand the page rather than a reason to revise it.anchoranchored
- chain
- ●mainnet-betaslot 470,681,232
- sig
5DhHjiByN621…KaUjUbKuexplorer ↗- hash
HXSau1zYFvjZ…gu425fqMsha256 → base58
verifying row…full verify ↗canonical bytes (1324 B) ▸
{"actor":"judge","artifact_identity":"88d2b80e3c04a9c0923afcf8c1b7a82f","band_override":null,"decided_at":"2026-11-17T21:17:19.061Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"db70d8e6-b464-41ed-81c3-e2e9c02d75b8","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":35,"page_slug":"opacus","prev_score":27,"reason":"All seven checked claims (claim_findings[0-6]) were confirmed against live sources, including the DexScreener market figures, Live Coin Watch supply figures, website content, the Meta AI release date and the PyPI version, so disputed_pct is 0%. The review found no omissions and the token is still operating, so nothing the page leaves out changes the picture. The one high-priority coverage gap, on-chain holder, deployer, liquidity lock and authority data, is already disclosed on the page, which says on-chain data was not obtained, so it is treated as a suggestion to expand the page rather than a reason to revise it.","replaces_fact_checks":{"score_before_fact_checks":35,"undone":3},"reviewer_def_hash":"fdb97944d5e6ae9b148ae8c41caf98db055a4c751afd15721cb2e08d11dfd37a","score_delta":8,"sequence_num":8,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}Verify offline (run on your own machine)python -m src.verify_decision a7ad72ca-5b25-48c8-9b39-f0f796705f4f
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine —
python -m src.verify_decision <event_id>.