We have not proved a Car–drainer connection or fraud.

Verified: the separate 750,000 pUSD transfer returned, with 753,333 pUSD received in total. Car also genuinely liquidated positions: 656,217.051510 pUSD gross in the initial 66-second burst, 676,996.268150 across the extended windows. Those are sale proceeds, not a loss estimate. Valid Car-key signatures do not prove informed consent. His original $800,000 claim remains unreconciled, not disproved.

Verified: three incident posts now have explicit author-deletion tombstones. Deletion time and motive are unknown. A retained rescue explanation is an edited screenshot with unknown version history. These facts do not establish a coverup.

Verified: E044, lolzzzlol, 5mTraderYes, 6d132 and Car have real funding relationships. They are not all proven to share a human controller. The shared ce523 receiving endpoint does not establish one exchange customer.

New, independently checked older oracle lead: Car’s actual key authorized 1,555 USDC.e to 3e837 on April 22, eight hours, 19 minutes and 30 seconds before that wallet proposed Yes on “US x Iran ceasefire extended by April 22, 2026?”. Car already held 44,785.664210 Yes shares in the parent block, before the proposal. The question and market ID are in the actual proposal event; the position is an archived CTF balance, not an imported estimate. An outside wallet disputed 22 seconds later. The request settled at the ignore/retry sentinel; the final market paid No. This is a genuine financial-alignment/conflict lead worth reviewing. It does not prove common ownership, dishonest intent, an invalid proposal, a rule violation or involvement in the drainer.

The old site's 134-proposal/21-dispute and 96-of-132 aggregate claims have not been independently reproduced in this incident audit. One verified example must not be reported as validation of every allegation. Full sources and the bounded one-case proof are in ASSESSMENT.json and ORACLE-ONE-CASE-VERIFIED.json.
