---
# System prepended metadata

title: Automate Dispute Resolution

---


# Automate Dispute Resolution

As of now, we are manually resolving the dispute by proving force hash(assumption: Trusted guy from EWF would perform this operation).

Now we need to automate this process. Here are few approaches:


## Approach 1: 
This approach aims to re-process operating envelope id if consensus encounters any error (eg: ConsensusNotReached, ConsensusError).

![](https://i.imgur.com/uAuFkoT.png)
<br>

In this approach, the offchain plugin will poll the Disputed_oe_ids storage in certain intervals in order to get disputed oe_ids and re-process the the whole flow of commit and reveal.

The Disputed_oe_ids storage will be populated if & only if consensus encounters any error.

Pros:
1. Reward Issuance will happen on the basis of majority rules only.

Cons:
1. We'll waste resources of nodes by re-processing oe_ids.


## Approach 2:

Issue rewards based on recieved results.

In this approach, we'll calculated the correct hash by computing majority hash from the received hashes.

Pros: 
1. We'll not waste the resources of those participants who have already submitted computed and submitted their results.

Cons:
1. Majority Rule will fail if we didn't get enough submissions, by doing this the majority rule will not make any sense.



