From the marginalia — the deposit pathway:

• Deposit confirmations from the claimant to FalconCM’s receiving wallet at falcon-cm.net.
• 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.

Off-ramp reading — exchange counterparty for FalconCM:

• Off-ramp endpoint for FalconCM resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• FalconCM’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for FalconCM is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the FalconCM off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

Recovery pathway — how this casefile moves toward filing:

1. Read the FalconCM submission — written go/no-go returned.
2. Map the FalconCM wallet trail — every hop captured with chain-of-custody hashes.
3. Name the FalconCM off-ramp — endpoint counterparty identified.
4. Build and file the FalconCM recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the FalconCM file — until written next steps exist.

Chains and off-ramps the Professor follows:

• Chains tracked on FalconCM — 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 FalconCM — named exchange counterparties with public compliance contacts.
• Filings supported on FalconCM — 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:

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