The annotation continues, off-ramp endpoint:

• PRIMOBULL off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The PRIMOBULL 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 PRIMOBULL, the packet meets the off-ramp’s published compliance standard.
• When the PRIMOBULL off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

The Professor’s recovery note for PRIMOBULL:

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

Reading-list, chains and exchanges in scope:

• Chains the Professor reads for PRIMOBULL casefiles, BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in PRIMOBULL, major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on PRIMOBULL, IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

Boundaries on every PRIMOBULL casefile, never crossed:

• What the Professor will not do on PRIMOBULL, ask for a seed phrase.
• What the Professor will not do on PRIMOBULL, request remote-access logins.
• What the Professor will not do on PRIMOBULL, demand cash up front.
• What the Professor will not do on PRIMOBULL, promise a guarantee.
• What the Professor will not do on PRIMOBULL, call you out of the blue.