On-chain reading, wallet flow for Ben Capital:

• Claimant-to-platform deposit transactions on the deposit chain used by Ben Capital.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet, the named centralised-exchange endpoint.

The annotation continues, off-ramp endpoint:

• Off-ramp endpoint for Ben Capital resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Ben Capital’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Ben Capital is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the Ben Capital 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 review on Ben Capital, reading the submission against the no-go list.
2. Trace mapping on Ben Capital, pathway documented to chain of custody standard.
3. Off-ramp naming on Ben Capital, exchange endpoint identified.
4. Packet filing on Ben Capital, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on Ben Capital.

Reading-list, chains and exchanges in scope:

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