OP Stack

How are we supposed to build on top of Optimism when they use fixed pragma Solidity versions in their contract?
Such a pain to deal with...

How are we supposed to build on top of Optimism when they use fixed pragma Solidity versions in their contract?
Such a pain to deal with...
https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/L1/L1CrossDomainMessenger.sol

Smart Contract Engineer at M0
pierrickgt.twitter
https://pierrick.turelier.com

Hmmm this is an interesting point. I believe the motivation was that everything is being tested with that specific compiler version and can't fully guarantee correctness with future compiler versions. Interfaces are already pragma ^ but... 1/2

Pragmatism (Security) at OP Labs.
Prev: ConsenSys & Coinbase.

Attribs: Friendly, curious, introverted, mid-witted.
Chans: /eth-security /maurelian /stoicism




... now that the OP Stack is really meant to be extended, I can see the argument for a principled approach to having pragma ^ on implementations too.

cc @maurelian.eth

Yeah, makes a lot of sense. 

What happens in 'forge build' if we let them float ? Does the compiler version change when we update foundry?

likes building things • https://alexgrover.me

We have deps with various versions, everything breaks when I do that.

you can pin the version used by forge in your foundry.toml:

`solc-version = "0.8.15"`

Nah the implementations should be pinned to a specific version, people building on top should use interfaces with relaxed versioning

Otherwise compilation will be non-deterministic depending on the latest solc release