Off-ramp reading, exchange counterparty for Bartex:

• Bartex 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 Bartex is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Bartex, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Bartex casefile.

Recovery pathway, how this casefile moves toward filing:

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

Chains and off-ramps the Professor follows:

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

Boundaries on every Bartex casefile, never crossed:

• Hard line on Bartex, no seed-phrase requests, period.
• Hard line on Bartex, no remote logins requested.
• Hard line on Bartex, no upfront cash retainer.
• Hard line on Bartex, no guarantee language.
• Hard line on Bartex, no unsolicited phone outreach.