Reading the wallets, Bane casefile:

• Deposit-side hashes from claimant wallets into Bane’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.

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

• Off-ramp endpoint for Bane resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Bane’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Bane is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the Bane 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. Casefile triage on Bane, the submission is read; a written assessment is delivered.
2. Forensic trace on Bane, every hop in the deposit pathway is captured and hashed.
3. Off-ramp identification, the Bane endpoint is named.
4. Recovery filing on Bane, packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
5. Continuing review of Bane, the Professor follows the casefile until next-step documentation exists.

What we read in a Bane casefile:

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