CAR: OLDER FUNDING AND FRESH TRANSACTIONS
30 October 2026. Exact block/time cutoffs are stated in the report and evidence.

Start here:
report/older-newer-findings.pdf — five-page updated findings
report/network/open-network.html — 9,600px interactive chart with three panels
report/network/delta-network-vector.pdf — large vector chart with proof links
report/network/proofs.html — eleven primary transaction proofs

What changed:
- A separate Car rescue-explanation post is platform-confirmed author-deleted.
  A publisher screenshot preserves the reported friend/bot-partner explanation.
  Its edited-version timing and exact deletion time remain unresolved.
- Another shared funding recipient is proven by Car111/E044333pUSD payments,
  followed by537pUSD from that recipient to a previously observed wallet lead.
- E044's legacy and beacon histories include33 recovered authorizations and
  five fully closed additional funding routes totaling19,797.438732pUSD.
- Car's new50,000pUSD movement is a Polymarket Perps collateral deposit naming
  his known signer. It is not a verified private-peer payout.
- A small attacker-linked USDT branch crossed Across to Base, funded a captured
  Commerce payment and then a pooled sweep to an explorer-tagged exchange address.
  Recipient/customer identity and attacker ownership of the payment accounts
  remain unproven. No Car-to-attacker key or funding link emerged.

Evidence layout:
history/ — E044 history, new111/333/537 funding, five deposits, Across signature
live/ — full fresh Polygon reconciliation and Base Commerce capture/sweep proofs
root/ — fresh Ethereum state/transactions, canonical token logs and Base fill
public/ — selected technical role proofs and deleted-post evidence
SOURCE-INDEX.json — source URLs, capture metadata and hashes for public pages
SHA256-EVIDENCE.json — hashes of every bundled evidence file

Public articles, documentation pages and screenshots are referenced by source
URL and capture hash. The working workspace retains those original captures.
The evidence pack focuses on chain records, signature proofs, technical source
bindings and the report; the publisher article itself is not reproduced in it.

Reproduce the report with Python3+BeautifulSoup+Playwright:
python3 build_update.py
python3 export_update.py
Then use Python+pypdf:
report/make_pdf_links_portable.py report/older-newer-findings.pdf --apply
 --audit-out report/PDF-LINK-PORTABILITY.json
The chart has its own builder and QA records in report/network/.

Older source snapshots are retained as siblings where needed. They are historical
inputs; the current report states the new findings and current coverage. All
operations were public/read-only research; no transactions were signed or sent,
and no external contact or publication was performed in this pass.
