Ben Jones

A note on this: since so many crypto transactions contain a large number of hashes/addresses/etc. which are "random" and hard to compress, I think a prepopulated dictionary could afford really...

I believe that this could actually be done in both directions, i.e. make the change to the `OVM_L1CrossDomainMessenger` as well. In the L1 case, another field could be added to...

Actually utilizing/enforcing the L2->L1 gas would be a pre-requisite for using the `XDomainMessageStatus` laid out above in the `OVM_L1CrossDomainMessenger` as well.

I have a plan in motion to collect this and other feature requests for the bridge so that we can get a proper community-driven implementation, stay tuned :) I have...

I think that this is a very interesting mechanism and is worth strongly considering. After mulling it over a bit, I think there could even be a further improvement: it...

@tynes FYI there is a good chance #254 requires new genesis for Kovan anyway; maybe we will have more luck verifying the newer contract.

basically we need to either: 1. replicate [this](https://github.com/ethereum-optimism/solidity/blob/416121951c95b2af1120f39a0c89fe1479deeca4/libsolidity/interface/CompilerStack.cpp#L1028-L1052) logic for deployedbytecode, but get it to work 2. upgrade to a version of solidity where we don't have to do the...

I can look into doing this! @smartcontracts do you know if this requires changes to our solidity plugin? Intuitively it seems like the command changing for the native build would...

This is awesome, thanks!!! Would you be able to make this PR against `feat/0.6/silence-errors` instead of `develop-0.6`? I think we wanna keep errors on for the default branches. :)