CS = Crypto-Scam
Thank you all for your questions and ideas. Thanks to them I've developed a better abstract concept of handling crypto abuse. Before answering your concerns separately I'm gonna draw the whole picture of the working mechanism and hopefully your question will be answered meanwhile.
As mentioned several times before, such database will rarely be queried by anyone before sending coins. That's the reason why integration with major wallets is a must so they can help automate that process and actually advertise it to the user; what I mean is, there are two ways in which wallets should affiliate with CS:
- Receipt checking - Before executing a SEND order wallet app queries CS database and checks if the receipt address is fraudulent, because average user won't do that by himself
- Address reporting - I believe a very very small amount of crypto users will actually go to http://crypto-scam.io/report and fill a report with an abusive address they spot online, because that would require them to: a) open a tab in browser, b) lookup the domain of CS in case they forgot it, c) find a way to append the abusive address, d) fill other required info - given more and more people are using smartphones it's a general tedious process. If wallet devs would implement in-app reporting mechanisms to CS that would be great in terms of accessibility and more abusive addresses would be discovered, because people tend to be familiar with wallet app's interface instead of the one of another site.
I believe anyone should be able to report addresses without the need of some account registration. The cryptocurrency world is vast with many users, requiring each to create an account to report may be exhausting for server and possibly a privacy killer depending on the required registration data. However, as posts here have mentioned, reports themselves cannot be trusted and must be validated. For such issue I propose a dicing system, what do you think of it?
https://i.imgur.com/nZnjALD.png (image)Steps: 1. Humans are applying as verifiers. Verifiers are manually confirmed by CS webmasters to make sure they aren't bots or criminals. They will later check and validate reported crypto addresses. Because not many may enjoy browsing a website daily to do that, they will use a CS website interface and a custom android/iOS app.
2. Within wallet application someone reports abusive addresses.
3. CS sends the report to 3 random verifiers across globe to validate it and set the state of the address - scam or not. State of address is decided democratically. In case one or more verifiers is not online the report is passed to others worldwide. This method is more secure because in case a verifier itself is an abuser and reports addresses for no reason he can't be sure he'll be the one to incriminate the false-positive.
4. Before executing SEND order, wallet checks the state of receipt address with CS.
I think this is very similar to, Bitcoin Abuse Database. Maybe you can look at that thread and see what other members are saying, pros/cons.
It's similar to that with few exceptions: CS database will support more than BTC addresses, and will have a different verification system for deciding whether a report is fake or not.
Without a software wallet integrating such thing, this will just be another list that most beginners won't ever see...
There is no need for a new wallet. Already existing ones can use CS via the public API it offers; for example:
https://api.crypto-scam.io/a/0x3Ae5c187FDB90553Cc439b1ee7341C0D2461688A/rep,type. They just need to code it in their app and ship a new version with it.
- Any plans for its adaptation or you're just hoping for the best?
I've started this last week; project is still in beta phase - that means features are to be added, bugs to be fixed and tests to be made before asking popular wallet software developers to use CS. After being confident the backbone of the service is reliable I'll ping them, starting with those open source.
- At most, a centralized so-called crypto wallet might use it but at the same time, a lot of users have switched their wallets to something with little to no restrictions.
As mentioned before there's no need for a centralized wallet but I understand your point - yes, it will take time until wallets will make use of CS database. However things will speed up if service proves to be efficient, and that can be achieved by implementing meaningful tested features.