From the marginalia, the deposit pathway:

• Initial deposit hashes to the BPS Capital receiving address at bpscap.com.
• 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 reading, exchange counterparty for BPS Capital:

• On the BPS Capital 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 BPS Capital is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the BPS Capital casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, BPS Capital escalates to IC3, state AG, and civil-discovery overlay.

How a BPS Capital casefile becomes a evidence filing:

1. Casefile triage on BPS Capital, the submission is read; a written assessment is delivered.
2. Forensic trace on BPS Capital, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the BPS Capital endpoint is named.
4. Recovery filing on BPS Capital, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of BPS Capital, the Professor follows the casefile until next-step documentation exists.

Boundaries on every BPS Capital casefile, never crossed:

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