On-chain reading, wallet flow for Cryptojet:

• Deposit confirmations from the claimant to Cryptojet’s receiving wallet at cryptojet.ltd.
• 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.

The annotation continues, off-ramp endpoint:

• Cryptojet casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for Cryptojet is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Cryptojet, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Cryptojet casefile.

The Professor’s recovery note for Cryptojet:

1. Casefile review on Cryptojet, reading the submission against the no-go list.
2. Trace mapping on Cryptojet, pathway documented to chain of custody standard.
3. Off-ramp naming on Cryptojet, exchange endpoint identified.
4. Packet filing on Cryptojet, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on Cryptojet.

What the casefile records, chains and counterparties:

• Chains in scope for Cryptojet, the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for Cryptojet, named centralised exchanges with compliance leverage.
• Filings supported on Cryptojet, IC3, state AG, off-ramp desk, civil discovery as applicable.