Profile of trianglesphere in Optimism

Posts by trianglesphere

• [Draft] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 30, 2023, 9:16 p.m.
  Content: @WildfireDAO because these changes do not touch the deposits or withdrawals codepaths and touch no L 1 smart contracts (and one particular L 2 contract, but very minimal and unrelated to withdrawals), we feel that these changes do not need an audit. The OP Labs audit framework is described in more detail here: OP Labs Audit Framework: When to get external security review and how to prepare for it 4 .
  Likes: 2 Replies: 0
  Likers: fractalvisions, wildfiredao
  No replies yet.
• [FINAL] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 30, 2023, 9:16 p.m.
  Content: @WildfireDAO because these changes do not touch the deposits or withdrawals codepaths and touch no L 1 smart contracts (and one particular L 2 contract, but very minimal and unrelated to withdrawals), we feel that these changes do not need an audit. The OP Labs audit framework is described in more detail here: OP Labs Audit Framework: When to get external security review and how to prepare for it 4 .
  Likes: 2 Replies: 0
  Likers: fractalvisions, wildfiredao
  No replies yet.
• [Draft] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 30, 2023, 4:16 p.m.
  Content: @WildfireDAO because these changes do not touch the deposits or withdrawals codepaths and touch no L 1 smart contracts (and one particular L 2 contract, but very minimal and unrelated to withdrawals), we feel that these changes do not need an audit. The OP Labs audit framework is described in more detail here: OP Labs Audit Framework: When to get external security review and how to prepare for it 4 .
  Likes: 2 Replies: 0
  Likers: FractalVisions, WildfireDAO
  No replies yet.
• [FINAL] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 30, 2023, 4:16 p.m.
  Content: @WildfireDAO because these changes do not touch the deposits or withdrawals codepaths and touch no L 1 smart contracts (and one particular L 2 contract, but very minimal and unrelated to withdrawals), we feel that these changes do not need an audit. The OP Labs audit framework is described in more detail here: OP Labs Audit Framework: When to get external security review and how to prepare for it 4 .
  Likes: 2 Replies: 0
  Likers: FractalVisions, WildfireDAO
  No replies yet.
• [Draft] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 30, 2023, 4:16 p.m.
  Content: @WildfireDAO because these changes do not touch the deposits or withdrawals codepaths and touch no L 1 smart contracts (and one particular L 2 contract, but very minimal and unrelated to withdrawals), we feel that these changes do not need an audit. The OP Labs audit framework is described in more detail here: OP Labs Audit Framework: When to get external security review and how to prepare for it.
  Likes: 2 Replies: 0
  Likers: FractalVisions, WildfireDAO
  No replies yet.
• [FINAL] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 30, 2023, 4:16 p.m.
  Content: @WildfireDAO because these changes do not touch the deposits or withdrawals codepaths and touch no L 1 smart contracts (and one particular L 2 contract, but very minimal and unrelated to withdrawals), we feel that these changes do not need an audit. The OP Labs audit framework is described in more detail here: OP Labs Audit Framework: When to get external security review and how to prepare for it.
  Likes: 2 Replies: 0
  Likers: FractalVisions, WildfireDAO
  No replies yet.
