soyboy
soyboy
This is being tracked an internal issue
This is now addressed in the node tutorial section
Yup good call. However I'm in favor of keeping it the OP Stack section because the contracts will be common across OP Stack forks. Where the "Contract Addresses" are specific...
When this page is updated we should also add the following notes: - We recommend against using the `L2ToL1MessagePasser` directly. Otherwise those that do have their finalized withdrawals being one-shot...
Updated here with the all the L1 and L2 contract details. Also added a comprehensive changelog over the L1 release versions: https://docs.optimism.io/stack/smart-contracts The contract addresses will go into Superchain Registry...
Already added to this page: https://docs.optimism.io/stack/smart-contracts#protocolversions
Another report of this tutorial being broken: https://github.com/ethereum-optimism/developers/discussions/351 Additional context: https://github.com/ethereum-optimism/developers/discussions/17#discussioncomment-9145846
closing in favor of https://github.com/ethereum-optimism/docs/issues/917
This information is included on this page: https://docs.optimism.io/builders/node-operators/network-upgrades#canyon
https://github.com/ethereum-optimism/docs/pull/447 addresses the ingress traffic and general architecture