-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🕵️ How do you think we could highlight independent fraud analysis? #35
Comments
Linked thread is a great example - where do most people develop and post this kind of content? In this thread the author doesn't seem to mention how onlookers could review the listed information, or how they could see more similar info (besides following the user of course) Maybe that's the point of X and similar social media. To your question - First, on the content side, I think either we'd need to encourage users like this to embrace the group mission and post on a decentralized place either like this one or one that we can hook into, or we would identify value users who do this kind of work and archive and scrape whenever they make similar threads. How to highlight it, I think if folks are interested in this and there is a directory, perhaps that could help - but does the centralized social media already fit that niche with tagging / for you page / etc? This bit: "10/ So what does this mean for crypto security? • Multisigs aren't foolproof if human signers can be compromised I would argue all of these points are things we have known about blockchain since it was invented - the takeaway for me is that folks had the hubris to think that any of these problems were solved. |
LocaleI've mostly seen this kind of content posted on X so far, with a large deferred intention of social clout. Namely, it doesn't seem the main individuals I've investigated receive any direct remuneration for their investigative work, although surely there are some exceptions here. Often they come from semi-anonymous pseudonym accounts, which makes sense given retribution from caught fraudsters. Notwithstanding the risks, this thread is an exemplary example of self-monetization by plugging the user's proprietary trading platform at the very end. Content ReviewAgreed, often the materials on X don't include blockchain explorer links or more comprehensive content explanations.1 Maybe it's trying to keep posts short, maintain interest on the site (via the algorithm), or something else. Notwithstanding, given the immense existing private employment investments in abating fraud, it seems like one of the simplest things to reward more thorough engagement with. I'd say the parallel to the software and contract worlds would be bug bounties, whereby anyone who self-identifies challenges has a "white-hat" way to sustain future work. Oh yeah, reading your thoughts 🧠
Yes, this, awesome! A fun thought experiment, I think, is how to incentivize such power users (with technical skills) to build open bots adept at automatically identifying suspicious activity. The parallel to central work here would be most easily exemplified through cybersecurity, whereby large amounts of vulnerabilities get flagged for review. The latter part on continually hooking into central venues (as I understand the intent) – how might we set something like that in place? Organizing DiscoverabilityTough to say on this because there are so many users on so many chains working on these items. I love the idea of getting everyone on the same page to solve some of the longstanding challenges facing practically all projects, especially considering "bad" actors. That latter part probably needs explicit governmental definitions or at least guidelines (in terms of the DAO, not legacy nations). I was originally thinking of this as framing the innovative distributed analysis possible today on popular chains, along the lines of lightening the government's workload with private incentives. Footnotes
|
like this
I think it will help with decentralizing the regulation
The text was updated successfully, but these errors were encountered: