[Core Protocol] Pause Withdrawal from l2 -> l1

[neodiz]

Did you check the documentation and specs?

• Yes

Was there anything unclear or missing?

Pause bridge

Good day. According to the documentation, it is possible to somehow pause the withdrawal from l2- to l1. I looked at the smart contract superchain config and found a pause method(The address is passed as a parameter). Also, only guardian can perform these actions.
Questions:

1. Can I, as a network operator, pause the withdrawal of funds?
2. If I can, what address should I pass in the parameters?
3. I also did not find a description of how to pause l1->l2
4. Is it possible to set acl whitelist ok blacklist on output of funds from l2->l1 and l1->l2 ?

Did you check for duplicate questions?

• Yes

Similar Questions or Issues Found

No response

Please select the type of request

• Bug Report
• Feature Request

Steps to Reproduce

No response

Expected vs. Actual Behaviour

No response

Software Versions

op-contract v3.0.0-rc.2
op-node v1.13.0
op-challenger v1.13.0
op-batcher v1.13.0

Operating System

ubuntu latest
using docker

Hardware Resources

No response

Configuration Files, Startup Flags & Environment Variables

No response

Error Messages / Logs

No response

Feature Description

No response

Purpose and Benefits

No response

Relevant Context or Examples

No response

[hash1go]

Hello!
First, only the Guardian can pause L2->L1 withdrawals. If the network operator is not the Guardian (or an authorized Pause Deputy), they cannot pause. If they do hold that role, pass your chain’s ETHLockbox address to pause(<identifier>) to pause that chain, or pass address(0) for a global pause. For details, see the official specs.
https://specs.optimism.io/protocol/system-config.html#paused
https://specs.optimism.io/protocol/stage-1.html#pause-identifier
https://specs.optimism.io/protocol/superchain-config.html#pause

Second, there is no standard way to pause L1->L2 deposits. Nor is there a built-in whitelist/blacklist or other fine-grained controls. Achieving these would require out-of-protocol customizations (for example, modifying contracts or the gateway).

[neodiz]

Thanks for you help.

Can you explain where i can found ETHLockbox?
You mean i can setup my wallet from intent.toml(paramether superchainRoles -> guardian) then using op-deployer?

[hash1go]

For example, here is the ETH lockbox address for OP Mainnet.
https://etherscan.io/address/0xbEb5Fc579115071764c7423A4f12eDde41f106Ed#readProxyContract

I'm not familiar with the setup process using op-deployer.
cc: @opfocus Could you mention someone who is knowledgeable about op-deployer?

[neodiz]

@hash1go @opfocus Have any new for my discussions. Thanks

[Atharv181]

Hello Team @hash1go,
I have a similar question, so I’m posting it here in this thread.

I am working on transferring messages from the Optimism chain to Ethereum using the CrossDomainMessenger.
I have the following questions:

1. Does the bridge work similarly to token withdrawals, i.e., can it be paused by a guardian? and once paused message will not be executed on L1.

2. The CrossDomainMessenger.sol contract has a relayMessage function with the following comments:

        // On L1 this function will check the Portal for its paused status.
        // On L2 this function should be a no-op, because paused will always return false.

Does this mean that when I send a message from L2, it will not revert, but the message will not be delivered on L1 if the bridge is paused?

3. If I send a message from L2 to L1 while the bridge is paused, will those messages be replayed automatically once the bridge is unpaused? Or do I need to ensure that I don’t send any messages from L2 when the bridge is paused?

Thank you!