The annotation reads — wallet trace:

• Initial deposit hashes to the Clover Markets receiving address at clovermarkets.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

Off-ramp summary — Clover Markets casefile:

• Clover Markets off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Clover Markets off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for Clover Markets — the packet meets the off-ramp’s published compliance standard.
• When the Clover Markets off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery sequence — from on-chain reading to filed packet:

1. Read the Clover Markets submission — written go/no-go returned.
2. Map the Clover Markets wallet trail — every hop captured with chain-of-custody hashes.
3. Name the Clover Markets off-ramp — endpoint counterparty identified.
4. Build and file the Clover Markets recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the Clover Markets file — until written next steps exist.

What the on-chain reading covers:

• Deposit + forwarding chains for Clover Markets — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the Clover Markets casefile may resolve to — centralised exchanges that respond to compliance filings.
• Filing pathways on Clover Markets — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

What the Professor will never do — by policy:

• What the Professor will not do on Clover Markets — ask for a seed phrase.
• What the Professor will not do on Clover Markets — request remote-access logins.
• What the Professor will not do on Clover Markets — demand cash up front.
• What the Professor will not do on Clover Markets — promise a guarantee.
• What the Professor will not do on Clover Markets — call you out of the blue.