On-chain reading — wallet flow for HeroFX:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for HeroFX.
• 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 HeroFX:

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

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

What the Professor tracks across HeroFX casefiles:

• Chains tracked on HeroFX — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on HeroFX — named exchange counterparties with public compliance contacts.
• Filings supported on HeroFX — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

Lines the Professor will not cross:

• HeroFX policy — seed phrases are never requested.
• HeroFX policy — remote-access logins are never requested.
• HeroFX policy — no upfront cash retainer to scope.
• HeroFX policy — no guaranteed-recovery language. None.
• HeroFX policy — no unsolicited calls. The Professor responds in writing only.