Information about detecting multi-accounts are easily available online. There are no such hidden technology. I have done some study since it seems I am heavily involved in this case.
1. Programmable tools/methods/studies:
- IP Addresses
- HTTP Referrer
- Cookies & Tracking Scripts
- Super Cookies. Example
https://samy.pl/evercookie/- User Agent
- Browser Fingerprinting. Example
https://panopticlick.eff.org/Ref:
https://www.howtogeek.com/115483/htg-explains-learn-how-websites-are-tracking-you-online/But all have their weakness. So one can not be 100% sure if someone is multi-accounting. Here is a good read:
https://superuser.com/questions/1036422/how-can-a-website-recognise-a-multiple-account-usageAs you have noted, all of these methods have one main drawback: they are a PITA for people legitimately sharing computers and other devices. If you're designing a service that relies on users having only one account, then instead of preventing multi-accounts, design it in such a way that makes having multiple accounts pointless. This site is one example of such service: people gain reputation for doing things that are beneficial for the community. Newly created account has low reputation and is severely limited. As it gets reputation points, some capabilities are unlocked (eg. commenting everywhere) and user gets some bonuses (limited ads).
I am really interested to know what determines sportsbet that OP is multi accounting, and they are 100% sure. I do not find a rocket science method/study except the above mentioned references.
2. Then we have KYC which needs human involvements (with automated image reading/scanning and cross-checking with the central database provided by the authority like they do when we pass immigration)
An online KYC involves, cross-referencing name, address, city and other details using ID card (driving license, passport), utility bills, bank statements etc.
I am really interested to know which information of the KYC determines that OP is multi accounting and KYC isn't passed?
3. Then we have blockchain evidences and other payment systems. We can track the deposit/withdrawal references for both blockchain and traditional methods.
Weeks ago there was a case against bitcasino and
Karl came up with some solid information that was undeniable so it was accepted by most of us without further questioning.
What happened in this case?
Sportsbet.io should still privately to the client or even publicly state why the client failed the KYC procedure, while protecting the clients privacy, as they have done so previously:
I don't know if that really can prove or disprove multi-accounting. The client can be a jerk about it and say Sportsbet is lying even if the proof is correct. It's not something that can be verified independently (e.g. on the blockchain)
so basically in order to use is as proof you have to trust Sportsbet anyway.Would we say the same if this was fairly new sportsbook or if the claim came up from a very well established forum member?
What would we do if some reputable members who play poker regularly in SwC files a similar case against a reputable bookie? Which side we will trust?
This is livecoin all over again.
Livecoin failed to be transparent or a user failed to bring enough proof?