← BTC24H4 decisions on this page
Audit log
Every state-changing event for BTC24H: 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.
- #1publishby system:backfill2026-05-30 04:56:42ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 423,087,962
- sig
iVK1aAbXGFGF…GnhXkPCWexplorer ↗- hash
4BPFJFqCK2h8…tVA7VHPfsha256 → base58
verifying row…full verify ↗canonical bytes (4888 B) ▸
{"actor":"system:backfill","investigation_id":"989aead3-c953-49ff-a28f-846df2c9bc83","kind":"publish","page_slug":"btc24h","published_at":"2026-05-30T04:56:42.562Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"BTC24H","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://btc24h.site/","type":"other","url":""},{"credibility":3,"name":"https://bitcoin24h.io/","type":"other","url":""},{"credibility":3,"name":"https://polygonscan.com/token/0xbcde600B00232E49DCf9E5c89c588269999ac97a","type":"other","url":""},{"credibility":3,"name":"https://www.geckoterminal.com/polygon_pos/pools/0x8671b56bcc6cf8832593f78b6b01f12621133b0c","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://quadrigainitiative.com/casestudy/btc24hclaimsystemcontractmissingeligibilitycheck.php","type":"other","url":""},{"credibility":3,"name":"https://hacked.slowmist.io/?c=Polygon","type":"other","url":""},{"credibility":3,"name":"https://www.nominis.io/insights/crypto-security-incidents-december-2024","type":"other","url":""},{"credibility":3,"name":"https://polygonscan.com/tx/0x554c9e4067e3bc0201ba06fc2cfeeacd178d7dd9c69f9b211bc661bb11296fde","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://quadrigainitiative.com/casestudy/btc24hclaimsystemcontractmissingeligibilitycheck.php","type":"other","url":""},{"credibility":3,"name":"https://btc24h.site/","type":"other","url":""},{"credibility":3,"name":"https://www.beermoneyforum.com/threads/bitcoin24h-io-reviews-scam-or-legit.51695/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.scamadviser.com/check-website/bitcoin24h.net","type":"other","url":""},{"credibility":3,"name":"https://www.scamadviser.com/check-website/bitcoin24h.org","type":"other","url":""},{"credibility":3,"name":"https://www.scamvoid.net/check/bitcoin24h.io/","type":"other","url":""},{"credibility":3,"name":"https://www.scam-detector.com/validator/bitcoin24h-org-review/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://polygonscan.com/token/0xbcde600B00232E49DCf9E5c89c588269999ac97a","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/dexscan/polygon/0x1d99ab27a248a8ca2674b580edda0378e030a7e0/","type":"other","url":""},{"credibility":3,"name":"https://www.geckoterminal.com/polygon_pos/pools/0x8671b56bcc6cf8832593f78b6b01f12621133b0c","type":"other","url":""},{"credibility":3,"name":"https://quadrigainitiative.com/casestudy/btc24hclaimsystemcontractmissingeligibilitycheck.php","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://t.me/s/investigations","type":"other","url":""},{"credibility":3,"name":"https://www.beermoneyforum.com/threads/bitcoin24h-io-reviews-scam-or-legit.51695/","type":"other","url":""},{"credibility":3,"name":"https://tgstat.com/channel/@investigations","type":"other","url":""}]}],"sources_used":[],"summary":"BTC24H is an ERC-20 token and associated DAO platform launched on Polygon in late 2024, marketed as a mechanism for continuous Bitcoin distribution through high-yield daily payouts. The platform's Lock contract suffered a critical access-control vulnerability in December 2024 that allowed any caller to drain tokens, resulting in an estimated $85,700 loss. Multiple independent scam-detection services rate associated BTC24H web domains as high-risk or outright malicious, and the project's tokenomics — 5% daily returns for 30 days via a multi-level referral structure — exhibit structural characteristics consistent with unsustainable high-yield investment programs.","timeline":[{"date":"2024-11-01","event":"Domain bitcoin24h.net registered (approximate, based on Scamadviser analysis noting November 2024 registration date).","source":""},{"date":"2024-12-01","event":"BTC24H token (0xbcde600B) deployed on Polygon PoS; Uniswap v3 liquidity pools created with near-zero liquidity.","source":""},{"date":"2024-12-16","event":"BTC24H Lock contract on Polygon exploited via missing eligibility check in the 'claim' function; estimated loss of $85,700. Exploit transaction: 0x554c9e4067e3bc0201ba06fc2cfeeacd178d7dd9c69f9b211bc661bb11296fde.","source":""},{"date":"2024-12-17","event":"SlowMist Weekly Security Report documents the BTC24H Polygon exploit. Security monitors @TenArmorAlert, @0xCommitAudits, and @IncentiveFi flag the suspicious activity.","source":""},{"date":"2025-01-27","event":"Quadriga Initiative publishes case study formally documenting the BTC24H claim system contract missing eligibility check, classifying the loss at approximately $86,000.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision 82df41c6-860d-4aa9-96bb-9149b26d6bf6 - #2rescoreby systemsystem2026-10-10 18:41:52ZScore: 18 → 26 (+8)Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 26. Problems weighed by who is responsible: the subject's own conduct −40, incidents the subject suffered −3.2; no established finding that it defrauded anyone, so it stays out of the red band.anchoranchored
- chain
- ●mainnet-betaslot 455,361,072
- sig
4gGEPeWFp4bi…znqB1TcHexplorer ↗- hash
GLzQVSyfbrvb…ZEsFxNarsha256 → base58
verifying row…full verify ↗canonical bytes (628 B) ▸
{"actor":"system","decided_at":"2026-10-10T18:41:52.123Z","decision":"rescore","investigation_id":"989aead3-c953-49ff-a28f-846df2c9bc83","new_score":26,"page_slug":"btc24h","prev_score":18,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 18 → 26. Problems weighed by who is responsible: the subject's own conduct −40, incidents the subject suffered −3.2; no established finding that it defrauded anyone, so it stays out of the red band.","score_delta":8,"score_model":"v2","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 22f1f8f2-810f-45dc-919d-301feaa63db3 - #3reviewby reviewerreviewer2026-10-27 19:14:13ZScore: 26 → 26 (no score change)The core exploit claims (missing eligibility check, about $85,700 loss, tx hash) and the Scamadviser findings on bitcoin24h.net match the sources I fetched. Problems: the ZachXBT flag is asserted though the page admits it has no evidence; a paraphrase is put in quotation marks as a Quadriga quote; the Jan 27 Quadriga publication date and the exact Dec 16-17 dates are not backed by the case study. On-chain and market-data claims could not be read and are not scored. I found no information on the project's current status.anchoranchored
- chain
- ●mainnet-betaslot 462,185,065
- sig
5NNeHEqXKDm5…1PycG9NZexplorer ↗- hash
H1JcCSXPTRkV…TzeEZRBTsha256 → base58
verifying row…full verify ↗canonical bytes (1368 B) ▸
{"actor":"reviewer","artifact_identity":"c752ec75dbd4ec85a09e19594728f982","blocked_count":1,"decided_at":"2026-10-27T19:14:12.913Z","decision":"review","disputed_pct":0.3333,"findings_hash":"79uX4nsbhP8fQ3fbJDGBSNQHP92DYtFytrcNt7B3piej","investigation_id":"989aead3-c953-49ff-a28f-846df2c9bc83","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_content_hash":"957f330f3cb3b25884b7b7db6d66a9368736369d40f70fa66a960ca7f0b3633e","page_slug":"btc24h","prev_score":26,"reason":"The core exploit claims (missing eligibility check, about $85,700 loss, tx hash) and the Scamadviser findings on bitcoin24h.net match the sources I fetched. Problems: the ZachXBT flag is asserted though the page admits it has no evidence; a paraphrase is put in quotation marks as a Quadriga quote; the Jan 27 Quadriga publication date and the exact Dec 16-17 dates are not backed by the case study. On-chain and market-data claims could not be read and are not scored. I found no information on the project's current status.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":3,"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 e0aa74ee-5281-448e-a3b2-c433398ae7f7 - #4review reviseby judgejudge2026-10-27 19:14:13ZScore: 26 → 26 (no score change)Of 7 claims checked, 1 could not be assessed because the source blocked the reviewer and was left out, leaving 6. Two of those 6 (33%) could not be verified: the ZachXBT flag (claim_findings[5]), which the page asserts while admitting it found no supporting post, and the 2025-01-27 Quadriga publication date (claim_findings[1]). The core exploit claims (missing eligibility check, about $85,700 loss) and the Scamadviser findings were confirmed, and a quotation attributed to Quadriga is actually a paraphrase (claim_findings[4]). The penalty sits at the low end of the band because reviewer confidence is moderate-to-low (0.5) and the page's central allegations hold up. On-chain and market-data claims could not be read, which is a coverage limit rather than a defect of the page.anchoranchored
- chain
- ●mainnet-betaslot 462,185,070
- sig
5X2JPhnYH9Bd…KZCWyVHBexplorer ↗- hash
DjextTcsgpry…bJ3bTLkWsha256 → base58
verifying row…full verify ↗canonical bytes (1459 B) ▸
{"actor":"judge","artifact_identity":"c752ec75dbd4ec85a09e19594728f982","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:14:12.913Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"989aead3-c953-49ff-a28f-846df2c9bc83","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"btc24h","prev_score":26,"reason":"Of 7 claims checked, 1 could not be assessed because the source blocked the reviewer and was left out, leaving 6. Two of those 6 (33%) could not be verified: the ZachXBT flag (claim_findings[5]), which the page asserts while admitting it found no supporting post, and the 2025-01-27 Quadriga publication date (claim_findings[1]). The core exploit claims (missing eligibility check, about $85,700 loss) and the Scamadviser findings were confirmed, and a quotation attributed to Quadriga is actually a paraphrase (claim_findings[4]). The penalty sits at the low end of the band because reviewer confidence is moderate-to-low (0.5) and the page's central allegations hold up. On-chain and market-data claims could not be read, which is a coverage limit rather than a defect of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"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 942dc556-82de-4940-b28c-96e7dd4c8af7
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>.