Reading the wallets, SigmaBanc casefile:

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

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

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

The Professor’s recovery note for SigmaBanc:

1. Casefile review on SigmaBanc, reading the submission against the no-go list.
2. Trace mapping on SigmaBanc, pathway documented to chain of custody standard.
3. Off-ramp naming on SigmaBanc, exchange endpoint identified.
4. Packet filing on SigmaBanc, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on SigmaBanc.

What the Professor will never do, by policy:

• Hard line on SigmaBanc, no seed-phrase requests, period.
• Hard line on SigmaBanc, no remote logins requested.
• Hard line on SigmaBanc, no upfront cash retainer.
• Hard line on SigmaBanc, no guarantee language.
• Hard line on SigmaBanc, no unsolicited phone outreach.