EndymionJkb

Decided not to do it. Other fees don't give both values (e.g., in ProtocolFeesProvider); subgraph does have enough info, just a little more work.

Thanks! It's a bit broken at the moment (by some merges: I actually didn't intend to push it that last time). Will update it soon. On Thu, Jul 14, 2022,...

Superseded by #1792 (and others to follow)

> > It only works when there is a deployed contract; hence changes to use existing Mock contracts instead of calling the library directly. (ManagedPoolStorageLib tests could be covered if...

Closed for lack of interest

Inspired by #1816 , I have a version of this with a 66-bit weight complement that likewise removes compression, and contains a detailed range analysis (to remove compression from the...

> I checked and we can actually remove `CircuitBreakerParams` as we don't get stack issues if we just pass in the the 4 fields separately. This could help readability and...

Thanks, @jubeira !

What we should do ultimately depends on who is using the artifact files and for what purpose. It looked like the deployment tasks always used the build-info, but the artifacts...

Can we close this now, after the last TimelockAuthorizer deployment?