[Core Protocol] Pause mechanism

[unknownunknown1]

Did you check the documentation and specs?

• Yes

Was there anything unclear or missing?

Hi, I have a couple of questions regarding pause mechanism. https://docs.optimism.io/stack/security/pause

1. In what cases do you plan to use the pause feature? What would you say is the likelihood of ever using it?
2. When bridge is paused all L2->L1 txs are stopped. But when it's unpaused will they ever be picked up? Or just discarded?

We are planning to use a contract with cross-chain communication (Mainnet - OP), and our L2 tx updates the status of the contract that makes it not possible to replay L2->L1 call if it fails. We want to know how fatal it might be

Thanks

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

No response

Operating System

No response

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

[imtipi]

In what cases do you plan to use the pause feature? What would you say is the likelihood of ever using it?

note: i am a technerd (aka community contributor), i give my answer base on my knowledge of op stack. if you running service/business in production environment, please contact team for the most accurate answer

most likely use in critical vulnerabilities found in bridge contracts,or other attack attempts found

When bridge is paused all L2->L1 txs are stopped. But when it's unpaused will they ever be picked up? Or just discarded?

pause function only stops you from finalize your pending withdrawal,you can still start new withdrawal or prove withdrawal

[unknownunknown1]

Thanks for your response, but as for 2nd question, do I understand correctly that L2->L1 txs can be finalized when the bridge is unpaused?
Or to put it plainly, the bridge is paused -> I make L2-L1 tx -> I can prove it on L1 but can't actually use it yet so the tx is stuck -> when bridge is unpaused I can finalize that tx and my L1 contract will process it, so nothing is discarded in the end.
Is it correct interpretation?

[imtipi]

when bridge is unpaused I can finalize that tx and my L1 contract will process it, so nothing is discarded in the end.

yes, nothing is discarded,only delays

unless we assume theres contract upgrade following the pause,which might require you prove again,but still won't discard(treat it as rollback?)

heres an example:https://docs.optimism.io/notices/upgrade-13#for-bridges-and-users

All withdrawals that are not finalized before the Fault Proofs upgrade executes will need to be reproven after the upgrade is complete. You may want to consider waiting until after the upgrade is complete to begin a withdrawal during this 7-day window.

the upgrade also upgraded the contract, makes the withdrawal transaction needs to reprove

[unknownunknown1]

Thank you

[imtipi]

👍please mark as answered if your question is solved