• [Draft] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 14, 2023, 5:13 p.m.
  Content: Executive Summary Hi I’m Joshua, an engineer at OP Labs. OP Labs is a software development company focused on the Optimism ecosystem, and a core developer of the OP Stack. We provide some services to, but do not represent or speak on behalf of, the Optimism Foundation. Upgrade # 2 , Canyon is the first proposed network upgrade after Bedrock. Canyon contains the Shapella network upgrade from Ethereum, a change to reduce the volatility of the basefee, and several minor bug fixes. The Canyon upgrade will maintain EVM equivalence & improve the ergonomics of using the OP Stack for developers and end users. In addition, node operators will need to upgrade their nodes to stay in sync. Canyon brings the OP Stack protocol version to v 4 . 0 . 0 . If this vote passes, Canyon will activate on op-mainnet, base-mainnet, pgn-mainnet, & zora-mainnet on Thu Jan 11 17 : 00 : 01 UTC 2024 (Unix Time 1704992401 ) barring a critical security issue. All op-node versions after v 1 . 3 . 1 & all op-geth versions after v 1 . 101304 . 1 are compatible with Canyon. We will release a new version of op-node & op-geth with the Canyon activation time baked in if the vote passes governance. Specifications Technical Specification We are activating the following features as part of the Canyon upgrade. Full Canyon Specification 17 in Github. Shapella EIP- 3651 : Warm COINBASE 12 EIP- 3855 : PUSH 0 instruction 8 EIP- 3860 : Limit and meter initcode 2 EIP- 4895 : Beacon chain push withdrawals as operations 3 EIP- 6049 : Deprecate SELFDESTRUCT 5 Prohibit withdrawals in OP Stack blocks P 2 P Spec 3 Block Building Spec 4 EIP- 1559 Parameter Changes Increasing EIP- 1559 Denominator from 50 to 250 Specification 13 Adjust Channel Ordering The first ready channel is now read rather than the first channel when it is ready Specification 3 Receipt Hash Change The deposit nonce is included in the deposit receipt hash Specification 8 create 2 Deployer We are deploying standardized bytecode to 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 Specification 6 Security Considerations Consistent with the OP Labs Audit Framework 11 , OP Labs did not have the contents of Canyon audited; however OP Labs did perform a security review of these changes. The Shapella L 1 upgrade consists of relatively standard EVM changes & the addition of beacon chain withdrawals. OP Labs considers the EVM changes low risk because they have been active on L 1 without issue. Withdrawals are a new L 1 codepath to create arbitrary mints in the EVM. OP Labs has ensured that this type of transaction cannot occur on L 2 … The next set of changes, EIP- 1559 config change, the channel ordering change, and the receipt hash change also are low risk changes. They do not modify any code path which is responsible for securing user funds and have been tested. The last change, the create 2 Deployer, presents a larger user facing change. Canyon unconditionally modifies the bytecode of the 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 address. This address already has the create 2 Deployer on it on some, but not all, networks. OP Labs has validated that the contract code deployed by Canyon matches the public ABI of the existing contract. This upgrade does remove portions of the admin ABI (pausing, ownable), but OP Labs has confirmed that the contract author is ok with removing the Ownable & Pausable functionality. A typical developer would not be able to call these functions. Impact Summary OP Labs does not anticipate any down time due to this upgrade. This network upgrade does not contain backwards incompatible changes for end users. Shapella is important to retain compatibility with Ethereum. One change to be aware of is the deprecation warning of the SELFDESTRUCT opcode. The behavior of the opcode is not changing in Canyon, but is expected to change in a future network upgrade. Ethereum is expected to implement EIP- 6780 2 in the Dencun network upgrade to modify this opcode, and the Optimism community should expect to follow this change in the spirit of EVM equivalence. The EIP- 1559 Denominator will be changing from 50 to 250 . OP Labs is proposing this change to decrease volatility in the basefee on the OP Stack. By increasing the denominator, the amount the basefee increases is reduced when the gas used is over the gas target. A denominator of 50 was initially chosen for Bedrock such that the basefee on the OP Stack would decrease at approximately a rate of - 12 % per 12 s when the block were completely empty. This matches the decrease of Ethereum’s basefee. The rate of increase with completely full blocks was 77 % over 12 s because the gas limit on the OP Stack is 6 x the gas target. Since Bedrock, 2 minutes of full congestion ( 30 m gas blocks) on the OP Stack would result in an increased base fee of **** 304 x ****( 1 . 1 ^ 60 ) ******vs 2 minutes of full congestion on L 1 Ethereum would result in an increased base fee of 3 . 24 x ( 1 . 125 ^ 10 ). OP Labs is suggesting a denominator of 250 to match the rate of increase of Ethereum when OP Stack blocks are completely full. This will also reduce how quickly the basefee decays when blocks are empty and will enable users to have their transactions included more easily during periods of high usage. Canyon modifies the protocol to handle unclosed channels. Previously, only a single channel could be active at a time and if the channel was not closed, it would need to time out before progress could resume. Following the upgrade, the op-node will read the first channel that is ready. A new field will be added to the deposit transaction receipt encoding. It modifies the encoding to fix a bug where the deposit transaction nonce was not in consensus encoding. Finally, Canyon sets the create 2 Deployer bytecode at 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 on all OP networks. This enables developers to have access to this commonly used contract on all OP networks, not just OP Mainnet. This also particularly helps users on Base mainnet, where, due to a deployment issue, the create 2 Deployer is not able to be deployed to this address. Block explorers may have to re-verify the create 2 Deployer contract. Action Plan If this vote passes, the Canyon upgrade will be schedule for execution 5 ****weeks after the vote passes, on Thu Jan 11 17 : 00 : 01 UTC 2024 . The upgrade will occur automatically for nodes on a release which contains the baked in activation time. Canyon is code complete in the optimism monorepo at commit 6 cce 3728 b 7 bed 5 e 36234 aeba 3 b 773 e 0 f 97867 be 3 and op-geth at commit ed 8 e 9 f 54 ed 0 a 5069 e 77 ea 34895 ff 12 a 9 ac 4 ca 17 f. The op-node release v 1 . 3 . 1 and op-geth release v 1 . 101304 . 1 contain these changes. These commits do not contain the Canyon timestamp for mainnet. These releases could be used on mainnet by using the --override.canyon flag. OP Labs will release a future version of op-node & op-geth with the Canyon time configured if governance approves this upgrade. This upgrade has already been activated on internal devnets in coordination with Base & Conduit. It successfully activated on op-goerli, op-sepolia, base-goerli, base-sepolia, pgn-sepolia, & zora-sepolia on November 14 at 17 : 00 : 00 UTC. If there is a critical security issue, node operators will be able to disable the upgrade by using the —override.canyon flag on both op-node & op-geth. OP Labs will also collaborate with the community to extensively communicate that the upgrade is no longer happening. OP Labs will release a new version of op-node & op-geth with the Canyon activation date baked in and publicize to node operators & end users that the Canyon upgrade will be occurring. Conclusion This proposal outlines the Optimism Collective’s first network upgrade after Bedrock titled Canyon. This network upgrade maintains EVM equivalence via activating the Shapella network upgrade and includes several OP Stack specific improvements. We expect that this upgrade will not result in any down time and will occur at Thu Jan 11 17 : 00 : 01 UTC 2024 .
  Likes: 18 Replies: 1
  Likers: bobby, lavande, chain_l, pumbi, xlans, omarsin, moneymandoug, pgov, brichis, polynya, shun_daoasia, butterbum, kelvin, fractalvisions, merir, sete, tane, criptomommy
  Replies:

  • ksett: trianglesphere: ny down time due to this upgrade. This network upgrade does not contain backwards incompatible changes for end users. Shapella is important to retain compatibility with Ethereum. One change to be aware of is the deprecation warning of the SELFDESTRUCT opcode. The behavior of the opcode is not changing in Canyon, but is expected to change in a future network upgrade. Ethereum is expected to implement EIP-6780 in the Dencun network upgrade to modify this opcode, and the Optimism community should expect to follow this change in the spirit of EVM equivalence. The EIP-1559 Denominator will be changing from 50 to 250. OP Labs is proposing this change to decrease volatility in the basefee on the OP Stack. By increasing the denominator, the amount the basefee increases is reduced when the gas used is over the gas target. A denominator of 50 was initially chosen for Bedrock such that the basefee on the OP Stack would decrease at approximately a rate of -12% per 12s when the block were completely empty. This matches the decrease of Ethereum’s basefee. The rate of increase with completely full blocks was 77% over 12s because the gas limit on the OP Stack is 6x the gas target. Since Bedrock, 2 minutes of full congestion (30m gas blocks) on the OP Stack would result in an increased base fee of ****304x ****(1.1^60) ******vs 2 minutes of full congestion on L1 Ethereum would result in an increased base fee of 3.24x (1.125^10). OP Labs is suggesting a denominator of 250 to match the rate of increase of Ethereum when OP Stack blocks are completely full. This will also reduce how quickly the basefee decays when blocks are empty and will enable users to have their transactions included more easily during periods of high usage. Canyon modifies the protocol to handle unclosed channels. Previously, only a single channel could be active at a time and if the channel was not closed, it would need to time out before progress could resume. Following the upgrade, the op-node will read the first channel that is ready. A new field will be added to the deposit transaction receipt encoding. It modifies the encoding to fix a bug where the deposit transaction nonce was not in consensus encoding. Finally, Canyon sets the create2Deployer bytecode at 0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2 on all OP networks. This enables developers to have access to this commonly used contract on all OP networks, not just OP Mainnet. This also particularly helps users on Base mainnet, where, due to a deployment issue, the create2Deployer is not able to be deployed to this address. Block explorers may have to re-verify the create2Deployer contract. Action Plan If this vote passes, the Canyon upgrade will be schedule for execution 5 ****weeks after the vote passes, on Thu Jan 11 17:00:01 UTC 2024. The upgrade will occur automatically for nodes on a release which contains the baked in activation time. Canyon is code complete in the optimism monorepo at commit 6cce3728b7bed5e36234aeba3b773e0f97867be3 and op-geth at commit ed8e9f54ed0a5069e77ea34895ff12a9ac4ca17f. The op-node release v1.3.1 and op-geth release v1.101304.1 contain these changes. These commits do not contain the Canyon timestamp for mainnet. These releases could be used on mainnet by using the --override.canyon flag. OP Labs will release a future version of op-node & op-geth with the Canyon time configured if governance approves this upgrade. This upgrade has already been activated on internal devnets in coordination with Base & Conduit. It successfully activated on op-goerli, op-sepolia, base-goerli, base-sepolia, pgn-sepolia, & zora-sepolia on November 14 at 17:00:00 UTC. If there is a critical security issue, node operators will be able to disable the upgrade by using the —override.canyon flag on both op-node & op-geth. OP Labs will also collaborate with the community to extensively communicate that the upgrade is no longer happening. OP Labs will release a new version of op-node & op-geth with the Canyon activation date baked in and publicize to node operators & end users that the Canyon upgrade will be occurring. Hey @trianglesphere we are thrilled at the additional level of scalability brought about by the Canyon Network Upgrade! The Lyra Chain has recently been deployed ahead of the V2 launch of the Lyra Protocol. Is it possible to include Lyra Chain in this proposal and the scheduled upgrades? mirror.xyz Lyra Chain: Harder, Better, Faster, Stronger We know Lyra V2 is coming. We know it’s made for pro traders. And we know it’s the most scalable derivatives protocol yet. But how did we build it all onchain? It’s time to find out how we leveraged the OP Stack to build Lyra Chain and make us
