zkGUN

CRYPTO FORENSICS // RECOVERY UNIT

Submit a Case  ↗

Authorized cooperation channel

Technical findings built for formal action.

Victims often arrive with fragmented screenshots and raw transaction data. We organize technical material into a clearer case narrative that may help authorized investigators, legal representatives and compliance teams understand what happened.

Request cooperation ↗ Victim case intake →
Channel status // Verified requests only

Who this channel is for

Built for people with a legitimate role in the case.

This channel is for parties who need to review, request or receive technical case material in a professional capacity — not a general contact form.

Role 01

Law Enforcement

Investigators seeking transaction mapping, wallet indicators or a structured incident timeline for an open case.

Role 02

Legal Representatives

Attorneys or counsel acting on behalf of a victim who require technical context for legal proceedings.

Role 03

Compliance Teams

Exchange or service-provider compliance staff reviewing flagged wallet activity or account misuse.

Role 04

Authorized Victims

Victims or their designated representatives submitting a case that may require formal escalation.

Evidence package

What a structured case file contains.

Where a matter supports it, we prepare technical material in a format that investigators and legal teams can work with directly.

Transaction mappingVisualized asset movement across relevant addresses.
Wallet indicatorsSending, receiving and intermediary address data.
Incident timelineChronological reconstruction of the event.
Evidence indexOrganized reference of supporting records and sources.
CASE_REF // STRUCTURED
SOURCES // INDEXED
FORMAT // REVIEW-READY

How a request is handled

Request workflow.

01 // IDENTIFY

Role Verification

We confirm the requesting party’s role and connection to the case before any material is shared.

02 // MATCH

Case Lookup

The relevant case reference and available technical findings are located and reviewed for relevance.

03 // PREPARE

Package Assembly

Findings are compiled into a structured format appropriate for the requesting party’s purpose.

04 // DELIVER

Secure Handoff

Material is shared through an appropriate channel, with scope limited to what the request supports.

Before you request

What to include in a formal request.

To keep case material limited to people with a genuine need to review it, requests should identify the requesting party, their role and the specific case or victim the request relates to.

Requesting party & role
Case or victim reference
Purpose of request
Preferred secure contact

Scope of cooperation

What this channel is — and is not.

This channel supports

Evidence-based cooperation

  • Sharing organized technical findings tied to a specific, identifiable case.
  • Clarifying blockchain activity for investigators and legal teams.
  • Responding to verified requests from compliance departments.
  • Supporting victims’ authorized representatives with case context.
This channel does not

Unverified or unlawful action

  • Provide case material to unverified or unrelated third parties.
  • Perform unauthorized access, seizure or retaliation on anyone’s behalf.
  • Guarantee investigative outcomes or recovery timelines.
  • Act as a substitute for filing an official report with authorities.

Official channel

Have an active case that needs technical context?

Send your role, the case or victim reference and the purpose of your request. We will confirm what technical material, if any, is available to share.

Request cooperation ↗