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

Two parties pay appeal fees and simple insurance mechanism #126

Closed
whwgeorge opened this issue Sep 18, 2018 · 0 comments
Closed

Two parties pay appeal fees and simple insurance mechanism #126

whwgeorge opened this issue Sep 18, 2018 · 0 comments
Assignees

Comments

@whwgeorge
Copy link

Denote by x the total amount that must be paid to jurors in an upcoming appeal. In case of appeal, the party that won the previous round should pay x+s_A in appeal fees while the party that lost the previous round should pay x+2s_A in appeal fees. If one party pays appeal fees and the other does not, the party that pays appeal fees wins the dispute. If neither party pays appeal fees, the previous decision stands. The party that ultimately wins (after all appeal rounds are concluded) receives all the remaining value left over after the jurors are paid. The period for the party that won the previous round to pay her fees should be after that of the party that lost the previous round.

s_A should be a parameter that can be tuned by governance: default recommendation s_A=x.

Additionally, create system for appeal fees to be "crowdsourced" by third parties. Namely, individuals can pay a portion of the fee. If enough is raised, the appeal is financed and any stake s_A or 2s_A that that party receives if she wins due to that round is split proportionally between the crowdsourcers based on contribution size.

See:

https://drive.google.com/file/d/1y67t-NJUjRPNkp1UB8lDJWas9Sb9KFU7/view?usp=sharing

for more details and analysis. (Crowdsourcing proposal on pages 1-2.)

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