The annotation reads, wallet trace:

• Initial deposit hashes to the IPrimeCapital receiving address at iprimecapital.site.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain of custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets, the named counterparty that holds compliance leverage.

Off-ramp reading, exchange counterparty for IPrimeCapital:

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

Recovery sequence, from on-chain reading to filed packet:

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

What we read in a IPrimeCapital casefile:

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