The Double Counter fingerprint

A Discord ID is a long string of digits nobody remembers. A fingerprint is five words you can read out in a voice call, paste into a mod log, or compare at a glance with the one in a ban note from last month.

It sits in the Signals section of every report, under the three counters, on every plan. When the same five words turn up on a new account, you are looking at someone you have met before — whatever name, avatar or server they come with this time.

That is the moment it is made for: a ban evader starting over with a new name and a new avatar. The fingerprint is the part of the report that is about the person, not the profile.

Because the fingerprint belongs to the person rather than to one account, it works as a shared reference between moderation teams. When you ban someone, keep the fingerprint with the reason. When another server's mod team asks whether you know an account, compare fingerprints instead of screenshots.

It also makes your own records hold up over time. Accounts get deleted and renamed; a note that says “fingerprint amber-orbit-quiet-fossil-nine, banned for raiding” still means something a year later. Pair it with the watchlist and the next account that person makes finds its way back to you. It helps inside your own team too: a fingerprint in a handover note says more than a username that may have changed by the next shift.

Some reports show “To be generated” where the five words should be: Double Counter has not built a fingerprint for that identity yet.

The rest of the report works the same. The counters, the linked accounts and the network map do not depend on the fingerprint, so a missing one is no reason to skip the certain layer. Search the account again later: the report is rebuilt on every search.

A missing fingerprint does not mean the account is clean or new, and it does not make it suspicious either: the five words are only not there yet. Judge the account on the counters and layers you can see, and leave the fingerprint column of your mod log empty until the next report.

The fingerprint is an identifier, not a description. The five words say nothing about the person, where they connect from or how their accounts were matched; they are a label for an identity, generated from the behavioural signals Double Counter has captured.

That keeps it safe to write down and share with other moderators. It helps you recognise a returning member; it tells nobody who that member is outside Discord.

Treat it the way you treat an account ID: a reference your team can quote, compare and look up in its own notes, not a piece of evidence to post in public. When you share it with another server, share it moderator to moderator, with the reason you are asking.

Most mod teams already keep a log of bans and warnings. Add a column for the fingerprint, filled in from the report when you act on an account.

When someone new joins and Doogle shows a fingerprint that is already in your log, you do not have to argue about writing styles or join times: the log tells you who it is and why they were removed.

Keep the fingerprint next to the account ID, not instead of it. The ID tells Discord which account to act on; the fingerprint tells your team which person it belongs to. Together they make a ban note that still makes sense after the account is gone. A plain spreadsheet with the date, the ID, the fingerprint and the reason is enough to start.