The annotation continues, off-ramp endpoint:

• Sun Long GMTK 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 Sun Long GMTK is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Sun Long GMTK, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Sun Long GMTK casefile.

How a Sun Long GMTK casefile becomes a evidence filing:

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

Chains and off-ramps the Professor follows:

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

What the Professor will never do, by policy:

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