Nicolás Venturo

Add read-only chained references

1

We've already thought of a number of scenarios in which they'd prove useful.

Relayer calls are currently a bit obscure in that it is not possible to `eth_call` them and get a sense of the result. While `multicall` does return all of the...

This seems to be the only function that doesn't use them.

Some deployments, like the batch relayers, deploy more than one contract from the same build info. We should fetch their ABI. Similarly, factory deployments should extract the ABI of whatever...

We should have the deploy command also at least save action ids, but potentially extract artifacts as well. It's annoying to have to remember to do all of these.

This will highlight repeated ids and force the user to handle them.

Add GaugeAction tests

1

This module was added in https://github.com/balancer-labs/balancer-v2-monorepo/pull/1146 with no tests, we should write them before deployment.

Determine veBAL critical permissioned actions and appropriate timelocks.

3

Some actions can permanently cripple parts or the entirety of the veBAL system, so as an added safety measure we should have these permissioned actions have non-zero delays (see #588)....

Migrate to solc 0.8

6

At some point we'll want to do this. There's two big changes that I know of that will affect us: - enums will become 256 bits wide, as opposed to...

With the large number of new interconnected contracts (the entire LM architechture, subDAOs, etc.), it'd be very useful to be able to reference these on-chain (we're currently passing a multitude...