Mark Tyneway
Mark Tyneway
There is a desire to make the max bytecode size configurable by the chain operator. This would allow chains in increase or decrease their max bytecode size by calling the...
**Description** We need a clear explanation about why specs and how to think about them. Opening this PR for feedback.
### Component Forge ### Describe the feature you would like There are times when it is desired to set a specific named storage slot. The solidity compiler `storageLayout` contains each...
**Description** WIP Standard L2 Genesis
We still have codepaths to generate an L1 chainspec that configures clique. The clique engine is no longer maintained as part of `go-ethereum`, we should remove support for it. Once...
# Overview The Standard L2 Genesis aims to solve contract versioning and upgrades for predeploys. The main idea is that the network specific chain configuration should be moved to a...
One major benefit of the OP Stack is that it is minimally different from Ethereum. This means that users, developers and infrastructure providers have less chain specific gotchas and more...
The JSON response from the RPC `getnames` has gotten too large and will no longer return. This is a problem because there are currently applications that exist that are using...
We sometimes need to make quick releases of `op-geth` because a new chain was added to the `superchain-registry`. This can be unsafe and create weird dependencies across different teams. We...
All of our contracts implement `ISemver` so that we can know which versions are being used. Right now `RISCV.sol` doesn't implement this. The fact that it was [vendored](https://github.com/ethereum-optimism/optimism/blob/90435d076bdc9a7f4cee6ade0fa86afb9dc2609d/packages/contracts-bedrock/src/vendor/asterisc/RISCV.sol) into the...