Reading the wallets, BFTBOT casefile:

• Deposit-side hashes from claimant wallets into BFTBOT’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

The Professor’s off-ramp note:

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

How a BFTBOT casefile becomes a evidence filing:

1. Read the BFTBOT submission, written go/no-go returned.
2. Map the BFTBOT wallet trail, every hop captured with chain of custody hashes.
3. Name the BFTBOT off-ramp, endpoint counterparty identified.
4. Build and file the BFTBOT recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the BFTBOT file, until written next steps exist.

What the Professor will never do, by policy:

• On the BFTBOT casefile, never request a seed phrase. Ever.
• On the BFTBOT casefile, never request remote-access logins to a wallet or exchange.
• On the BFTBOT casefile, never demand an upfront cash retainer to scope the matter.
• On the BFTBOT casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the BFTBOT casefile, never call the claimant unsolicited. Written-only.