Liquidity-removal incident anatomy

A real liquidity removal can occur in a migration or an ordinary redemption. The event itself and a fraud hypothesis need different evidence.

HISTORICAL PROVENANCE WARNING: the frozen package is a bounded transcription of an Etherscan rendering inspected on 2 October 2026 for a 26 September 2020 event. The web tool may use a cached rendering. No byte-identical HTML, native receipt/header or block hash was independently captured. The historical record is not a current Radar assessment.

Inspect the exact transaction and pool in docs/academy-2/datasets/p13/withdrawal.json. The explorer renders a Burn event at displayed locator 15 with two integer amounts. Corresponding transfer locators 12/13 show the same amounts leaving the pool for the recorded destination. LP transfer/burn rows provide mechanism context. The outer call is decoded as migration; the package does not independently reconstruct destination custody or the entire migration trace.

Decode the two 32-byte Burn data words and compare them with the rendered raw transfer integers. The offline verifier checks these equalities and display conversions. That is reproducible indexed event analysis, not independent canonical inclusion. Exclude current USD panels and friendly entity labels: they are unnecessary to establish what the bounded record displays and can introduce time or identity confusion. A withdrawal observation supports a technical action; fraud, theft and intent remain separate unestablished claims.

Burn event: protocol-specific liquidity-redemption event, distinct from a misconduct label.

Raw amount: integer asset units before decimal display.

Explorer locator: displayed event position for repeat inspection.

Attribution boundary: event participants are addresses, not identified humans.

Ethereum mainnet, transaction 0x479e5dc5e1950916f29f1b3897c4158b94882339312da76373c496ce6c46d9fd, indexed block 10935968, rendered timestamp 2020-09-26T03:55:41Z. Pool 0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc sends to 0x8cc757bc682e718d2f0264c1fcd3269eccf8214e. Raw amounts: 92255858879 USDC units and 262329864091228143654 WETH units; rendered equivalents 92,255.858879 USDC and 262.329864091228143654 WETH. Exact token addresses, event topic/data and indexed Burn/transfer locators are frozen. This is an actual historical indexed event, not a fictional launch.

Historical signal timeline for indexed block 10935968 with rendered LP redemption/Burn/outflow locators and exact raw/display amounts. Put migration context and native proof gaps in separate boxes; no fraud badge or USD loss estimate.

Caption: Historical explorer-documented withdrawal; fraudulent intent and human identity are not established.

SPECIFICATION_ONLY — the rendered visual has not been produced or independently reviewed.

OBSERVED at the explorer boundary: the rendered successful transaction, exact pool/asset locators, timestamp and matching Burn/outflow amounts. Local decoding reproduces the raw integers and stated decimal displays.

No independent native inclusion/header, complete pool withdrawal fraction, subsequent destination accounting, human identity, theft, criminal intent or global safety is established. Decoded migration context is not a full independent benign-purpose proof either.

Calling every Burn a rugpull; using current USD valuation as historical movement value; assigning a human from the explorer label; claiming complete migration custody from one transaction.

Decode the two Burn data words using the frozen verifier, match them to transfer amounts, and prepare two conclusions: one about withdrawal and one about fraud. Include one unresolved migration dependency.

• Use exact transaction/pool/token identifiers.
• Match Burn and transfer raw amounts.
• Retain rendered/indexer provenance limits.
• Separate withdrawal from identity, motive and legal conclusions.

The real indexed withdrawal has inspectable identifiers and amount correspondence, but those technical records do not settle an allegation of fraud.

• An actual withdrawal can be supported without a fraud conclusion.
• Raw units and display decimals need separate provenance.
• Migration context does not remove destination-accounting gaps.

P13-L04

Use the named ZECOIN tool only as an evidence-reading context. This lesson creates no tool output, account session or entitlement. Offline exercise; do not sign, deploy, approve or fund anything.

• WITHDRAWAL: Historical rendered withdrawal transaction — Rendered Burn locator 15 and corresponding token outflows 12/13, transaction/height/time; source is an indexed explorer rendering, not independent native capture. Boundary: Bounded field transcription; cached web rendering possible. No independently captured native receipt/header, block hash, complete migration trace or human identity.
• POOL: Uniswap v2 pools — LP tokens represent pool participation; withdrawal mechanism is separate from motive or fraud. Boundary: Mechanism documentation only; original illustrative values are stipulated, not observations. Historical records have separately frozen provenance and explicit collection gaps.

HISTORICAL — event dates and retrieval dates are separate. See frozen package and collection gaps.

2026-10-02 (retrieval date; not event time)

1

null

needs_review