The annotation reads — wallet trace:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for BTrade.
• Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

The Professor’s off-ramp note:

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

Recovery sequence — from on-chain reading to filed packet:

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

Reading-list — chains and exchanges in scope:

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

Lines we never cross — by published policy:

• What the Professor will not do on BTrade — ask for a seed phrase.
• What the Professor will not do on BTrade — request remote-access logins.
• What the Professor will not do on BTrade — demand cash up front.
• What the Professor will not do on BTrade — promise a guarantee.
• What the Professor will not do on BTrade — call you out of the blue.