Wallet trace — what the Professor maps:

• Initial deposit hashes to the JK Analytics receiving address at jk-analytics.com.
• 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.

The Professor’s off-ramp note:

• JK Analytics off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The JK Analytics 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 JK Analytics — the packet meets the off-ramp’s published compliance standard.
• When the JK Analytics 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 JK Analytics:

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

What the Professor tracks across JK Analytics casefiles:

• Chains tracked on JK Analytics — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on JK Analytics — named exchange counterparties with public compliance contacts.
• Filings supported on JK Analytics — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

What the Professor will never do — by policy:

• On the JK Analytics casefile — never request a seed phrase. Ever.
• On the JK Analytics casefile — never request remote-access logins to a wallet or exchange.
• On the JK Analytics casefile — never demand an upfront cash retainer to scope the matter.
• On the JK Analytics casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the JK Analytics casefile — never call the claimant unsolicited. Written-only.