The annotation reads, wallet trace:

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

• Yescom casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for Yescom is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Yescom, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Yescom casefile.

Recovery pathway, how this casefile moves toward filing:

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

What we read in a Yescom casefile:

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