You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
So I made some change to
/governance/scripts/deployments/keyManager.js
like this and deploy again, and it occurs another issues.The text was updated successfully, but these errors were encountered: