Replies: 8 comments 18 replies
-
Kickoff 06/17/2024Goals
Discussion
Project UpdatesInterop Go updates:
|
Beta Was this translation helpful? Give feedback.
-
Kickoff 06/24/2024Goals
Project UpdatesInterop Client (Go work) updates:Deriver refactorSince last update, landed:
Proto working on:
op-supervisor
deposit-tx handling
Superc20 updates:SuperchainERC20 StandardWe're about to make a PR on PR 71 that covers most of the required topics. Also, we'll focus on the xERC20 spike over the new standard. Liquidity MigrationWe have made small updates to the Mirror Factory Design Doc and have been discussing the Liquidity Migration and Mirror docs (see above). This week, we will discuss our designs (on Tuesday), and then we will move on to the specs. DevX
|
Beta Was this translation helpful? Give feedback.
-
Kickoff 07/08/2024Goals
Project UpdatesClientWe are resuming from a week of pause. deriver (events refactor), Proto:
op-supervisor, Adrian:
deposit-tx, Mofi:
Source of truth for communicating with devinfra: https://github.com/ethereum-optimism/devinfra-pod/issues/165 Governance
Superc20 (Wonderland) updates:SuperchainERC20 Standard specsWe continue updating our PR on SuperchainERC20 Standard specs:
The latest version is available for reviews: ethereum-optimism/specs#257 SuperchainERC20 Standard developmentWe have started onboard our solidity dev team into the project. Liquidity MigrationWe have worked extensively on design approaches around the Convert solution, and we have opened a new thread into the interop-evm Discord channel, discussing isolated vs. unified approaches. Next step is to make our design doc public. |
Beta Was this translation helpful? Give feedback.
-
Kickoff 07/17/2024Project UpdatesClient WorkQuick mid-week Interop client Go update: Devnet 1 timeline is slipping:
Deriver-refactor: done, deployed on Sepolia devnet, being tested in regular release flow. Supervisor: integration time, working on RPC endpoints and automated safety progression to update heads data. Deposit-tx interop work: no progress. SuperchainERC20Superc20 (Wonderland) updates: SuperchainERC20 Standard specsOur latest commit has been merged into specs repo. ethereum-optimism/specs#268 Superchain ERC20 developmentWe have started the development of the initial implementation of the Liquidity MigrationToday we had a design review session, and the convert-unified has been the selected as the design path to go forward. ethereum-optimism/design-docs#46 Now we're gonna start with the work on specs, breaking them into two separate projects: the convert solution itself and the registry for legacy token authenticity. SuperchainERC20 Factory specsWe're making great progress on the GovTokenGovernance (Agora + Diego) updates: GovernanceToken: ImplementationWorking on last implementation details at #11168, aiming to be ready for review EOD. Alligator: SpecsResolved last review comments and ready for another iteration: ethereum-optimism/specs#247 Alligator: ImplementationContract and predeploy setup in progress, aiming to be ready for review tommorow: #11167 |
Beta Was this translation helpful? Give feedback.
-
Kickoff 07/22/2024Goals
Project UpdatesInterop DevX Update:
Go Interop update:
Superc20 (Wonderland) updates:Superchain ERC20 developmentContinuing in the progress of initial version of SuperchainERC20 standard and Factory contracts. Liquidity MigrationWe continue making progress on the specs for convert approach and the needed registry. We plan to make a first PR this week. We started to work with other token cases to complete the TVL coverage. SuperchainERC20 Factory specsWe will make some changes regarding SuperchainERC20, most notably to make possible token deployments on L2 and conserving underlying token properties properly. ethereum-optimism/design-docs#50 Governance (Agora) updates:GovernanceToken: ImplementationGovernaceToken ready for review at #11167, decoupling to be easily reviewed. Alligator: SpecsWorking on resolving last comments from review at ethereum-optimism/specs#247 Alligator: ImplementationWorking on fuzz and unit tests for Alligator contract at #11167 |
Beta Was this translation helpful? Give feedback.
-
Kickoff 08/05/2024Goals
Interop Go updatesLocal devnetWork in progress. Draft by Proto: #11324 op-e2e testingCurrently blocked by minimal After that, for proper integration with unblocked path for full coverage into op-e2e, We still have an open design doc for cache-based integration of the deploy scripts into op-e2e: ethereum-optimism/design-docs#52 This may however be replaced with a newer alternative idea of running the Forge scripts in Go, to avoid caching complexity. Tracked here: #11360
|
Beta Was this translation helpful? Give feedback.
-
Update 08/14/2024Interop (Wonderland) updates:Implementation
Superc20 (Wonderland) updates:Implementation
Design Doc and Specs
Interop Go client updates
Once the cheatcodes PR is ready we can run through the deployment scripts of OPSM 0.5. And outside of interop we are reviewing the op-geth 1.14.8 changes, to land a snap-sync bugfix from upstream geth. |
Beta Was this translation helpful? Give feedback.
-
Kickoff 08/19/2024Goals
Project UpdatesInterop (Wonderland) updates:Implementation
Superc20 (Wonderland) updates:Implementation
Design Doc and Specs
Governance (Agora) updates:Implementation
Design Doc and Specs
Go client update: Supervisor Updates: This now includes test suites for new functionality Forge script op-e2e integrationWe landed all Go forge functions: #11490 The L2 genesis generation items (#11492, #11493) are being started today. SupervisorAxel is continuing on the cross-safe-head maintainer functionality: #11458 DevnetAfter the local devnet setup is done, and the supervisor core functions are ready, DevX Update[Supersim MVP]
[Supersim Extensibility]
[Reference Implementations]
[Interop Abstractions]
|
Beta Was this translation helpful? Give feedback.
-
This is a tracking discussion for updates on the development of the interop project.
Contributing
The interop specs serve as the source of truth for what is being built. The specs should be written before any implementations are merged and should be used to drive code review. Longer form discussions exist for async communications about the project.
There are 3 standups per week: Monday, Wednesday, and Friday. Notes are kept here. The Monday standup is required and all teams should provide a status update to share with the rest of the team about their work stream.
The design-docs repository should be used to build consensus on designs. Please follow the guidelines in the design docs repo's
README
.It is up to the discretion of the engineers to decide what should be turned into a design doc vs a spec. Some features should be a design doc first and then turned into a spec while others only need one of the two.
Meetings
A new comment should be created each week that includes status updates from each owner of a project. Further discussion about that week should be done in sub comments.
The following templates can be used:
Resources
Beta Was this translation helpful? Give feedback.
All reactions