Wallet trace — what the Professor maps:

• Initial deposit hashes to the Finabel receiving address at finabel.co.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

The Professor’s off-ramp note:

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

The Professor’s recovery note for Finabel:

1. Submission triage — Finabel casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — Finabel deposit and forwarding wallets captured.
3. Endpoint identification — Finabel off-ramp wallet named.
4. Filing — Finabel packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — Finabel stays on file until a documented next step is reached.

Reading-list — chains and exchanges in scope:

• Chains tracked on Finabel — 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 Finabel — named exchange counterparties with public compliance contacts.
• Filings supported on Finabel — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

What the Professor will never do — by policy:

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