Submit evidence securely for recovery and investigation

Your browser encrypts every field and file before upload. Only the corresponding private key, stored offline, can open the submission. Submitting does not authorize publication.

A useful submission can be short

Tell us what happened and attach the clearest records you have. Optional fields can help connect your account to transactions, public statements, and loss calculations.

Protect yourself before sending

Never submit a seed phrase, private key, password, or recovery code.
Upload copies only. Preserve original files, platform exports, metadata, and devices separately. Uploaded copies may contain hidden author, location, or device information.
Up to 10 files, 25 MB each, and 100 MB total.
This channel is not an emergency service and does not create an attorney-client relationship.

You decide who may receive it

You can separately authorize confidential sharing with victim-side counsel, an appropriate law-enforcement or regulatory authority, or a vetted reporter. Those choices never authorize publication or public identification; either requires your later, separate, specific confirmation.

Encryption key and technical details

This fingerprint lets an investigator confirm that the site supplied the expected encryption key.

Loading…

Key ID: Loading…

Field and file contents use AES-256-GCM. The one-time content key uses RSA-OAEP-4096. SHA-256 provides the public-key and sealed-submission fingerprints.

JavaScript is required only for this form’s local encryption. The dossier itself remains readable without JavaScript. Do not send sensitive evidence through an unencrypted alternative.

Verifying this site’s encryption key before enabling the form…

Start with what happened

Choose a submission type, describe the evidence, and complete two safety confirmations. Every other field and every sharing choice is optional.

About this submission

What best describes this submission? (required)

Describe the evidence

What happened, and what supports it? (required) Tell us what you personally observed, when it happened, how you know it, and which records support it. Clearly identify any conclusion or inference.

Supporting files

No files selected. Up to 10 files, 25 MB each, 100 MB total.

Add dates, wallets, promises, or loss details Optional details that can connect your account to transactions and calculate harm

Relevant public wallet addresses or transaction hashes Enter only public wallet addresses and transaction hashes. Never enter a seed phrase, private key, password, or recovery code.

Relevant dates or date range

Advertisement, promise, or statement you relied on Quote or describe what you saw, where you saw it, and approximately when. Attach a screenshot, link, email, or original platform export if available.

Purchase and staking details Include dates, SOV quantity, purchase price or cost basis, staking transaction, lock duration, fees expected, fees received, and whether you later unstaked or sold.

Your loss calculation and supporting records State the amount, currency, valuation date, and method. Attach exchange statements, wallet records, staking history, tax lots, or calculations that support it.

Add identity, contact, or a follow-up request Optional; leave these fields blank if you do not want a reply

Name or pseudonym

Country or jurisdiction Helps identify the relevant authority if you authorize confidential sharing.

Preferred contact method

Contact detail (required if you request a reply)

Contact details are encrypted with the submission. Leaving them blank does not guarantee anonymity if the evidence itself identifies you.

I consent to confidential follow-up using the contact detail I supplied.

What follow-up are you requesting? Describe what you want the review team to do next. A request does not guarantee a response.

Confirm and choose confidential sharing

Both confirmations are required. The three sharing permissions are optional, off by default, and never authorize publication.

I have described what I know truthfully, separated direct knowledge from inference, and understand that knowingly false submissions may harm victims and an investigation. (required)

I confirm that I did not include a seed phrase, private key, password, or recovery code. (required)

I authorize confidential sharing with victim-side counsel for evaluation and recovery work.

I authorize confidential sharing with an appropriate law-enforcement or regulatory authority.

I authorize confidential sharing with a vetted reporter. This does not authorize publication or identification.

No checkbox authorizes publication. These optional sharing choices do not authorize publication or public identification. Either requires your later, separate, specific affirmative consent.

Start with what happened

Submission encrypted and received