what do we want to use for dispute resolution long term?

[owocki]

https://kleros.io/ Delphi

[owocki]

@mbeylin do you think Delphi is on the roadmap still? were evaluating our options and obvi would prefer Delphi if it's going to beshipped soon.

cc @vs77bb

[mbeylin]

Yeah we're putting a bit of a pause on Delphi as it isn't something we're squarely focussed on for the immediate future. All of the code for Delphi is open source https://github.com/Bounties-Network/Delphi however we've come to realize the designs are not in a completed enough state to begin being deployed in production.

[0xferit]

Happy new year!

Do you plan to implement dispute resolution anytime soon? I would like to help to integrate with Kleros.

[owocki]

its something we'd love to integrate. there is an address in standard bounties for the arbiter address that we could plug a kleros (or similar) dispute resolution framework into.

[0xferit]

@owocki Could you direct me to the source code please?

[owocki]

@ferittuncer _arbiter in https://github.com/Bounties-Network/StandardBounties/blob/master/docs/documentation_v1.md

[0xferit]

I think we can write an adapter contract to plug ERC 792 Arbitration Standard to Bounties Network API.

Here is a similar contract written for Realitio.

https://github.com/kleros/kleros-interaction/blob/master/contracts/standard/proxy/RealitioArbitratorProxy.sol

https://etherscan.io/address/0x701cabaf65ed3974925fb94988842a29d2ce7aa3#code

[clesaege]

I looked at the bounty contract and the issuer can call killBounty to be reimbursed and changeBountyArbiter to change the arbiter. So in this contract the issuer has full control.

We could:

• Make a new contract based on StandardBounties which remove the changeBountyArbiter function and allow the arbiter contract to killBounty instead of the the issuer.
• Keep the contract, but make gitcoin users create bounties through another contract which would then call StandardBounties. This other contract would be the issuer (and not the bounty creator). Some functions allowed to the bounty creator would be proxied but not changeBountyArbiter nor killBounty.
• Have an entirely new contract.

[0xferit]

Hello again @owocki

I'm starting to work on this.

My plan is:

• Make a new contract based on StandardBounties which remove the changeBountyArbiter function and allow the arbiter contract to killBounty instead of the the issuer.
• Use resolver.kleros.io for submitting evidence and appealing so changes to Gitcoin UI would be very minimal
• Implement logic to make Gitcoin UI support both the new contract and the old contract at the same time.

Does this sound good to you?

[marsrobertson]

Interesting:

• https://court.kleros.io/cases/169
• https://court.kleros.io/cases/170

Low tech but good enough for now.

Need some attention and publicity though.

Kleros protocol works if there is a bunch of internet trolls extracting "free money" from the appeal system.

Otherwise, it is possible that 3 guys are chosen, 2 didn't vote, 1 single juror makes the ultimate decision.

[owocki]

would it help if i gave those disputes some publicity / channeled some of the debate there? the reason we chose twitter for this round was that its simple and has wide distribution

[marsrobertson]

Posting to Twiter is great!

I happened to find it because I have a personal dispute: https://resolve.kleros.io/interact/172

Just saying the Kleros protocol works best when there is plenty of guys scrutinizing the decision, appealing to get "free money". On the other hand, a party in a dispute can fund the appeal themselves. More eyeballs mean more scrutiny. There is a dedicated https://t.me/klerosjuror group of guys paying close attention.