• [FINAL] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 14, 2023, 5:13 p.m.
  Content: Executive Summary Hi I’m Joshua, an engineer at OP Labs. OP Labs is a software development company focused on the Optimism ecosystem, and a core developer of the OP Stack. We provide some services to, but do not represent or speak on behalf of, the Optimism Foundation. Upgrade # 2 , Canyon is the first proposed network upgrade after Bedrock. Canyon contains the Shapella network upgrade from Ethereum, a change to reduce the volatility of the basefee, and several minor bug fixes. The Canyon upgrade will maintain EVM equivalence & improve the ergonomics of using the OP Stack for developers and end users. In addition, node operators will need to upgrade their nodes to stay in sync. Canyon brings the OP Stack protocol version to v 4 . 0 . 0 . If this vote passes, Canyon will activate on op-mainnet, base-mainnet, pgn-mainnet, & zora-mainnet on Thu Jan 11 17 : 00 : 01 UTC 2024 (Unix Time 1704992401 ) barring a critical security issue. All op-node versions after v 1 . 3 . 1 & all op-geth versions after v 1 . 101304 . 1 are compatible with Canyon. We will release a new version of op-node & op-geth with the Canyon activation time baked in if the vote passes governance. Specifications Technical Specification We are activating the following features as part of the Canyon upgrade. Full Canyon Specification 17 in Github. Shapella EIP- 3651 : Warm COINBASE 12 EIP- 3855 : PUSH 0 instruction 8 EIP- 3860 : Limit and meter initcode 2 EIP- 4895 : Beacon chain push withdrawals as operations 3 EIP- 6049 : Deprecate SELFDESTRUCT 5 Prohibit withdrawals in OP Stack blocks P 2 P Spec 3 Block Building Spec 4 EIP- 1559 Parameter Changes Increasing EIP- 1559 Denominator from 50 to 250 Specification 13 Adjust Channel Ordering The first ready channel is now read rather than the first channel when it is ready Specification 3 Receipt Hash Change The deposit nonce is included in the deposit receipt hash Specification 8 create 2 Deployer We are deploying standardized bytecode to 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 Specification 6 Security Considerations Consistent with the OP Labs Audit Framework 11 , OP Labs did not have the contents of Canyon audited; however OP Labs did perform a security review of these changes. The Shapella L 1 upgrade consists of relatively standard EVM changes & the addition of beacon chain withdrawals. OP Labs considers the EVM changes low risk because they have been active on L 1 without issue. Withdrawals are a new L 1 codepath to create arbitrary mints in the EVM. OP Labs has ensured that this type of transaction cannot occur on L 2 … The next set of changes, EIP- 1559 config change, the channel ordering change, and the receipt hash change also are low risk changes. They do not modify any code path which is responsible for securing user funds and have been tested. The last change, the create 2 Deployer, presents a larger user facing change. Canyon unconditionally modifies the bytecode of the 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 address. This address already has the create 2 Deployer on it on some, but not all, networks. OP Labs has validated that the contract code deployed by Canyon matches the public ABI of the existing contract. This upgrade does remove portions of the admin ABI (pausing, ownable), but OP Labs has confirmed that the contract author is ok with removing the Ownable & Pausable functionality. A typical developer would not be able to call these functions. Impact Summary OP Labs does not anticipate any down time due to this upgrade. This network upgrade does not contain backwards incompatible changes for end users. Shapella is important to retain compatibility with Ethereum. One change to be aware of is the deprecation warning of the SELFDESTRUCT opcode. The behavior of the opcode is not changing in Canyon, but is expected to change in a future network upgrade. Ethereum is expected to implement EIP- 6780 2 in the Dencun network upgrade to modify this opcode, and the Optimism community should expect to follow this change in the spirit of EVM equivalence. The EIP- 1559 Denominator will be changing from 50 to 250 . OP Labs is proposing this change to decrease volatility in the basefee on the OP Stack. By increasing the denominator, the amount the basefee increases is reduced when the gas used is over the gas target. A denominator of 50 was initially chosen for Bedrock such that the basefee on the OP Stack would decrease at approximately a rate of - 12 % per 12 s when the block were completely empty. This matches the decrease of Ethereum’s basefee. The rate of increase with completely full blocks was 77 % over 12 s because the gas limit on the OP Stack is 6 x the gas target. Since Bedrock, 2 minutes of full congestion ( 30 m gas blocks) on the OP Stack would result in an increased base fee of **** 304 x ****( 1 . 1 ^ 60 ) ******vs 2 minutes of full congestion on L 1 Ethereum would result in an increased base fee of 3 . 24 x ( 1 . 125 ^ 10 ). OP Labs is suggesting a denominator of 250 to match the rate of increase of Ethereum when OP Stack blocks are completely full. This will also reduce how quickly the basefee decays when blocks are empty and will enable users to have their transactions included more easily during periods of high usage. Canyon modifies the protocol to handle unclosed channels. Previously, only a single channel could be active at a time and if the channel was not closed, it would need to time out before progress could resume. Following the upgrade, the op-node will read the first channel that is ready. A new field will be added to the deposit transaction receipt encoding. It modifies the encoding to fix a bug where the deposit transaction nonce was not in consensus encoding. Finally, Canyon sets the create 2 Deployer bytecode at 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 on all OP networks. This enables developers to have access to this commonly used contract on all OP networks, not just OP Mainnet. This also particularly helps users on Base mainnet, where, due to a deployment issue, the create 2 Deployer is not able to be deployed to this address. Block explorers may have to re-verify the create 2 Deployer contract. Action Plan If this vote passes, the Canyon upgrade will be schedule for execution 5 ****weeks after the vote passes, on Thu Jan 11 17 : 00 : 01 UTC 2024 . The upgrade will occur automatically for nodes on a release which contains the baked in activation time. Canyon is code complete in the optimism monorepo at commit 6 cce 3728 b 7 bed 5 e 36234 aeba 3 b 773 e 0 f 97867 be 3 and op-geth at commit ed 8 e 9 f 54 ed 0 a 5069 e 77 ea 34895 ff 12 a 9 ac 4 ca 17 f. The op-node release v 1 . 3 . 1 and op-geth release v 1 . 101304 . 1 contain these changes. These commits do not contain the Canyon timestamp for mainnet. These releases could be used on mainnet by using the --override.canyon flag. OP Labs will release a future version of op-node & op-geth with the Canyon time configured if governance approves this upgrade. This upgrade has already been activated on internal devnets in coordination with Base & Conduit. It successfully activated on op-goerli, op-sepolia, base-goerli, base-sepolia, pgn-sepolia, & zora-sepolia on November 14 at 17 : 00 : 00 UTC. If there is a critical security issue, node operators will be able to disable the upgrade by using the —override.canyon flag on both op-node & op-geth. OP Labs will also collaborate with the community to extensively communicate that the upgrade is no longer happening. OP Labs will release a new version of op-node & op-geth with the Canyon activation date baked in and publicize to node operators & end users that the Canyon upgrade will be occurring. Conclusion This proposal outlines the Optimism Collective’s first network upgrade after Bedrock titled Canyon. This network upgrade maintains EVM equivalence via activating the Shapella network upgrade and includes several OP Stack specific improvements. We expect that this upgrade will not result in any down time and will occur at Thu Jan 11 17 : 00 : 01 UTC 2024 .
  Likes: 18 Replies: 1
  Likers: bobby, lavande, chain_l, pumbi, xlans, omarsin, moneymandoug, pgov, brichis, polynya, shun_daoasia, butterbum, kelvin, fractalvisions, merir, sete, tane, criptomommy
  Replies:

  • ksett: trianglesphere: ny down time due to this upgrade. This network upgrade does not contain backwards incompatible changes for end users. Shapella is important to retain compatibility with Ethereum. One change to be aware of is the deprecation warning of the SELFDESTRUCT opcode. The behavior of the opcode is not changing in Canyon, but is expected to change in a future network upgrade. Ethereum is expected to implement EIP-6780 in the Dencun network upgrade to modify this opcode, and the Optimism community should expect to follow this change in the spirit of EVM equivalence. The EIP-1559 Denominator will be changing from 50 to 250. OP Labs is proposing this change to decrease volatility in the basefee on the OP Stack. By increasing the denominator, the amount the basefee increases is reduced when the gas used is over the gas target. A denominator of 50 was initially chosen for Bedrock such that the basefee on the OP Stack would decrease at approximately a rate of -12% per 12s when the block were completely empty. This matches the decrease of Ethereum’s basefee. The rate of increase with completely full blocks was 77% over 12s because the gas limit on the OP Stack is 6x the gas target. Since Bedrock, 2 minutes of full congestion (30m gas blocks) on the OP Stack would result in an increased base fee of ****304x ****(1.1^60) ******vs 2 minutes of full congestion on L1 Ethereum would result in an increased base fee of 3.24x (1.125^10). OP Labs is suggesting a denominator of 250 to match the rate of increase of Ethereum when OP Stack blocks are completely full. This will also reduce how quickly the basefee decays when blocks are empty and will enable users to have their transactions included more easily during periods of high usage. Canyon modifies the protocol to handle unclosed channels. Previously, only a single channel could be active at a time and if the channel was not closed, it would need to time out before progress could resume. Following the upgrade, the op-node will read the first channel that is ready. A new field will be added to the deposit transaction receipt encoding. It modifies the encoding to fix a bug where the deposit transaction nonce was not in consensus encoding. Finally, Canyon sets the create2Deployer bytecode at 0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2 on all OP networks. This enables developers to have access to this commonly used contract on all OP networks, not just OP Mainnet. This also particularly helps users on Base mainnet, where, due to a deployment issue, the create2Deployer is not able to be deployed to this address. Block explorers may have to re-verify the create2Deployer contract. Action Plan If this vote passes, the Canyon upgrade will be schedule for execution 5 ****weeks after the vote passes, on Thu Jan 11 17:00:01 UTC 2024. The upgrade will occur automatically for nodes on a release which contains the baked in activation time. Canyon is code complete in the optimism monorepo at commit 6cce3728b7bed5e36234aeba3b773e0f97867be3 and op-geth at commit ed8e9f54ed0a5069e77ea34895ff12a9ac4ca17f. The op-node release v1.3.1 and op-geth release v1.101304.1 contain these changes. These commits do not contain the Canyon timestamp for mainnet. These releases could be used on mainnet by using the --override.canyon flag. OP Labs will release a future version of op-node & op-geth with the Canyon time configured if governance approves this upgrade. This upgrade has already been activated on internal devnets in coordination with Base & Conduit. It successfully activated on op-goerli, op-sepolia, base-goerli, base-sepolia, pgn-sepolia, & zora-sepolia on November 14 at 17:00:00 UTC. If there is a critical security issue, node operators will be able to disable the upgrade by using the —override.canyon flag on both op-node & op-geth. OP Labs will also collaborate with the community to extensively communicate that the upgrade is no longer happening. OP Labs will release a new version of op-node & op-geth with the Canyon activation date baked in and publicize to node operators & end users that the Canyon upgrade will be occurring. Hey @trianglesphere we are thrilled at the additional level of scalability brought about by the Canyon Network Upgrade! The Lyra Chain has recently been deployed ahead of the V2 launch of the Lyra Protocol. Is it possible to include Lyra Chain in this proposal and the scheduled upgrades? mirror.xyz Lyra Chain: Harder, Better, Faster, Stronger We know Lyra V2 is coming. We know it’s made for pro traders. And we know it’s the most scalable derivatives protocol yet. But how did we build it all onchain? It’s time to find out how we leveraged the OP Stack to build Lyra Chain and make us
