From the marginalia, the deposit pathway:

• Deposit confirmations from the claimant to Linthrope’s receiving wallet at linthrope.com.
• 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 Professor’s off-ramp note:

• On the Linthrope casefile, the off-ramp endpoint resolves to a centralised exchange, Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for Linthrope is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the Linthrope casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Linthrope escalates to IC3, state AG, and civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

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

Chains and off-ramps the Professor follows:

• Chains in scope for Linthrope, the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for Linthrope, named centralised exchanges with compliance leverage.
• Filings supported on Linthrope, IC3, state AG, off-ramp desk, civil discovery as applicable.