← PeopleDAO3 decisions on this page
Audit log
Every state-changing event for PeopleDAO: 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 05:05:38ZScore: ? → ? (no score change)anchoranchored
- chain
- ●mainnet-betaslot 423,089,312
- sig
4oPutJTPw4gG…rPGXK8zPexplorer ↗- hash
3KeJEGawKarC…yDjH9vFZsha256 → base58
verifying row…full verify ↗canonical bytes (5420 B) ▸
{"actor":"system:backfill","investigation_id":"28b0aaa9-98f7-4552-b0ea-b8e96024fc77","kind":"publish","page_slug":"peopledao","published_at":"2026-05-30T05:05:38.598Z","sequence_num":1,"snapshot":{"content_type":"investigation","entity_name":"PeopleDAO","sections":[{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.gate.com/learn/articles/what-is-constitutiondao/672","type":"other","url":""},{"credibility":3,"name":"https://people-dao.com/governance/people-token","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/constitutiondao/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.theblock.co/post/219214/peopledao-hacked-via-google-sheets","type":"other","url":""},{"credibility":3,"name":"https://www.oodaloop.com/technology/2023/03/13/peopledao-hacked-via-google-sheets-120000-worth-of-ether-stolen/","type":"other","url":""},{"credibility":3,"name":"https://dexenetwork.medium.com/peopledao-hacked-for-76-5eth-in-the-most-comically-bad-way-f369ca12f4ea","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.theblock.co/post/219214/peopledao-hacked-via-google-sheets","type":"other","url":""},{"credibility":3,"name":"https://www.request.finance/post/peopledaos-crypto-payroll-hacked-for-76-5-eth-prevention-tips","type":"other","url":""},{"credibility":3,"name":"https://dexenetwork.medium.com/peopledao-hacked-for-76-5eth-in-the-most-comically-bad-way-f369ca12f4ea","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.oodaloop.com/technology/2023/03/13/peopledao-hacked-via-google-sheets-120000-worth-of-ether-stolen/","type":"other","url":""},{"credibility":3,"name":"https://www.theblock.co/post/219214/peopledao-hacked-via-google-sheets","type":"other","url":""},{"credibility":3,"name":"https://en.wikipedia.org/wiki/ZachXBT","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://www.coingecko.com/en/coins/constitutiondao","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/currencies/constitutiondao/","type":"other","url":""},{"credibility":3,"name":"https://coinmarketcap.com/cmc-ai/constitutiondao/price-prediction/","type":"other","url":""}]},{"content":"","heading":"","severity":"medium","sources":[{"credibility":3,"name":"https://peopledao.mirror.xyz/nPEAVJ7NPKwrFKwNQ1A960LyrU_Nh2etT02lLvORCcg","type":"other","url":""},{"credibility":3,"name":"https://people-dao.com/","type":"other","url":""},{"credibility":3,"name":"https://www.theblock.co/post/219214/peopledao-hacked-via-google-sheets","type":"other","url":""}]}],"sources_used":[],"summary":"PeopleDAO is a community-governed decentralized autonomous organization that emerged from ConstitutionDAO in late 2021, adopting the PEOPLE token as its governance instrument and operating as a meta-DAO incubator for social-good subDAOs. In March 2023, the organization suffered a significant treasury exploit in which an attacker stole 76.5 ETH (approximately $120,000) by exploiting a publicly shared Google Sheets payroll form with edit access — a failure of basic operational security controls. The stolen funds were moved to centralized exchanges and no recovery has been confirmed; the incident drew engagement from on-chain investigator ZachXBT and blockchain security firm SlowMist.","timeline":[{"date":"2021-11-01","event":"ConstitutionDAO forms with the goal of purchasing a copy of the U.S. Constitution at Sotheby's auction, raising over $47 million in ETH from 17,000+ contributors and issuing the PEOPLE ERC-20 token.","source":""},{"date":"2021-11-18","event":"ConstitutionDAO is outbid at the Sotheby's auction by hedge fund manager Ken Griffin, whose bid of approximately $43.2 million wins. The DAO announces dissolution and opens redemptions.","source":""},{"date":"2021-12-06","event":"Community members vote via Snapshot to form PeopleDAO, adopting the PEOPLE token as the governance instrument for a new meta-DAO structure focused on social good and Web3 coordination.","source":""},{"date":"2022-06-01","event":"PeopleDAO has incubated two subDAOs (PandaDAO and LanguageDAO) and one community project (Constitution Fractionalized), establishing its operational model as a subDAO accelerator.","source":""},{"date":"2023-03-06","event":"PeopleDAO's accounting lead accidentally posts a Google Sheets payroll form with edit access to a public Discord channel. An attacker inserts a fraudulent payment row for 76.5 ETH, conceals it, and the entry passes multi-sig review. The attacker receives 76.5 ETH (~$120,000) from the Gnosis Safe treasury.","source":""},{"date":"2023-03-06","event":"The attacker transfers stolen funds: 69.2 ETH ($110,000) to HitBTC and 7.3 ETH to Binance.","source":""},{"date":"2023-03-13","event":"PeopleDAO publicly discloses the exploit. The organization announces it is working with ZachXBT and SlowMist to trace the attacker and has reported the incident to U.S. law enforcement and the exchanges involved. A 10% white hat bounty is offered.","source":""},{"date":"2025-11-01","event":"KuCoin delists PEOPLE from Spot Margin Trading services, reducing leveraged trading access to the token.","source":""}]},"v":1}Verify offline (run on your own machine)python -m src.verify_decision e975c4ec-34c9-4699-8b57-bd1c9c7668b5 - #2reviewby reviewerreviewer2026-08-19 04:00:08ZScore: 42 → 42 (no score change)All ConstitutionDAO/PeopleDAO formation facts and hack details (amount, method, date, exchange destinations, and cooperative post-incident response) were independently confirmed against multiple primary and secondary sources with no contradictions. The page correctly frames PeopleDAO as the victim of an external attacker rather than a perpetrator, and does not use unhedged fraud language. The only defect found is a minor date/context error on the KuCoin delisting timeline entry (off by ~2 weeks, and presented without noting it was a routine multi-token action). The larger limitation is structural: the section bodies delivered to this review were empty, so roughly half the page's actual prose could not be fact-checked.anchorpending
- chain
- ●—
- hash
Fodyfdg8V3gQ…3Py1Q684sha256 → base58
verifying row…canonical bytes (1072 B) ▸
{"actor":"reviewer","decided_at":"2026-08-19T04:00:08.702Z","decision":"review","investigation_id":"28b0aaa9-98f7-4552-b0ea-b8e96024fc77","new_score":42,"page_slug":"peopledao","prev_score":42,"reason":"All ConstitutionDAO/PeopleDAO formation facts and hack details (amount, method, date, exchange destinations, and cooperative post-incident response) were independently confirmed against multiple primary and secondary sources with no contradictions. The page correctly frames PeopleDAO as the victim of an external attacker rather than a perpetrator, and does not use unhedged fraud language. The only defect found is a minor date/context error on the KuCoin delisting timeline entry (off by ~2 weeks, and presented without noting it was a routine multi-token action). The larger limitation is structural: the section bodies delivered to this review were empty, so roughly half the page's actual prose could not be fact-checked.","score_delta":0,"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 81c9f513-ddd0-4618-9fc8-620b5acfe590 - #3review approve with notesby judgejudge2026-08-19 04:00:08ZScore: 42 → 48 (+6)This is a calibration-only adjudication; content accuracy was not disputed (disputed_pct 0.0%, 13/14 claims confirmed, 1 partially_supported on a ~2-week timeline date). The substantive incident is a March 2023 theft of 76.5 ETH (~$120K) enabled by PeopleDAO's own operational-security failure (a publicly editable payroll Google Sheet) rather than pure third-party exploitation of code outside the DAO's control — per the page's own scoring instruction, own-negligence in a still-operating, non-convicted entity places this correctly in the WARNING band (20-49), consistent with the reviewer's incident_attributions[0]. Within that band, strong mitigating post-incident conduct — public disclosure within a week, voluntary law-enforcement and exchange notification, cooperation with ZachXBT and SlowMist, a good-faith 10% bounty offer, a comparatively small absolute loss, and no recurrence in the 3+ years since — justifies moving toward the top of the band rather than the middle. I agree with the reviewer's recommended_score of 48 (current_score 42), a modest 6-point lift that keeps the band unchanged and reflects conduct rather than facts in dispute. Notes: (Correct the KuCoin delisting timeline entry: the announcement was dated Nov 11, 2025 with an effective window of Nov 17-21, 2025 (UTC), not Nov 1, 2025.) (Note in that same entry that KuCoin's delisting was a routine, simultaneous action across six unrelated tokens (C, FLR, HOME, SPK, PEOPLE, RESOLV), not a PEOPLE-specific risk signal.) (Regenerate the six page sections before publication confidence is placed in them — as delivered to review, all `heading` and `content` fields were empty, so section prose could not be fact-checked.)anchorpending
- chain
- ●—
- hash
962ArQtoSb7x…ewWcVCbrsha256 → base58
verifying row…canonical bytes (2066 B) ▸
{"actor":"judge","decided_at":"2026-08-19T04:00:08.702Z","decision":"review_approve_with_notes","investigation_id":"28b0aaa9-98f7-4552-b0ea-b8e96024fc77","new_score":48,"page_slug":"peopledao","prev_score":42,"reason":"This is a calibration-only adjudication; content accuracy was not disputed (disputed_pct 0.0%, 13/14 claims confirmed, 1 partially_supported on a ~2-week timeline date). The substantive incident is a March 2023 theft of 76.5 ETH (~$120K) enabled by PeopleDAO's own operational-security failure (a publicly editable payroll Google Sheet) rather than pure third-party exploitation of code outside the DAO's control — per the page's own scoring instruction, own-negligence in a still-operating, non-convicted entity places this correctly in the WARNING band (20-49), consistent with the reviewer's incident_attributions[0]. Within that band, strong mitigating post-incident conduct — public disclosure within a week, voluntary law-enforcement and exchange notification, cooperation with ZachXBT and SlowMist, a good-faith 10% bounty offer, a comparatively small absolute loss, and no recurrence in the 3+ years since — justifies moving toward the top of the band rather than the middle. I agree with the reviewer's recommended_score of 48 (current_score 42), a modest 6-point lift that keeps the band unchanged and reflects conduct rather than facts in dispute. Notes: (Correct the KuCoin delisting timeline entry: the announcement was dated Nov 11, 2025 with an effective window of Nov 17-21, 2025 (UTC), not Nov 1, 2025.) (Note in that same entry that KuCoin's delisting was a routine, simultaneous action across six unrelated tokens (C, FLR, HOME, SPK, PEOPLE, RESOLV), not a PEOPLE-specific risk signal.) (Regenerate the six page sections before publication confidence is placed in them — as delivered to review, all `heading` and `content` fields were empty, so section prose could not be fact-checked.)","score_delta":6,"sequence_num":3,"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 200c09bf-418c-47b5-a31b-8e2fe25dc9a2
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>.