Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add shared lockbox invariants #15

Merged

Conversation

agusduha
Copy link
Member

No description provided.

@agusduha agusduha self-assigned this Dec 13, 2024
the on-chain chains list is simplified by assuming that joining the Shared Lockbox is
equivalent to joining the op-governed dependency set.
Based on the assumption that a chain joining the op-governed dependency set is an irreversible process,
it is assume that joining the Shared Lockbox is equivalent to it.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
it is assume that joining the Shared Lockbox is equivalent to it.
it is assumed that joining the Shared Lockbox is equivalent to it.

Comment on lines 20 to 21
Based on the assumption that a chain joining the op-governed dependency set is an irreversible process,
it is assume that joining the Shared Lockbox is equivalent to it.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this a business decision or a protocol specification. Should we mention this here 🤔?
In which way is it helpful to explain that when talking about the upgrade process?

@@ -26,19 +29,30 @@ The `OptimismPortal` contract will add the following storage layout and modified

### Integrating `SharedLockbox`

The integration with the `SharedLockbox` involves adding extra steps when executing deposit transactions
The integration with the `SharedLockbox` involves extra steps when executing deposit transactions
Copy link

@0xDiscotech 0xDiscotech Dec 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel this comment ethereum-optimism#465 (comment) is not 100% addressed like this.

What I understand he's asking is to say sthing like:

The extra steps are:
* Locking ETH on a deposit transactions
* unlocking ETH on finalized withdrawals

The integration with the `SharedLockbox` involves extra steps when executing deposit transactions
or finalizing withdrawal transactions.
These steps are locking and unlocking ETH without altering other aspects of the current `OptimismPortal` implementation.
The integration with the `SharedLockbox` locking ETH when executing deposit transactions and unlocking ETH

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The integration with the `SharedLockbox` locking ETH when executing deposit transactions and unlocking ETH
The integration with the `SharedLockbox` involves locking ETH when executing deposit transactions and unlocking ETH

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

@agusduha agusduha merged commit b25ed80 into sc-feat/add-shared-lockbox Dec 17, 2024
1 check passed
@agusduha agusduha deleted the feat/add-shared-lockbox-invariants branch December 17, 2024 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants