elixir-omg

elixir-omg copied to clipboard

`/in_flight_exit.get_data` crashes on attempt to IFE transactions spending spent deposits

8

``` watcher-0 watcher 2019-11-12 05:32:11.728 [info] module=Phoenix.Logger function=phoenix_error_rendered/4 request_id=FdZTUg-b4_1fYRkABSMB trace_id=6798762404176944400 span_id=3860092244967034233 ⋅Converted error {:case_clause, {:error, :no_deposit_for_given_blknum}} to 500 response⋅ watcher-0 watcher 2019-11-12 05:32:11.730 [error] ⋅#PID running OMG.WatcherRPC.Web.Endpoint (cowboy_protocol) terminated watcher-0...

0x234

This is a dead simple / last resort / out-of-band, competence-separated addition to #1277. 1. Create an S3 bucket for block storage, with contents readable by the world, writable by...

paulperegud

Discussion on authority address: design, usage, future

1

Place holder for a discussion on the rationale behind the current authority address usage (https://github.com/omisego/elixir-omg/blob/e127775203c0ed2e3fdd2fad3e7611898186b023/docs/details.md#nonces-restriction), and future design of this implementation. Strict use of nonces for reorg protection has impact...

0x234

While doing https://github.com/omisego/elixir-omg/pull/1397, (that was reported by https://github.com/omisego/elixir-omg/issues/1128 and https://github.com/omisego/elixir-omg/issues/1310), we realized that the root problem is a bit more complex than what's describe. Indeed it's not currently possible to...

mederic-p

If too many events are published inside a block they can't get through to datadog because statix crashes. I've noticed that with 200+ events in a block (read 200 deposits...

InoMurko

As a user I would like to be able to know what caused an invalid_exit byzantine event

1

### Description In my current environment the watcher reports an invalid_exit byzantine event. Based on the information provided by `/status.get` it is cumbersome to trace down what exactly caused the...

thec00n

Split invalidly processed exit from unchallenged exit events

2

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...

pdobacz

Block explorer includes the following user story (BE [Issue 36](https://github.com/omisego/blockexplorer/issues/36)) > As a user I would like to see a list of most recent blocks with their associated ETH `tx_hash`....

unnawut

Watcher Info API: /deposit.get

2

**Scope:** Watcher Informational API **Endpoint:** `/deposit.get` **Request:** ```json # /deposit.get { "eth_hash": "0x2733e50f526ec2fa19a22b31e8ed50f23cd1fdf94c9154ed3a7609a2f1ff981f" } ``` Request params: - `eth_hash`: the rootchain's exit transaction hash **Response:** ```json # /deposit.get { "success":...

unnawut

Watcher Info API may have exits before their respective blocks exist

1

Continuing from https://github.com/omisego/elixir-omg/pull/1123#discussion_r352586370. > `ExitStarted` events will go straight to the `Consumer` without waiting. (the `exit_processor` listener :point_up:, which will trigger that, doesn't wait for blocks **by design**, so one...

unnawut