šŸ§»
Rollup Economics Research (ROP-3)
/
Optimism Specs (Condensed)
/
10. Network Upgrades

10. Network Upgrades

Post-Bedrock upgrades
Regolith
  • TheĀ isSystemTxĀ boolean is disabled, system transactions now use the same gas accounting rules as regular deposits.
  • The actual deposit gas-usage is recorded in the receipt of the deposit transaction, and subtracted from the L2 block gas-pool. Unused gas of deposits is not refunded with ETH however, as it is burned on L1.
  • TheĀ nonceĀ value of the deposit sender account, before the transaction state-transition, is recorded in a new optional field (depositNonce), extending the transaction receipt (i.e. not present in pre-Regolith receipts).
  • The recorded depositĀ nonceĀ is used to correct the transaction and receipt metadata in RPC responses, including theĀ contractAddressĀ field of deposits that deploy contracts.
  • TheĀ gasĀ andĀ depositNonceĀ data is committed to as part of the consensus-representation of the receipt, enabling the data to be safely synced between independent L2 nodes.
Ā 
šŸ’”
The Regolith upgrade uses a L2 block timestamp activation rule.
šŸ’”
The block timestamp activation rule is specified in: - rollup-node (regolith_time) - execution engine (config.regolithTime)
šŸ§»
Rollup Economics Research (ROP-3)
/
Optimism Specs (Condensed)
/
10. Network Upgrades

10. Network Upgrades

Post-Bedrock upgrades
Regolith
  • TheĀ isSystemTxĀ boolean is disabled, system transactions now use the same gas accounting rules as regular deposits.
  • The actual deposit gas-usage is recorded in the receipt of the deposit transaction, and subtracted from the L2 block gas-pool. Unused gas of deposits is not refunded with ETH however, as it is burned on L1.
  • TheĀ nonceĀ value of the deposit sender account, before the transaction state-transition, is recorded in a new optional field (depositNonce), extending the transaction receipt (i.e. not present in pre-Regolith receipts).
  • The recorded depositĀ nonceĀ is used to correct the transaction and receipt metadata in RPC responses, including theĀ contractAddressĀ field of deposits that deploy contracts.
  • TheĀ gasĀ andĀ depositNonceĀ data is committed to as part of the consensus-representation of the receipt, enabling the data to be safely synced between independent L2 nodes.
Ā 
šŸ’”
The Regolith upgrade uses a L2 block timestamp activation rule.
šŸ’”
The block timestamp activation rule is specified in: - rollup-node (regolith_time) - execution engine (config.regolithTime)