pdobacz

> Ensure that the watcher can continue to perform its security-critical functions in all detected byzantine conditions AFAIK, this is true, as long as the user is abiding by the...

> if this piece of info is explicit then it should be enough. how would you see it made explicit (except for the docs as Kasima outlined, which I suppose...

> So we serve them on the first occurring basis. yeah, so instead of returning `late_invalid_exits_events` as done now, you should just tap into this: https://github.com/omisego/elixir-omg/blob/master/apps/omg_watcher/lib/omg_watcher/exit_processor/core.ex#L408 and append a single...

> > The event is already logged, the issue is that there's no details attached ... > > What kind of log would be sufficient? Hm, I'd say anything sufficient...

this https://github.com/omisego/plasma-contracts/pull/475 seems to help address the issue: > An IFE that is started but never piggybacked will timeout tacitly and hence remain in the report forever

Took the liberty to edit the task list and mention that one item is now **tracked in https://github.com/omisego/elixir-omg/issues/1279**

Thanks! I just ran into this same thing during the Watcher exit load/perf testing too :(. It is caused by an attempt to start an IFE using a _spent deposit_...

Ay, I just realized there is a case for starting such an IFE, so I'll add some more priority to this. The use is where the IFE spends a spent...

Here is an alice-bobbing scenario relevant: (it is a variant of [this](https://github.com/omisego/elixir-omg/blob/master/docs/morevp.md#operator-tries-to-steal-funds-from-a-multi-input-in-flight-transaction)) 1. Alice spends UTXO1a (not necessarily a deposit), Malory spends UTXO1m (**a deposit**) in TX1 to Bob, creating...

a note on JSON-RPC: chch and watcher used to do JSON-RPC (in order to be in-line with Ethereum JSON-RPC). We changed to HTTP-RPC in order to be in line with...