Discord Evidence Preservation Guide for Web3 Incidents

When scams or raids hit, what you capture in the first 15 minutes decides the outcome. Here is a practical Discord evidence preservation workflow that Web3 teams can use today.

Why Discord evidence preservation matters in Web3

In Web3, attacks often cross channels, wallets, and tools. A single missing message link or timestamp can break your case, slow takedowns, and block restitution. Good Discord evidence preservation makes it easier to suspend bad actors, reverse damage, and brief partners before the scam spreads. It also helps your team avoid legal and privacy mistakes when sharing proof. Treat preservation as a core moderation skill, not a task for later. The goal is to capture verifiable, complete, and minimally handled records as fast as possible.

Prep your server for incident logging, roles and settings

Set up a private channel named #security-cases with access for a small Incident Response role and your lead moderators. Create an Incident Manager role that can view audit logs, manage channels in a limited area, and post in security channels, but cannot delete server wide logs. Require two factor authentication for anyone with moderation powers. In Server Settings, enable Community features so you can use built in safety tools and logging. Turn on appropriate verification and content filters to reduce abuse while evidence is being gathered. Add a short incident template pinned in #security-cases so staff can capture details in a consistent way.

Capture the essentials fast, links, IDs, and timestamps

Turn on Developer Mode in User Settings, Advanced, Developer Mode. This unlocks Copy ID for users, messages, channels, and servers. For any suspicious message, right click or long press, copy Message Link, and paste it into your case thread. Copy the User ID of the sender and the Channel ID. Note the exact UTC time you first saw the content and whether the message was edited or deleted. If there are on chain elements, record the wallet address, transaction hash, and where it was posted in Discord. Speed matters, since edits and deletes can happen within minutes.

Log edits and deletes, use Audit Log and safe bot logging

Use the server Audit Log to capture role changes, invite edits, webhook creations, and message deletion events by moderators. Route AutoMod and moderation events to a private log channel that only your Incident Response role can see. To preserve message content at the moment of send and before it is deleted, use a trusted, well maintained logging bot with minimal permissions, or host an open source logger yourself. Store logs in a private channel, and back them up to secure storage, not to a public dashboard. Avoid logging direct messages unless users consent and laws allow it. Do not rely only on screenshots, since audit trails and raw logs carry more weight when reporting to Discord Trust and Safety.

Screenshot standards that hold up during review

When you must screenshot, capture the full Discord window, include the channel header and the system clock. Switch your system clock to show seconds and use UTC for consistency. Hover over message timestamps to display the full time, then capture. Include the message link in your case notes so reviewers can jump to context if it still exists. Save as PNG to avoid compression artifacts. Do not crop or annotate the original. If you need to redact private data before sharing, make a clean original and a redacted copy, and note the reason for redaction in the case file.

File handling, checksums, and secure storage for Discord evidence

Name files with a predictable format like YYYYMMDD_UTC-channelID-userID-shortlabel.png. Generate a SHA256 checksum for each file and paste it into the case notes to prove the file has not changed. Store evidence in an encrypted workspace with strict access rules, such as a limited Google Drive folder with viewer only links for stakeholders, or an S3 bucket with server side encryption and access logging. Enable versioning so you can see if any file was replaced. Back up the case folder to a second region or provider. Keep a simple access log that records who viewed or downloaded a file and when.

Chain of custody, privacy, and a clear retention policy

Write a one page chain of custody note for each case. Include who captured the evidence, the device used, the UTC time, where it was stored, and any transfers or redactions. Limit distribution to a need to know group, and avoid forwarding sensitive content to public channels or external group chats. Set a default retention period, for example 12 months for routine moderation, and up to 24 months for financial crime or repeat attacker cases. Delete evidence on schedule unless a legal hold is in place. Follow Discord Terms of Service and local law, and never publish doxing details or private documents.

Escalation, reporting, and public comms that build trust

Report violators to Discord Trust and Safety with message links, User IDs, Channel IDs, and a short summary that cites clear policy violations. If the incident involves funds, include wallet addresses, transaction hashes, and any exchange deposit address that was posted. Coordinate with partner servers if the same actor targets multiple communities, and share redacted indicators such as usernames, avatar hashes, and wallet addresses. Post a short public update that confirms containment, explains what members should do next, and links to your official channels. Avoid posting raw screenshots in public. Share only redacted examples that teach members how to spot the tactic without exposing victims.

Learn Discord evidence preservation for Web3 incidents. Capture links, IDs, logs, and screenshots correctly. Store securely and report with confidence.