The annotation reads, wallet trace:

• Deposit confirmations from the claimant to KnsTrade’s receiving wallet at knstrade.net.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

The Professor’s off-ramp note:

• Off-ramp endpoint for KnsTrade resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• KnsTrade’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for KnsTrade is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the KnsTrade off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

How a KnsTrade casefile becomes a evidence filing:

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

What the Professor will never do, by policy:

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