The annotation reads, wallet trace:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for Fenix Funds.
• Forwarding wallets on the deposit chain, each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint, the centralised exchange deposit address holding the compliance lever.

Off-ramp summary, Fenix Funds casefile:

• Fenix Funds off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Fenix Funds 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 Fenix Funds, the packet meets the off-ramp’s published compliance standard.
• When the Fenix Funds 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 Fenix Funds:

1. Triage on Fenix Funds, submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Fenix Funds, deposit pathway mapped across chains, captured with chain of custody hashes.
3. Identify on Fenix Funds, off-ramp endpoint matched to a named exchange counterparty.
4. File the Fenix Funds 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 Fenix Funds, the Professor stays on the casefile until a documented next step exists.