The annotation reads, wallet trace:

• Initial deposit hashes to the Coinnova receiving address at coinnova.eu.
• 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 Coinnova:

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

The Professor’s recovery note for Coinnova:

1. Submission triage, Coinnova casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace, Coinnova deposit and forwarding wallets captured.
3. Endpoint identification, Coinnova off-ramp wallet named.
4. Filing, Coinnova packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow, Coinnova stays on file until a documented next step is reached.

Boundaries on every Coinnova casefile, never crossed:

• Coinnova policy, seed phrases are never requested.
• Coinnova policy, remote-access logins are never requested.
• Coinnova policy, no upfront cash retainer to scope.
• Coinnova policy, no guaranteed-recovery language. None.
• Coinnova policy, no unsolicited calls. The Professor responds in writing only.