The annotation reads — wallet trace:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for BRCC.
• 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.

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

• On the BRCC casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for BRCC is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A regulator-ready packet is delivered to the named counterparty — the BRCC casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, BRCC escalates to IC3, state AG, and civil-discovery overlay.

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

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

What the Professor tracks across BRCC casefiles:

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

Lines we never cross — by published policy:

• Boundary on BRCC — seed phrases are off-limits.
• Boundary on BRCC — remote logins are off-limits.
• Boundary on BRCC — upfront cash retainers are off-limits.
• Boundary on BRCC — guaranteed-recovery promises are off-limits.
• Boundary on BRCC — unsolicited outbound contact is off-limits.