On-chain reading — wallet flow for Bex500:

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

The Professor’s off-ramp note:

• Bex500 off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Bex500 off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for Bex500 — the packet meets the off-ramp’s published compliance standard.
• When the Bex500 off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway — how this casefile moves toward filing:

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

What the Professor tracks across Bex500 casefiles:

• Chains tracked on Bex500 — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Bex500 — named exchange counterparties with public compliance contacts.
• Filings supported on Bex500 — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

What is never asked of a claimant:

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