Thanks to visit codestin.com
Credit goes to github.com

Skip to content

EVM network support #9304

@julien51

Description

@julien51

As of January 2024, Unlock Protocol has been deployed to 14 production networks and a few test networks.

Before we consider deploying on any network, we need at least the following:

  • EVM compatibility. At this point, our focus is on EVM networks. We do not need all of EVM, so we may still be able if some less frequently used opcodes are missing.
  • an RPC endpoint that we can use to deploy the contracts
  • Some tokens so we can deploy. We should not need much, but if you an airdrop enough to unlock-protocol.eth that would be very helpful (or tell us about faucets we can use!)
  • If you are advocating for a production network, we also need to be able to use a Gnosis Safe for "ownership" of the Unlock contract

This is the "bare" minimum for us to deploy the smart contracts. For the front end to work we also need the following:

Nice to have:

  • Block explorer with API to verify contracts
  • Uniswap (this is used to provide swap and purchase, as well as for distribution of UDT)
  • Bridges (Connext) so we can eventually govern the Unlock contract on this new network from the Unlock DAO

Want to get started yourself?

Because the core team is very busy it's not always easy for us to prioritize new chains... but everything about Unlock is open source so you should be able to do it yourself!

There is a "How to deploy the Protocol on a new network" section in the README .

Then you can look at past pull-requests such as Palm Network or Base Goerli

If you want the protocol deployed on more networks, please add them as comments to this issue, or upvote existing ones (no duplicates please!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions