The annotation reads, wallet trace:

• Deposit-side hashes from claimant wallets into Arbiquant’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

Off-ramp summary, Arbiquant casefile:

• Arbiquant off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Arbiquant 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 Arbiquant, the packet meets the off-ramp’s published compliance standard.
• When the Arbiquant off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

The Professor’s recovery note for Arbiquant:

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

Boundaries on every Arbiquant casefile, never crossed:

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