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

dev: add a way for partners to request the deployment of a DualVM token for their specific ERC20.cairo #1529

Open
Eikix opened this issue Oct 23, 2024 · 4 comments

Comments

@Eikix
Copy link
Member

Eikix commented Oct 23, 2024

IF a partner (e.g. Nimbora) creates a token (e.g. STRK LST)
THEN they can request Kakarot via a PR to the repo / Form completion / Issue to deploy a DualVM token
THEN Kakarot team can review the request and schedule a whitelist for that specific DualVM token

needs further scoping in technical review cc @enitrat @ClementWalter

@ClementWalter
Copy link
Member

We'll probably enable a service that deploys automatically dualvm when ERC20 starknet are deployed. In the meantime, they can reach out to the team for individual requests.

@ooochoche
Copy link

@ClementWalter is this open for contribution? If yes I would love to work on it

@Eikix
Copy link
Member Author

Eikix commented Oct 25, 2024

@ClementWalter is this open for contribution? If yes I would love to work on it

Hey, sorry it's not open

@Eikix
Copy link
Member Author

Eikix commented Oct 25, 2024

We'll probably enable a service that deploys automatically dualvm when ERC20 starknet are deployed. In the meantime, they can reach out to the team for individual requests.

We'll need a list of deployed dualVM tokens and their equivalent Starknet token, can this be scoped inside the issue?

@kkrt-labs kkrt-labs deleted a comment Oct 27, 2024
matthieuauger pushed a commit to matthieuauger/kakarot that referenced this issue Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: 🆕 Backlog
Development

No branches or pull requests

3 participants