Wallet trace — what the Professor maps:

• Initial deposit hashes to the Bitblanco receiving address at bitblanco.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.

Off-ramp summary — Bitblanco casefile:

• Bitblanco’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the Bitblanco off-ramp wallet against historical laundering throughput.
• The Bitblanco packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for Bitblanco, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

Filing pathway — the next step after the off-ramp is identified:

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

Reading-list — chains and exchanges in scope:

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

Boundaries on every Bitblanco casefile — never crossed:

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