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

[CUSTOM-SUPERTOKENS] Use metadata instead of hardcoded factory addresses #20

Open
d10r opened this issue Dec 20, 2022 · 2 comments · May be fixed by #26
Open

[CUSTOM-SUPERTOKENS] Use metadata instead of hardcoded factory addresses #20

d10r opened this issue Dec 20, 2022 · 2 comments · May be fixed by #26
Assignees
Labels
Team: Protocol Protocol Core, Sentinel, Peripherals, Protocol Infrastructure Tools & DevOps
Projects

Comments

@d10r
Copy link
Contributor

d10r commented Dec 20, 2022

And remove scripts/utils/constants.js

closes #26

@hellwolf hellwolf added this to Untriaged in PROTO Jan 2, 2023
@d10r d10r self-assigned this Jul 11, 2023
@d10r
Copy link
Contributor Author

d10r commented Jul 11, 2023

with the addition of the wizard this is getting more relevant

@d10r d10r added the Team: Protocol Protocol Core, Sentinel, Peripherals, Protocol Infrastructure Tools & DevOps label Jul 11, 2023
@ngmachado
Copy link
Collaborator

@d10r is right. We should add the metadata to this project. We already have some addresses to update. (SuperTokenFactory on Mumbai)

@hellwolf hellwolf changed the title Use metadata instead of hardcoded factory addresses [CUSTOM-SUPERTOKENS] Use metadata instead of hardcoded factory addresses Aug 7, 2023
@hellwolf hellwolf linked a pull request Aug 23, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team: Protocol Protocol Core, Sentinel, Peripherals, Protocol Infrastructure Tools & DevOps
Projects
No open projects
PROTO
  
Untriaged
Development

Successfully merging a pull request may close this issue.

2 participants