Dispute #249

Court Start Date Dispute Status Current Period Time remaining End Date
Curation 2020-07-10 20:51 Already Ruled Execution Already Ruled 2020-07-24 16:21
Arbitrable Creator

Unique Votes in all the rounds

Yes No Refuse to arbitrate Pending
3 0 0 0

Round 0

Yes No Refuse to arbitrate Pending
3 0 0 0
Round 0 Vote Casting Date
Yes 2020-07-14 14:22
Yes 2020-07-20 04:15
Yes 2020-07-14 15:16


Evidences provided by Vagarish

Evidence #1:

The meaning of launch is clear We are speaking about a decentralized application, so let's look at the wikidictionary: https://en.wiktionary.org/wiki/launch Multitude of definitions are applicable there but are all basically "to put in operation". So this may bring us to the next definition of "operation" https://en.wiktionary.org/wiki/operation "The method by which a device performs its function." To perform its function the software must necessarily be running, so if the Augur team announce a launch, but the contracts don't finish deployment prior the deadline, Augur would not have been put into operation so it should resolve as no. If the Augur contracts are deployed, but people can't access it, or know about it, Augur would not be able to perform its function (prediction market). If people can't predict on it, it isn't functioning, so it isn't operating so it isn't launched.

Evidence #2:

Challenge Justification What constitutes "launch" in this context? If Augur deploys but doesn't announce a launch, valid? If Augur announces a launch but contracts don't finish deployment prior to the deadline, valid?
Check this Case on Kleros Resolve