Reading the wallets, TapFin casefile:

• Deposit confirmations from the claimant to TapFin’s receiving wallet at tapfin.io.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

The annotation continues, off-ramp endpoint:

• Off-ramp endpoint for TapFin resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• TapFin’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for TapFin is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the TapFin off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

How a TapFin casefile becomes a evidence filing:

1. Casefile review on TapFin, reading the submission against the no-go list.
2. Trace mapping on TapFin, pathway documented to chain of custody standard.
3. Off-ramp naming on TapFin, exchange endpoint identified.
4. Packet filing on TapFin, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on TapFin.

Lines the Professor will not cross:

• Hard line on TapFin, no seed-phrase requests, period.
• Hard line on TapFin, no remote logins requested.
• Hard line on TapFin, no upfront cash retainer.
• Hard line on TapFin, no guarantee language.
• Hard line on TapFin, no unsolicited phone outreach.