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

Deploy Unlock protocol on Fuse mainnet #14565

Open
Supeeerpower opened this issue Sep 4, 2024 · 1 comment
Open

Deploy Unlock protocol on Fuse mainnet #14565

Supeeerpower opened this issue Sep 4, 2024 · 1 comment

Comments

@Supeeerpower
Copy link
Contributor

I am trying to deploy Unlock protocol to Fuse, but can't deploy hooks contracts and keyManager contract.

Just I want to deploy these contracts so that I can update fuse.ts.

image

So I made some change to /governance/scripts/deployments/keyManager.js like this and deploy again, and it occurs another issues.
image
image

@Calla-Ji
Copy link
Member

Calla-Ji commented Sep 4, 2024

Hi @Supeeerpower
I am not a developer but from what @julien51 said today during our Town Hall meeting:

Letting people deploy to new chains means that the Core Team of Unlock needs to maintain that added chain. So this creates additional work load for a small team. He asked if you can name at least two projects on Fuse who will definitely use Unlock Protocol on that chain. If yes he is happy to talk further.

First maybe clarify this. I am doing the same right now with LUKSO because it's really no use deploying to a chain where Unlock will not be visible to users or just not used.

Hope this makes sense :)

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

No branches or pull requests

2 participants