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

Allow challenger to provide a corrected version of the translation #22

Open
hbarcelos opened this issue Nov 23, 2020 · 10 comments
Open
Labels
enhancement New feature or request
Milestone

Comments

@hbarcelos
Copy link
Contributor

As suggested by @fnanni-0 here:

I think it would be great if the challenger could submit a translation with the corrections and claim the task price too. If the challenger wins, not only the translator is punished and the challenger is rewarded, but the requester gets the translation he requested instead of losing time and money.

This could improve requester's UX and potentially increase the payout of challengers.

Currently challengers can profit by finding a single issue with the translation which would make it non-compliant with the required quality tier. One can optimize this task by scanning for common sources of mistakes, for example.

With this change, if the challenger decides to put some additional effort into the task to provide a fully compliant translation, beyond getting the requester deposit, he would also be rewarded with the escrow payment from the requester.

The requester benefits because she would get the translation done. Currently she gets refunded of her initial escrow deposit, but will spend both money with gas and time waiting for the task. If she has a deadline, this might be a deal-breaker.

Some challenges remain on how to actually implement this:

  • Should we extend the current flow to allow the challenger to become the translator?
    • How much complexity would that bring to the smart contract?
    • Should we allow this process to be recurrent (a 4th party to challenge the original challenger's corrected translation)?
      • How to prevent and endless cycle of challenging that would keep the requester's escrow deposit locked in the contract for a long period of time?
  • Should we change the dispute ruling options to be non-binary and give jurors the ability to choose to accept the challenger's translation instead of the original translator's? (Suggestion made by @fnanni-0)
@hbarcelos hbarcelos added the enhancement New feature or request label Nov 23, 2020
@hbarcelos hbarcelos added this to the v2 milestone Nov 23, 2020
@epiqueras
Copy link

Should we change the dispute ruling options to be non-binary and give jurors the ability to choose to accept the challenger's translation instead of the original translator's? (Suggestion made by @fnanni-0)

This makes the most sense to me. Otherwise, the process could become even slower.

@eccentricexit
Copy link

eccentricexit commented Nov 23, 2020

I really like this. One strategy challengers use in the t2cr is to only challenge regarding one mistake so that they can profit again later. I think this would discourage this behavior.

I believe it would change quite a bit of the contract, because we'd need add some recursion to allow challenges to the challenger's submission and so on.

I'd say spend some time on the contract and see if it gets too complicated.

@fnanni-0
Copy link
Member

Another thing that could be interesting, but has the drawback of adding even more complexity to the contracts, is to allow some kind of settlement outside of court.

For example, if I submitted a translation and someone challenged it with an improved version of it, I could admit my mistake and share the task price with the challenger instead of going through the arbitration process with the certainty that I'm going to lose. One problem of this though, is that I would have incentives to challenge my own submission unless we allow the challenger to also get challenged. And maybe incentives for sloppy submissions would increase too.

@fnanni-0
Copy link
Member

I think of challengers as first instance judges (or something like that)

@epiqueras
Copy link

That's like a snake that eats its tail.

The non-binary ruling still makes the most sense.

@hbarcelos
Copy link
Contributor Author

Yeah, I think having 3 ruling options would suffice:

  1. Approve the original translation.
  2. Reject the original translation.
  3. Approve the translation provided by the challenger.

Changes in contract would be significant, but not in a sense that everything would have to be done from scratch.

@fnanni-0
Copy link
Member

Now that I think about it 2. and 3. are a subset of "reject the original translation" and that could be a problem. How does an arbitrator deal with the following situation:

  • 4 jurors vote 1.
  • 3 jurors vote 2.
  • 2 jurors vote 3.

Here 1. wins, but there are 5 jurors voting for options in which the original translation gets rejected.

@epiqueras
Copy link

A policy can say to pick the provided translation, if suitable.

@hbarcelos
Copy link
Contributor Author

Here 1. wins, but there are 5 jurors voting for options in which the original translation gets rejected.

Well, that's how a voting with 3+ options work. If it is not required a simple majority to determine the winner, the most voted option wins.

Depending on the way the policy is phrased, those 3 options can be considered mutually-exclusive. I don't think that's an issue, it's how it should work.

@clesaege
Copy link
Member

Yeah, it could be an option and he would have the evidence period to make the new translation.

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

No branches or pull requests

5 participants