Skip to content
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

Decide on rewards & incentive structure for scrypt verification #47

Open
sinahab opened this issue Nov 28, 2017 · 2 comments
Open

Decide on rewards & incentive structure for scrypt verification #47

sinahab opened this issue Nov 28, 2017 · 2 comments

Comments

@sinahab
Copy link
Collaborator

sinahab commented Nov 28, 2017

There is no jackpot in the current scrypt-interactive design; verifiers do not expect to earn rewards at equilibrium, as claimants will not submit incorrect claims.

To keep things simple in this proof-of-concept, we can assume that verifiers are altruistic. This means that: we need to run multiple independent verifier clients at different geographies.

Furthermore, we need to decide how to price the deposit required for being a claimant or verifier. This brings up multiple points:

a) the deposit should be partly burned (e.g. 60% burned, 40% transferred from loser of verification game to the winner). This is to prevent an attack where someone keeps challenging their own claim, indefinitely DoS'ing the system, without losing any deposits.

b) what should the actual deposit value be? A good candidate is deposit == 2 x (gas costs), or perhaps even more. This makes it costly for someone to submit bogus claims, while also remunerating verifiers.

c) we need to protect against an attack, described as follows: the attacker knows the total amount of deposits the altruistic verifiers have available. Therefore, it creates enough claims to bond all these deposits, and then some more. These extra claims will go through unchallenged. The solution to this is to limit the number of parallel claims.

@teutsch
Copy link

teutsch commented Nov 28, 2017

Why 60%?

@hswick
Copy link
Contributor

hswick commented Jan 8, 2018

This should be addressed by @sinahab's recent protocol work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants