From the marginalia, the deposit pathway:

• Deposit confirmations from the claimant to FerratumCapital’s receiving wallet at ferratumcapital.co.
• 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:

• Endpoint counterparty in the FerratumCapital casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• FerratumCapital’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty, the FerratumCapital packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the FerratumCapital off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

How a FerratumCapital casefile becomes a evidence filing:

1. Triage on FerratumCapital, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on FerratumCapital, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on FerratumCapital, off-ramp endpoint matched to a named exchange counterparty.
4. File the FerratumCapital packet, IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on FerratumCapital, the Professor stays on the casefile until a documented next step exists.