Off-ramp map, where the funds left the chain:

• AXNEB Ltd off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The AXNEB Ltd 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 AXNEB Ltd, the packet meets the off-ramp’s published compliance standard.
• When the AXNEB Ltd off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

1. First read on AXNEB Ltd, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on AXNEB Ltd, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for AXNEB Ltd is named to a centralised exchange wallet.
4. Packet filing on AXNEB Ltd, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with AXNEB Ltd until a documented outcome or escalation step is on file.

Chains and off-ramps the Professor follows:

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