• [Draft] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 14, 2023, 12:13 p.m.
  Content: Executive Summary Hi I’m Joshua, an engineer at OP Labs. OP Labs is a software development company focused on the Optimism ecosystem, and a core developer of the OP Stack. We provide some services to, but do not represent or speak on behalf of, the Optimism Foundation. Upgrade # 2 , Canyon is the first proposed network upgrade after Bedrock. Canyon contains the Shapella network upgrade from Ethereum, a change to reduce the volatility of the basefee, and several minor bug fixes. The Canyon upgrade will maintain EVM equivalence & improve the ergonomics of using the OP Stack for developers and end users. In addition, node operators will need to upgrade their nodes to stay in sync. Canyon brings the OP Stack protocol version to v 4 . 0 . 0 . If this vote passes, Canyon will activate on op-mainnet, base-mainnet, pgn-mainnet, & zora-mainnet on Thu Jan 11 17 : 00 : 01 UTC 2024 (Unix Time 1704992401 ) barring a critical security issue. All op-node versions after v 1 . 3 . 1 & all op-geth versions after v 1 . 101304 . 1 are compatible with Canyon. We will release a new version of op-node & op-geth with the Canyon activation time baked in if the vote passes governance. Specifications Technical Specification We are activating the following features as part of the Canyon upgrade. Full Canyon Specification 22 in Github. Shapella EIP- 3651 : Warm COINBASE 16 EIP- 3855 : PUSH 0 instruction 9 EIP- 3860 : Limit and meter initcode 3 EIP- 4895 : Beacon chain push withdrawals as operations 6 EIP- 6049 : Deprecate SELFDESTRUCT 6 Prohibit withdrawals in OP Stack blocks P 2 P Spec 4 Block Building Spec 4 EIP- 1559 Parameter Changes Increasing EIP- 1559 Denominator from 50 to 250 Specification 14 Adjust Channel Ordering The first ready channel is now read rather than the first channel when it is ready Specification 3 Receipt Hash Change The deposit nonce is included in the deposit receipt hash Specification 8 create 2 Deployer We are deploying standardized bytecode to 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 Specification 8 Security Considerations Consistent with the OP Labs Audit Framework 14 , OP Labs did not have the contents of Canyon audited; however OP Labs did perform a security review of these changes. The Shapella L 1 upgrade consists of relatively standard EVM changes & the addition of beacon chain withdrawals. OP Labs considers the EVM changes low risk because they have been active on L 1 without issue. Withdrawals are a new L 1 codepath to create arbitrary mints in the EVM. OP Labs has ensured that this type of transaction cannot occur on L 2 … The next set of changes, EIP- 1559 config change, the channel ordering change, and the receipt hash change also are low risk changes. They do not modify any code path which is responsible for securing user funds and have been tested. The last change, the create 2 Deployer, presents a larger user facing change. Canyon unconditionally modifies the bytecode of the 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 address. This address already has the create 2 Deployer on it on some, but not all, networks. OP Labs has validated that the contract code deployed by Canyon matches the public ABI of the existing contract. This upgrade does remove portions of the admin ABI (pausing, ownable), but OP Labs has confirmed that the contract author is ok with removing the Ownable & Pausable functionality. A typical developer would not be able to call these functions. Impact Summary OP Labs does not anticipate any down time due to this upgrade. This network upgrade does not contain backwards incompatible changes for end users. Shapella is important to retain compatibility with Ethereum. One change to be aware of is the deprecation warning of the SELFDESTRUCT opcode. The behavior of the opcode is not changing in Canyon, but is expected to change in a future network upgrade. Ethereum is expected to implement EIP- 6780 2 in the Dencun network upgrade to modify this opcode, and the Optimism community should expect to follow this change in the spirit of EVM equivalence. The EIP- 1559 Denominator will be changing from 50 to 250 . OP Labs is proposing this change to decrease volatility in the basefee on the OP Stack. By increasing the denominator, the amount the basefee increases is reduced when the gas used is over the gas target. A denominator of 50 was initially chosen for Bedrock such that the basefee on the OP Stack would decrease at approximately a rate of - 12 % per 12 s when the block were completely empty. This matches the decrease of Ethereum’s basefee. The rate of increase with completely full blocks was 77 % over 12 s because the gas limit on the OP Stack is 6 x the gas target. Since Bedrock, 2 minutes of full congestion ( 30 m gas blocks) on the OP Stack would result in an increased base fee of **** 304 x ****( 1 . 1 ^ 60 ) ******vs 2 minutes of full congestion on L 1 Ethereum would result in an increased base fee of 3 . 24 x ( 1 . 125 ^ 10 ). OP Labs is suggesting a denominator of 250 to match the rate of increase of Ethereum when OP Stack blocks are completely full. This will also reduce how quickly the basefee decays when blocks are empty and will enable users to have their transactions included more easily during periods of high usage. Canyon modifies the protocol to handle unclosed channels. Previously, only a single channel could be active at a time and if the channel was not closed, it would need to time out before progress could resume. Following the upgrade, the op-node will read the first channel that is ready. A new field will be added to the deposit transaction receipt encoding. It modifies the encoding to fix a bug where the deposit transaction nonce was not in consensus encoding. Finally, Canyon sets the create 2 Deployer bytecode at 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 on all OP networks. This enables developers to have access to this commonly used contract on all OP networks, not just OP Mainnet. This also particularly helps users on Base mainnet, where, due to a deployment issue, the create 2 Deployer is not able to be deployed to this address. Block explorers may have to re-verify the create 2 Deployer contract. Action Plan If this vote passes, the Canyon upgrade will be schedule for execution 5 ****weeks after the vote passes, on Thu Jan 11 17 : 00 : 01 UTC 2024 . The upgrade will occur automatically for nodes on a release which contains the baked in activation time. Canyon is code complete in the optimism monorepo at commit 6 cce 3728 b 7 bed 5 e 36234 aeba 3 b 773 e 0 f 97867 be 3 and op-geth at commit ed 8 e 9 f 54 ed 0 a 5069 e 77 ea 34895 ff 12 a 9 ac 4 ca 17 f. The op-node release v 1 . 3 . 1 and op-geth release v 1 . 101304 . 1 contain these changes. These commits do not contain the Canyon timestamp for mainnet. These releases could be used on mainnet by using the --override.canyon flag. OP Labs will release a future version of op-node & op-geth with the Canyon time configured if governance approves this upgrade. This upgrade has already been activated on internal devnets in coordination with Base & Conduit. It successfully activated on op-goerli, op-sepolia, base-goerli, base-sepolia, pgn-sepolia, & zora-sepolia on November 14 at 17 : 00 : 00 UTC. If there is a critical security issue, node operators will be able to disable the upgrade by using the —override.canyon flag on both op-node & op-geth. OP Labs will also collaborate with the community to extensively communicate that the upgrade is no longer happening. OP Labs will release a new version of op-node & op-geth with the Canyon activation date baked in and publicize to node operators & end users that the Canyon upgrade will be occurring. Conclusion This proposal outlines the Optimism Collective’s first network upgrade after Bedrock titled Canyon. This network upgrade maintains EVM equivalence via activating the Shapella network upgrade and includes several OP Stack specific improvements. We expect that this upgrade will not result in any down time and will occur at Thu Jan 11 17 : 00 : 01 UTC 2024 .
  Likes: 19 Replies: 1
  Likers: bobby, lavande, Chain_L, Pumbi, Xlans, Omarsin, MoneyManDoug, PGov, brichis, polynya, shun_DAOAsia, Luckyhooman.eth, kelvin, FractalVisions, MeriR, Sete, Tane, criptomommy, ethdev
  Replies:

  • ksett: trianglesphere: ny down time due to this upgrade. This network upgrade does not contain backwards incompatible changes for end users. Shapella is important to retain compatibility with Ethereum. One change to be aware of is the deprecation warning of the SELFDESTRUCT opcode. The behavior of the opcode is not changing in Canyon, but is expected to change in a future network upgrade. Ethereum is expected to implement EIP-6780 in the Dencun network upgrade to modify this opcode, and the Optimism community should expect to follow this change in the spirit of EVM equivalence. The EIP-1559 Denominator will be changing from 50 to 250. OP Labs is proposing this change to decrease volatility in the basefee on the OP Stack. By increasing the denominator, the amount the basefee increases is reduced when the gas used is over the gas target. A denominator of 50 was initially chosen for Bedrock such that the basefee on the OP Stack would decrease at approximately a rate of -12% per 12s when the block were completely empty. This matches the decrease of Ethereum’s basefee. The rate of increase with completely full blocks was 77% over 12s because the gas limit on the OP Stack is 6x the gas target. Since Bedrock, 2 minutes of full congestion (30m gas blocks) on the OP Stack would result in an increased base fee of ****304x ****(1.1^60) ******vs 2 minutes of full congestion on L1 Ethereum would result in an increased base fee of 3.24x (1.125^10). OP Labs is suggesting a denominator of 250 to match the rate of increase of Ethereum when OP Stack blocks are completely full. This will also reduce how quickly the basefee decays when blocks are empty and will enable users to have their transactions included more easily during periods of high usage. Canyon modifies the protocol to handle unclosed channels. Previously, only a single channel could be active at a time and if the channel was not closed, it would need to time out before progress could resume. Following the upgrade, the op-node will read the first channel that is ready. A new field will be added to the deposit transaction receipt encoding. It modifies the encoding to fix a bug where the deposit transaction nonce was not in consensus encoding. Finally, Canyon sets the create2Deployer bytecode at 0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2 on all OP networks. This enables developers to have access to this commonly used contract on all OP networks, not just OP Mainnet. This also particularly helps users on Base mainnet, where, due to a deployment issue, the create2Deployer is not able to be deployed to this address. Block explorers may have to re-verify the create2Deployer contract. Action Plan If this vote passes, the Canyon upgrade will be schedule for execution 5 ****weeks after the vote passes, on Thu Jan 11 17:00:01 UTC 2024. The upgrade will occur automatically for nodes on a release which contains the baked in activation time. Canyon is code complete in the optimism monorepo at commit 6cce3728b7bed5e36234aeba3b773e0f97867be3 and op-geth at commit ed8e9f54ed0a5069e77ea34895ff12a9ac4ca17f. The op-node release v1.3.1 and op-geth release v1.101304.1 contain these changes. These commits do not contain the Canyon timestamp for mainnet. These releases could be used on mainnet by using the --override.canyon flag. OP Labs will release a future version of op-node & op-geth with the Canyon time configured if governance approves this upgrade. This upgrade has already been activated on internal devnets in coordination with Base & Conduit. It successfully activated on op-goerli, op-sepolia, base-goerli, base-sepolia, pgn-sepolia, & zora-sepolia on November 14 at 17:00:00 UTC. If there is a critical security issue, node operators will be able to disable the upgrade by using the —override.canyon flag on both op-node & op-geth. OP Labs will also collaborate with the community to extensively communicate that the upgrade is no longer happening. OP Labs will release a new version of op-node & op-geth with the Canyon activation date baked in and publicize to node operators & end users that the Canyon upgrade will be occurring. Hey @trianglesphere we are thrilled at the additional level of scalability brought about by the Canyon Network Upgrade! The Lyra Chain has recently been deployed ahead of the V2 launch of the Lyra Protocol. Is it possible to include Lyra Chain in this proposal and the scheduled upgrades? mirror.xyz Lyra Chain: Harder, Better, Faster, Stronger We know Lyra V2 is coming. We know it’s made for pro traders. And we know it’s the most scalable derivatives protocol yet. But how did we build it all onchain? It’s time to find out how we leveraged the OP Stack to build Lyra Chain and make us
