You are viewing a single comment's thread.

view the rest of the comments →

0
0

[–] collegetoker ago  (edited ago)

Couldn't you resolve this with accounts attached to cryptographic signatures to ensure that users aren't abusing the system? Also if you're using credit cards as the payment method, couldn't you blacklist a card that has been shown to exhibit fraudulent activity? This same principle could be applied even if you are using a payment processor to convert dollars into bitcoin.

Also, you can check for mock locations (in android), preventing automated abuse.:

public static boolean isMockSettingsON(Context context) {
    // returns true if mock location enabled, false if not enabled.
    if (Settings.Secure.getString(context.getContentResolver(),
                                Settings.Secure.ALLOW_MOCK_LOCATION).equals("0"))
        return false;
    else
        return true;
}

0
0

[–] Vailx ago 

As to the first, no. If I can have one anonymous account, I can have hundreds. If I can share one with someone, I could share one with hundreds.

If credit cards are involved, SURE, that would absolutely work. Now you have a central location though, a repository. It's not peer to peer any more. Still, a credit card is unique enough that if you could find a way to use that in a way that was peer to peer without revealing the card info to everyone, like those encryption methods that allow transformations to be applied... hrm. Honestly, there COULD be a way to make this part peer to peer.

As for the code based tech check, I'm sure there's somebody who has a way around that stuff. Your second part seems doable and really great though.