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

OPCM L1 Upgrades #159

Merged
merged 12 commits into from
Nov 22, 2024
Merged

OPCM L1 Upgrades #159

merged 12 commits into from
Nov 22, 2024

Conversation

maurelian
Copy link
Contributor

Describes a fully onchain upgrade process.

protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
@maurelian maurelian marked this pull request as ready for review November 19, 2024 19:19
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Outdated Show resolved Hide resolved
protocol/l1-upgrades.md Show resolved Hide resolved
Pure modifier
ownership transfer
Copy link
Contributor

@mds1 mds1 left a comment

Choose a reason for hiding this comment

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

love this

@maurelian maurelian merged commit 0034943 into main Nov 22, 2024
@maurelian maurelian deleted the L1-upgrades branch November 22, 2024 10:14
contracts within one block.
- **Declarative design:** As much as possible, a developer should be able to simply indicate what
bytecode should be deployed, and what storage values (if any) should be initialized or modified.
- **Deterministic upgrade calldata:** The exact calldata to be submitted during the upgrade should
Copy link
Contributor

Choose a reason for hiding this comment

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

@maurelian The AnchorStateRegistry is a possible exception to this where the calldata is based on recent chain state and that state cannot be known at the time of the governance proposal. While we can relax this chain state requirement for initializing the ASR, perhaps it would be good to callout this as design principle when writing smart contract initializers.

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.

9 participants