• [FINAL] Upgrade Proposal #2: Canyon Network Upgrade by trianglesphere - No Role
  Posted on: Nov. 14, 2023, 12:13 p.m.
  Content: Executive Summary Hi I’m Joshua, an engineer at OP Labs. OP Labs is a software development company focused on the Optimism ecosystem, and a core developer of the OP Stack. We provide some services to, but do not represent or speak on behalf of, the Optimism Foundation. Upgrade # 2 , Canyon is the first proposed network upgrade after Bedrock. Canyon contains the Shapella network upgrade from Ethereum, a change to reduce the volatility of the basefee, and several minor bug fixes. The Canyon upgrade will maintain EVM equivalence & improve the ergonomics of using the OP Stack for developers and end users. In addition, node operators will need to upgrade their nodes to stay in sync. Canyon brings the OP Stack protocol version to v 4 . 0 . 0 . If this vote passes, Canyon will activate on op-mainnet, base-mainnet, pgn-mainnet, & zora-mainnet on Thu Jan 11 17 : 00 : 01 UTC 2024 (Unix Time 1704992401 ) barring a critical security issue. All op-node versions after v 1 . 3 . 1 & all op-geth versions after v 1 . 101304 . 1 are compatible with Canyon. We will release a new version of op-node & op-geth with the Canyon activation time baked in if the vote passes governance. Specifications Technical Specification We are activating the following features as part of the Canyon upgrade. Full Canyon Specification 22 in Github. Shapella EIP- 3651 : Warm COINBASE 16 EIP- 3855 : PUSH 0 instruction 9 EIP- 3860 : Limit and meter initcode 3 EIP- 4895 : Beacon chain push withdrawals as operations 6 EIP- 6049 : Deprecate SELFDESTRUCT 6 Prohibit withdrawals in OP Stack blocks P 2 P Spec 4 Block Building Spec 4 EIP- 1559 Parameter Changes Increasing EIP- 1559 Denominator from 50 to 250 Specification 14 Adjust Channel Ordering The first ready channel is now read rather than the first channel when it is ready Specification 3 Receipt Hash Change The deposit nonce is included in the deposit receipt hash Specification 8 create 2 Deployer We are deploying standardized bytecode to 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 Specification 8 Security Considerations Consistent with the OP Labs Audit Framework 14 , OP Labs did not have the contents of Canyon audited; however OP Labs did perform a security review of these changes. The Shapella L 1 upgrade consists of relatively standard EVM changes & the addition of beacon chain withdrawals. OP Labs considers the EVM changes low risk because they have been active on L 1 without issue. Withdrawals are a new L 1 codepath to create arbitrary mints in the EVM. OP Labs has ensured that this type of transaction cannot occur on L 2 … The next set of changes, EIP- 1559 config change, the channel ordering change, and the receipt hash change also are low risk changes. They do not modify any code path which is responsible for securing user funds and have been tested. The last change, the create 2 Deployer, presents a larger user facing change. Canyon unconditionally modifies the bytecode of the 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 address. This address already has the create 2 Deployer on it on some, but not all, networks. OP Labs has validated that the contract code deployed by Canyon matches the public ABI of the existing contract. This upgrade does remove portions of the admin ABI (pausing, ownable), but OP Labs has confirmed that the contract author is ok with removing the Ownable & Pausable functionality. A typical developer would not be able to call these functions. Impact Summary OP Labs does not anticipate any down time due to this upgrade. This network upgrade does not contain backwards incompatible changes for end users. Shapella is important to retain compatibility with Ethereum. One change to be aware of is the deprecation warning of the SELFDESTRUCT opcode. The behavior of the opcode is not changing in Canyon, but is expected to change in a future network upgrade. Ethereum is expected to implement EIP- 6780 2 in the Dencun network upgrade to modify this opcode, and the Optimism community should expect to follow this change in the spirit of EVM equivalence. The EIP- 1559 Denominator will be changing from 50 to 250 . OP Labs is proposing this change to decrease volatility in the basefee on the OP Stack. By increasing the denominator, the amount the basefee increases is reduced when the gas used is over the gas target. A denominator of 50 was initially chosen for Bedrock such that the basefee on the OP Stack would decrease at approximately a rate of - 12 % per 12 s when the block were completely empty. This matches the decrease of Ethereum’s basefee. The rate of increase with completely full blocks was 77 % over 12 s because the gas limit on the OP Stack is 6 x the gas target. Since Bedrock, 2 minutes of full congestion ( 30 m gas blocks) on the OP Stack would result in an increased base fee of **** 304 x ****( 1 . 1 ^ 60 ) ******vs 2 minutes of full congestion on L 1 Ethereum would result in an increased base fee of 3 . 24 x ( 1 . 125 ^ 10 ). OP Labs is suggesting a denominator of 250 to match the rate of increase of Ethereum when OP Stack blocks are completely full. This will also reduce how quickly the basefee decays when blocks are empty and will enable users to have their transactions included more easily during periods of high usage. Canyon modifies the protocol to handle unclosed channels. Previously, only a single channel could be active at a time and if the channel was not closed, it would need to time out before progress could resume. Following the upgrade, the op-node will read the first channel that is ready. A new field will be added to the deposit transaction receipt encoding. It modifies the encoding to fix a bug where the deposit transaction nonce was not in consensus encoding. Finally, Canyon sets the create 2 Deployer bytecode at 0 x 13 b 0 D 85 CcB 8 bf 860 b 6 b 79 AF 3029 fCA 081 AE 9 beF 2 on all OP networks. This enables developers to have access to this commonly used contract on all OP networks, not just OP Mainnet. This also particularly helps users on Base mainnet, where, due to a deployment issue, the create 2 Deployer is not able to be deployed to this address. Block explorers may have to re-verify the create 2 Deployer contract. Action Plan If this vote passes, the Canyon upgrade will be schedule for execution 5 ****weeks after the vote passes, on Thu Jan 11 17 : 00 : 01 UTC 2024 . The upgrade will occur automatically for nodes on a release which contains the baked in activation time. Canyon is code complete in the optimism monorepo at commit 6 cce 3728 b 7 bed 5 e 36234 aeba 3 b 773 e 0 f 97867 be 3 and op-geth at commit ed 8 e 9 f 54 ed 0 a 5069 e 77 ea 34895 ff 12 a 9 ac 4 ca 17 f. The op-node release v 1 . 3 . 1 and op-geth release v 1 . 101304 . 1 contain these changes. These commits do not contain the Canyon timestamp for mainnet. These releases could be used on mainnet by using the --override.canyon flag. OP Labs will release a future version of op-node & op-geth with the Canyon time configured if governance approves this upgrade. This upgrade has already been activated on internal devnets in coordination with Base & Conduit. It successfully activated on op-goerli, op-sepolia, base-goerli, base-sepolia, pgn-sepolia, & zora-sepolia on November 14 at 17 : 00 : 00 UTC. If there is a critical security issue, node operators will be able to disable the upgrade by using the —override.canyon flag on both op-node & op-geth. OP Labs will also collaborate with the community to extensively communicate that the upgrade is no longer happening. OP Labs will release a new version of op-node & op-geth with the Canyon activation date baked in and publicize to node operators & end users that the Canyon upgrade will be occurring. Conclusion This proposal outlines the Optimism Collective’s first network upgrade after Bedrock titled Canyon. This network upgrade maintains EVM equivalence via activating the Shapella network upgrade and includes several OP Stack specific improvements. We expect that this upgrade will not result in any down time and will occur at Thu Jan 11 17 : 00 : 01 UTC 2024 .
  Likes: 19 Replies: 1
  Likers: bobby, lavande, Chain_L, Pumbi, Xlans, Omarsin, MoneyManDoug, PGov, brichis, polynya, shun_DAOAsia, Luckyhooman.eth, kelvin, FractalVisions, MeriR, Sete, Tane, criptomommy, ethdev
  Replies:

  • ksett: trianglesphere: ny down time due to this upgrade. This network upgrade does not contain backwards incompatible changes for end users. Shapella is important to retain compatibility with Ethereum. One change to be aware of is the deprecation warning of the SELFDESTRUCT opcode. The behavior of the opcode is not changing in Canyon, but is expected to change in a future network upgrade. Ethereum is expected to implement EIP-6780 in the Dencun network upgrade to modify this opcode, and the Optimism community should expect to follow this change in the spirit of EVM equivalence. The EIP-1559 Denominator will be changing from 50 to 250. OP Labs is proposing this change to decrease volatility in the basefee on the OP Stack. By increasing the denominator, the amount the basefee increases is reduced when the gas used is over the gas target. A denominator of 50 was initially chosen for Bedrock such that the basefee on the OP Stack would decrease at approximately a rate of -12% per 12s when the block were completely empty. This matches the decrease of Ethereum’s basefee. The rate of increase with completely full blocks was 77% over 12s because the gas limit on the OP Stack is 6x the gas target. Since Bedrock, 2 minutes of full congestion (30m gas blocks) on the OP Stack would result in an increased base fee of ****304x ****(1.1^60) ******vs 2 minutes of full congestion on L1 Ethereum would result in an increased base fee of 3.24x (1.125^10). OP Labs is suggesting a denominator of 250 to match the rate of increase of Ethereum when OP Stack blocks are completely full. This will also reduce how quickly the basefee decays when blocks are empty and will enable users to have their transactions included more easily during periods of high usage. Canyon modifies the protocol to handle unclosed channels. Previously, only a single channel could be active at a time and if the channel was not closed, it would need to time out before progress could resume. Following the upgrade, the op-node will read the first channel that is ready. A new field will be added to the deposit transaction receipt encoding. It modifies the encoding to fix a bug where the deposit transaction nonce was not in consensus encoding. Finally, Canyon sets the create2Deployer bytecode at 0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2 on all OP networks. This enables developers to have access to this commonly used contract on all OP networks, not just OP Mainnet. This also particularly helps users on Base mainnet, where, due to a deployment issue, the create2Deployer is not able to be deployed to this address. Block explorers may have to re-verify the create2Deployer contract. Action Plan If this vote passes, the Canyon upgrade will be schedule for execution 5 ****weeks after the vote passes, on Thu Jan 11 17:00:01 UTC 2024. The upgrade will occur automatically for nodes on a release which contains the baked in activation time. Canyon is code complete in the optimism monorepo at commit 6cce3728b7bed5e36234aeba3b773e0f97867be3 and op-geth at commit ed8e9f54ed0a5069e77ea34895ff12a9ac4ca17f. The op-node release v1.3.1 and op-geth release v1.101304.1 contain these changes. These commits do not contain the Canyon timestamp for mainnet. These releases could be used on mainnet by using the --override.canyon flag. OP Labs will release a future version of op-node & op-geth with the Canyon time configured if governance approves this upgrade. This upgrade has already been activated on internal devnets in coordination with Base & Conduit. It successfully activated on op-goerli, op-sepolia, base-goerli, base-sepolia, pgn-sepolia, & zora-sepolia on November 14 at 17:00:00 UTC. If there is a critical security issue, node operators will be able to disable the upgrade by using the —override.canyon flag on both op-node & op-geth. OP Labs will also collaborate with the community to extensively communicate that the upgrade is no longer happening. OP Labs will release a new version of op-node & op-geth with the Canyon activation date baked in and publicize to node operators & end users that the Canyon upgrade will be occurring. Hey @trianglesphere we are thrilled at the additional level of scalability brought about by the Canyon Network Upgrade! The Lyra Chain has recently been deployed ahead of the V2 launch of the Lyra Protocol. Is it possible to include Lyra Chain in this proposal and the scheduled upgrades? mirror.xyz Lyra Chain: Harder, Better, Faster, Stronger We know Lyra V2 is coming. We know it’s made for pro traders. And we know it’s the most scalable derivatives protocol yet. But how did we build it all onchain? It’s time to find out how we leveraged the OP Stack to build Lyra Chain and make us