boolafish

sure just make sure this issue or there is some issue left tracking this

@pnowosie I think I did not get what you mean 😅 Are you saying that DD is the only consumer of the OMG.bus for the exit events, and it is...

This is a bit tricky though...because only the specific watcher that receives the `/transaction.submit` request would know such account related info. I think ideally it should be the responsibility of...

Don’t forgot previous awesome work from @unnawut . https://github.com/omgnetwork/elixir-omg/issues/1660 The new column family thing looks pretty good to shard by address to increase performance

> Whole UTXO set cardinality is below 10M BTW, it will be nice to have some documentation or investigation on the impact of UTXO set actually goes over that. I...

> But instead of maintaining two "ledgers" we refactor the current storage to use just the partitioned one. how.....do you do that though? BTW, also want to bring this out...

as discussed as slack, the problem is ALD does not have the assumption "owner address" would definitely exists for all output type. It is on each output type to define...

[more like for discussion, probably not too much suitable for the task] If there are multiple metrics, we might consider to invest some time to see the possibility of stream...

Hmmm, interesting. I think to enable `exoife`, we would also need to make sure we can handle the case of competing IFE shows up. If we are aggressively including one...

> Hm, this sounds like Watcher's responsibility (and we're doing it - Watcher will do its best to challenge the non-included tx with the included one, and not the other...