Reading the wallets, AirrsanFx casefile:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for AirrsanFx.
• 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 reading, exchange counterparty for AirrsanFx:

• Endpoint counterparty in the AirrsanFx casefile is named, typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• AirrsanFx’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 AirrsanFx packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the AirrsanFx 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.

The Professor’s recovery note for AirrsanFx:

1. Casefile triage on AirrsanFx, the submission is read; a written assessment is delivered.
2. Forensic trace on AirrsanFx, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the AirrsanFx endpoint is named.
4. Recovery filing on AirrsanFx, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of AirrsanFx, the Professor follows the casefile until next-step documentation exists.