Felix Leupold

Thanks for the explanation. In my use case I have a very large number of public input parameters for a computation that I want to verify on the Ethereum blockchain....

Here is another use case that is currently using a third party gadget for calculating a finalized sha256 hash: https://github.com/barryWhiteHat/roll_up

Do we know how long the deep copy actually takes (e.g. compared to fetching the events since the last confirmed block)? This would help us prfioritize this task.

My concern is if this is worth doing at all.

> An alternative implementation could not strictly forbid withdrawal under incoming tokens from the solver but instead, look at the amount that is incoming (would need to go over all...

> Iterating over the max 30 orders and calculate the 'credited sum' The issue with this is that it breaks the unidirectional dependency of BatchExchange --> EpochTokenLocker. Now EpochTokenLocker would...

Here is the plea for not changing the smart contract (I'm not saying I'm strongly opposed to it, but feel like that view point is missing in the arguments so...

I'm however very concerned about the suggestion of merging EpochToken and BatchExchange as this is not an isolated change and will require re-reviewing the entire contract. I think if the...

#647 mitigates this somewhat in the viewer by only fetching the list of users required for this page once. This allows to fetch the open orders with a page size...

Yes that makes perfect sense.