runsheet for pausing L2 systems from L1

[artdgn]

If L2 sequencer is down, it is still possible to enqueue() transactions to the "L2 chain" on the optimism L1 contract. Upon sequencer resumption the system may or may not pause due to rates being stale. This depends on both CL and on timestamps injected into the OVM. This means that:

1. Possibly exploitative transactions can be enqueued by anyone.
2. System suspension can be enqueued to pause the system and resume it in a controllable manner. This will mitigate the risk from 1,

Whitelisted EOAs can trigger system suspension on L1 and L2, but enqueuing an L1->L2 tx is not straightforward (or done rutinely)

Task:

• Prepare a runsheet that will detail the steps and prepare the payload to be submitted to the bridge to trigger suspension.
• Test this works on kovan bridge setup.

Resources:

• Address aliasing peculiarities: https://community.optimism.io/docs/developers/build/differences/#address-aliasing
• Conversation with Optimism on their channel with some sample transactions (and a bug on etherscan that causes from to be wrongly displayed as 0x0)
• The method to be used: https://github.com/ethereum-optimism/optimism/blob/34649132e619e4ef4e1dbd01f3766c195fb29871/packages/contracts/contracts/L1/rollup/CanonicalTransactionChain.sol#L210
• All contracts in docs: https://community.optimism.io/docs/protocol/protocol-2.0/#canonicaltransactionchain-ctc
• Addresses: https://github.com/ethereum-optimism/optimism/tree/master/packages/contracts/deployments

[artdgn]

can be done by EOAs directly (e.g. deployer)