pdobacz
pdobacz
A common scenario now is that: 1. Alice places a deposit 2. Alice's Watcher waits some finality and reports the deposit as a spendable UTXO 3. Alice wants to spend...
## Preface This issue aims at explaining the current behaviors of the child chain server and watcher implementations, with regards to the (perceived, but not accurately precise) feature dubbed "0...
(I think there used to be an ancient pivotal/Jira ticket for this, but submitting a fresh one is easier ;) ) In #1421 an (unlikely) edge-case failure of the operator,...
Coming from #1275, which in the end opted to take a different approach to solve. > separate the conflated unchallenged_exit from invalidly_processed_exit and have things called by their name. The...
From discussions with @boolafish @Pongch. When a contract upgrade (e.g. a new `ExitGame` contract) happens, users need to upgrade their watchers before new type txs keep flowing through the system,...
It is unlikely to be exploitable or even affect us in real-world operation of the child chain and watcher but is an issue intrinsic to `OMG.State` making its behaviors surprising...
Unless this got obsoleted altogether, due to code moving to `ex_plasma`, this comment should be observed and followed, for inputs and outputs alike https://github.com/omisego/elixir-omg/pull/1164#pullrequestreview-338823576 > > InoMurko 17 hours ago...
It seems there is an unexpected resonse from the said child chain's endpoint that can confuse the watcher. It would be when the JSON response from that RPC is decoded...
Reported by @jarindr: - `transaction.submit` and `block.get` use signed - `in_flight_exit.get_data` use signed - rest of security critical API uses unsigned (all challenges, byzantine_events etc) - `transaction.all`/`get` not sure in...
Expanding on the original issue `OMG-349 - Include IFEd txs in blocks?`. With the new learnings, it is apparent that the more involved model (called `exoife` below) turns out to...