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

SuperchainERC20: Spike xERC20 over New Standard #10875

Closed
Tracked by #10877
tynes opened this issue Apr 29, 2024 · 5 comments
Closed
Tracked by #10877

SuperchainERC20: Spike xERC20 over New Standard #10875

tynes opened this issue Apr 29, 2024 · 5 comments
Assignees

Comments

@tynes
Copy link
Contributor

tynes commented Apr 29, 2024

This ticket involves spiking out what an xERC20 based superchain erc20 standard would like like compared to the one proposed in ethereum-optimism/specs#71. The learnings of this spike should be used to drive updates to the spec. We need to update the spec including the specific reasons behind the decision to go with one standard over the other.

@skeletor-spaceman skeletor-spaceman self-assigned this May 13, 2024
@tynes tynes transferred this issue from another repository Jun 17, 2024
@tynes tynes transferred this issue from ethereum-optimism/temp-export Jun 17, 2024
@tynes tynes added this to the Interop: Devnet 2 milestone Jun 17, 2024
@0xParticle
Copy link
Contributor

0xParticle commented Jul 25, 2024

@tynes we think this task is outdated and should be deprecated. How should we handle it?

@0xParticle 0xParticle moved this from In progress to Done in Interoperability Jul 31, 2024
@skeletor-spaceman
Copy link
Collaborator

closing this issue, since we already went with the superc20 vanilla design, while keeping SuperOPxERC20 as a custom implementation.

@stas
Copy link

stas commented Aug 14, 2024

@skeletor-spaceman where's the best place to follow the work on SuperOPxERC20?

@skeletor-spaceman
Copy link
Collaborator

hey @stas ! I just created the parent ticket for the SuperOPxERC20 standard :)
You'll be able to follow progress there: #11485
First we need the Custom Implementation Factory, to then create the xERC20 flavor on top :)

@stas
Copy link

stas commented Aug 14, 2024

Ty ty! Excited!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants