Paul Peregud

In the mean time this can be used as a workaround. ``` def arr_eq(field[256] a, field[256] b) -> (field): field equal = 1 for field i in 0..256 do equal...

Gents, Firefox is a great browser. Please add support :-)

Having to choose dependencies basing on "does it still support CommonJS" criterion is annoying. Following this issue.

My use case is cloning and building for CI.

Apparently, this behavior might be against ERC20 standard (or at least against its idea). It would be nice if we could ignore the misbehaving token.

@Nikodemek18 yep, here is the result of my meeting with him: https://github.com/omisego/research/issues/95#issuecomment-499614468

This trick might work because: 1) venue has quite a lot of time to compute such snark 2) CPU time is cheap, and venue is well motivated to do that...

> We can probably solve this by decreasing challenge period, or just make sure challenge period is, for instance, half of the period of “exitable” waiting period. I believe that...

> We would need to know where to exit to though. IDK, AuthenticationScheme would be able to provide where to exit? Previously this info would either be owner or outputGuard....

> Or, we can even make each output predicate handles only one authentication api. So the output type would act as AuthenticationScheme ID. This is the exact scenario I want...