chore: ethereum oracles acceptance criteria updates

[MuthuVega]

No description provided.

[wwestgarth]

Can we have an AC for sending in a malicious eth-call chain-event that didn't happen on chain? I think this is important given the security issues we found before. We need to make sure that the on-chain-verification step works and we can only do this with a negative test.

Edit: you can add this in another PR to not block this particular PR.

[MuthuVega]

Can we have an AC for sending in a malicious eth-call chain-event that didn't happen on chain? I think this is important given the security issues we found before. We need to make sure that the on-chain-verification step works and we can only do this with a negative test.

Edit: you can add this in another PR to not block this particular PR.

Think the above is covered by this acceptance criteria

6. Will need some tests around consensus, will require setting up a network and having some nodes receive different values for the same oracle data point and testing that the oracle data point is/is not published depending on voting (<a name="0082-ETHD-035" href="#0082-ETHD-035">0082-ETHD-035</a>)