Ask HN: Why don't we have a global, unified database for scam reputation? | Hacker News Reader

Ask HN: Why don't we have a global, unified database for scam reputation?

5 pointsmysocialguard4 comments

We have global protocols for email (SMTP), global databases for IP reputation (Spamhaus), and global ledgers for money (Crypto).

Yet, when it comes to scam prevention, the data is incredibly fragmented. If a scammer uses a specific Telegram handle, a leaked bank account, and a crypto wallet to defraud someone, that data stays in isolated silos or restricted private databases. By the time one platform flags them, they’ve already moved to the next one.

I’ve been thinking about a community-driven "reputation layer" for digital identities. A place where a bank account reported in one country can be flagged for a crypto user in another, instantly.

I’m curious to hear from the HN community: 1. Is a decentralized, community-voted scam database viable, or will it always be gamed by malicious actors? 2. Why haven't big tech or financial institutions built a cross-platform API for this yet? 3. How do we balance the "right to be forgotten" with the public's need to be protected from repeat offenders?

I’ve started building a platform to address this called MySocialGuard (mysocialguard.com), using a community voting and comment system to verify reports across bank/crypto/social handles/phone number/e-wallet.

I’d love to hear your thoughts on whether this "decentralized trust" approach is the right way forward or if there’s a better technical architecture I should consider.

One reason is that you can get sued for libel or defamation. Another reason is privacy laws (weak to non-existent in the USA, but strong in Europe, Canada, and elsewhere).

Also the potential for abuse to destroy competitors.

That is a critical point. The 'Sybil attack' or malicious reporting to sabotage competitors is a real risk for any reputation system.

To mitigate this, we are currently designing a weighted reputation system for reporters. The goal is to ensure that a report from a brand-new account doesn't carry the same weight as one from a contributor with a proven track record of accurate flagging.

In the meantime, we are emphasizing the inclusion of verifiable evidence (like transaction hashes or communication logs) so the community can peer-review the validity of a report rather than just counting 'blind' votes.

It’s a constant cat-and-mouse game. Since we are in the early stages, I'm very interested to hear if you’ve seen any specific consensus models or 'Web of Trust' implementations that could help us prevent this type of abuse effectively.

You've hit the nail on the head regarding the biggest challenges for any reputation system.

On Libel/Defamation: This is why MySocialGuard doesn't act as a 'judge.' Instead of making definitive claims, we provide a platform for community-sourced signals. We are implementing a 'consensus threshold' model where data is only highlighted after multiple independent reports and evidence are provided, similar to how community-driven spam filters or 'Community Notes' work.

On Privacy (GDPR/CCPA): MySocialGuard is a live platform, and we are actively navigating these challenges. Our primary focus is on publicly used identifiers involved in transactions (like crypto wallets and business-related handles). However, balancing transparency with privacy is our top priority. We are currently building out 'Right to Dispute' mechanisms and strict data-handling policies to ensure we remain compliant as we scale globally.

I believe the 'public interest' in preventing financial fraud provides a strong baseline for this, but I'm fully committed to refining our legal framework as the platform grows.

Reply on news.ycombinator.com