Public Nuker Registry

Every server using Versa automatically benefits from one shared global archive documenting every person or bot proven to have destroyed a server — no extra setup required, and with zero impact on protection response speed.

What gets recorded?#

  • Every real protection punishment: any ban/kick/timeout/role-strip protection executed against a real actor — human or bot — is recorded with the type of destruction, the server, and the exact roles they held at that moment.
  • Every bot addition: who added any bot to any server, and whether they were trusted at the time — automatically linked later if the added bot turns out to have destroyed the server.

Recording covers every kind of destruction the protection system detects — mass channel/role deletion, mass kick/ban, malicious webhooks, raids, and more — because it's hooked into the shared execution point used by every protection feature, not just one.

Across every server at once#

The archive is shared between the main bot and every private bot instance — if someone destroys a server protected by any bot in the Versa family, they immediately show up in the registry for every other server, even one running a completely different bot instance.

The Public Page#

A complete, public record — reachable by any visitor without logging in — at versaiq.xyz/known-nukers. For each person it shows: Discord ID, username, avatar, incident count, number of affected servers, and the full detail of every incident (server, punishment type, reason, and the roles they held at the time) on their profile page.

The Proactive Alert#

If someone with a prior destruction record (on any other server) joins your server, you get an instant alert in your security logs channel — the same channel you configure from the Protection page → Security Logs → Alert Channel — including a direct link to their full profile.

The Protection Page Warning#

The Protection page in the dashboard automatically checks your current members against the registry — if any of them are recorded, a red warning appears at the top showing their name, incident count, and a link to their full profile.

How does it work with zero impact on protection speed?#

1

Protection punishes the attacker first

The decision and execution (ban/kick/role-strip) happen at maximum speed, with zero waiting on any database write.

2

Recording happens in the background

Writing the incident to the registry is fired without waiting for its result (fire-and-forget) — even if it's delayed or fails, the punishment itself is never affected.

Wrongly-flagged record?

If a specific incident turns out to be the result of a stolen token or a clear mistake, the team can review it and permanently remove it from the registry when contacted through the official support server.