
Today, we’re introducing a new tool that lets a developer change the behavior of deployed locks through hooks while still using the Unlock Labs checkout user interface. This is implemented by way of a data builder URL in the checkout config.

![data-hook.png](/images/blog/data-hook.png)

But first, let’s start with a bit of context!

## Giving Unlock Protocol the hook

Inside Unlock, the membership contract is called `PublicLock`. Unlock is a protocol because every membership contract (of the same protocol version) implements the same functions and features. When a creator deploys _their_ lock, they deploy a contract from a template.

Over the years, many creators have told us about the need to customize the behavior of their contracts. To maintain the “base” behavior standard, we introduced the [concept of “hooks.”](https://docs.unlock-protocol.com/core-protocol/public-lock/hooks)

Hooks introduce the ability to call third-party contracts as part of specific lock functions, while still retaining the protocol-standard functions. These hooks can be [configured by lock managers](https://docs.unlock-protocol.com/core-protocol/public-lock/access-control). For example, we introduced a few “public” hook contracts such as our [password hook](https://unlock-protocol.com/guides/password-protected-nft-memberships/), which is used for situations where a lock manager only wants the subset of individuals who know the password to be able to create a membership.

One of these hooks is called `onPurchaseHook`, and you probably understand from its name: it is called by the public lock’s `purchase` function. This `onPurchaseHook` hook includes 2 different functions:

- `keyPurchasePrice` is a function that is called with the following parameters: buyer’s address, recipient of the NFT address (they’re often the same but could be different), the referrer address, and a _mysterious `data`_ parameter (we’ll come back to this soon). The `keyPurchasePrice` function is expected to return a number, the amount the buyer is expected to pay for the membership. This can be used to make membership prices dynamic.
- `onKeyPurchase` is a function that is called with the same parameters as the function above, as well as a `tokenId` parameter for the membership being bought, and a few more items. Again, there is also a `data` parameter.

The lock’s purchase function will **first** call the `keyPurchasePrice` to determine the price to be paid (and especially if the user has approved enough!), and will finish its execution by calling `onKeyPurchase` .

Remember: hooks are proper contracts, so they can also store any data they want, and could also include other functions. A single hook can also implement multiple hook functions to be called at different points in the lock’s lifecycle.

## Introducing the Data Builder URL

In the previous section, we discussed that both `keyPurchasePrice` and `onKeyPurchase` have a `data` argument. That `data` parameter is, in fact, completely ignored by the lock itself and just passed to the hook’s function. It can be used by the front-end application to send data to the hook so the hook can change its behavior based on it.

For example, this `data` argument is what we use to pass a `secret` corresponding to the password in the context of the password hook. We could also pass some useful metadata to be stored in the hook and returned by the lock to display specific metadata.

Now, our front-end checkout application does not “know” how to build the `data` blob for the specific hooks deployed on specific contracts. For this reason, we are introducing what we call _Data Builder URLs_.

The `dataBuilder` is a new parameter you can use inside of the [paywall configuration](https://docs.unlock-protocol.com/tools/checkout/configuration) for any lock that you are configuring there. If the `dataBuilder` is set, then our front-end application will perform a GET request to it and include the following parameters: `recipient`, `lockAddress`, and `network`, so that the web application can compute a specific `data` blob to be passed as an argument for the `purchase` function.

## An example!

Our friends at [Zealous](https://zealous.app) wanted to create a new kind of membership for their platform. Anyone who has their membership NFT can access some premium features. However, they wanted to create a system where people who owned NFTs from specific collections would get a discount.

Looking up what NFTs someone owns using an on-chain script would be extremely expensive (and maybe even impossible as many contracts don’t include a way to list tokens per address), so we must do it off-chain. However, doing it solely off-chain would expose us to the possibility of someone claiming they own a special NFT (when they actually don’t) so they could grab the discount. So we’re taking a mixed approach: we look for NFTs owned by the user off-chain, but then create a `dataBuilder` to compute a “hint” that is passed as `data` to the contract.

The hook can then use the hint to confirm that indeed the user owns one of these NFTs.


Extending Unlock Protocol’s “hook” capabilities with data.

Extending Unlock Protocol’s “hook” capabilities with data

The Data Builder URL

Today, we’re introducing a new tool that lets a developer change the behavior of deployed locks through hooks while still using the Unlock Labs checkout user interface. This is implemented by way of a data builder URL in the checkout config.
<img src="/images/blog/data-hook.png" alt="data-hook.png">
But first, let’s start with a bit of context!
<h2>Giving Unlock Protocol the hook</h2>
Inside Unlock, the membership contract is called <code>PublicLock</code>. Unlock is a protocol because every membership contract (of the same protocol version) implements the same functions and features. When a creator deploys their lock, they deploy a contract from a template.
Over the years, many creators have told us about the need to customize the behavior of their contracts. To maintain the “base” behavior standard, we introduced the <a href="https://docs.unlock-protocol.com/core-protocol/public-lock/hooks">concept of “hooks.”</a>
Hooks introduce the ability to call third-party contracts as part of specific lock functions, while still retaining the protocol-standard functions. These hooks can be <a href="https://docs.unlock-protocol.com/core-protocol/public-lock/access-control">configured by lock managers</a>. For example, we introduced a few “public” hook contracts such as our <a href="https://unlock-protocol.com/guides/password-protected-nft-memberships/">password hook</a>, which is used for situations where a lock manager only wants the subset of individuals who know the password to be able to create a membership.
One of these hooks is called <code>onPurchaseHook</code>, and you probably understand from its name: it is called by the public lock’s <code>purchase</code> function. This <code>onPurchaseHook</code> hook includes 2 different functions:
<ul>
<li><code>keyPurchasePrice</code> is a function that is called with the following parameters: buyer’s address, recipient of the NFT address (they’re often the same but could be different), the referrer address, and a mysterious <code>data</code> parameter (we’ll come back to this soon). The <code>keyPurchasePrice</code> function is expected to return a number, the amount the buyer is expected to pay for the membership. This can be used to make membership prices dynamic.</li>
<li><code>onKeyPurchase</code> is a function that is called with the same parameters as the function above, as well as a <code>tokenId</code> parameter for the membership being bought, and a few more items. Again, there is also a <code>data</code> parameter.</li>
</ul>
The lock’s purchase function will first call the <code>keyPurchasePrice</code> to determine the price to be paid (and especially if the user has approved enough!), and will finish its execution by calling <code>onKeyPurchase</code> .
Remember: hooks are proper contracts, so they can also store any data they want, and could also include other functions. A single hook can also implement multiple hook functions to be called at different points in the lock’s lifecycle.
<h2>Introducing the Data Builder URL</h2>
In the previous section, we discussed that both <code>keyPurchasePrice</code> and <code>onKeyPurchase</code> have a <code>data</code> argument. That <code>data</code> parameter is, in fact, completely ignored by the lock itself and just passed to the hook’s function. It can be used by the front-end application to send data to the hook so the hook can change its behavior based on it.
For example, this <code>data</code> argument is what we use to pass a <code>secret</code> corresponding to the password in the context of the password hook. We could also pass some useful metadata to be stored in the hook and returned by the lock to display specific metadata.
Now, our front-end checkout application does not “know” how to build the <code>data</code> blob for the specific hooks deployed on specific contracts. For this reason, we are introducing what we call Data Builder URLs.
The <code>dataBuilder</code> is a new parameter you can use inside of the <a href="https://docs.unlock-protocol.com/tools/checkout/configuration">paywall configuration</a> for any lock that you are configuring there. If the <code>dataBuilder</code> is set, then our front-end application will perform a GET request to it and include the following parameters: <code>recipient</code>, <code>lockAddress</code>, and <code>network</code>, so that the web application can compute a specific <code>data</code> blob to be passed as an argument for the <code>purchase</code> function.
<h2>An example!</h2>
Our friends at <a href="https://zealous.app">Zealous</a> wanted to create a new kind of membership for their platform. Anyone who has their membership NFT can access some premium features. However, they wanted to create a system where people who owned NFTs from specific collections would get a discount.
Looking up what NFTs someone owns using an on-chain script would be extremely expensive (and maybe even impossible as many contracts don’t include a way to list tokens per address), so we must do it off-chain. However, doing it solely off-chain would expose us to the possibility of someone claiming they own a special NFT (when they actually don’t) so they could grab the discount. So we’re taking a mixed approach: we look for NFTs owned by the user off-chain, but then create a <code>dataBuilder</code> to compute a “hint” that is passed as <code>data</code> to the contract.
The hook can then use the hint to confirm that indeed the user owns one of these NFTs.


[ETHSanFrancisco](https://sf.ethglobal.com) was the largest in-person hackathon to date from ETHGlobal, and the hackers delivered! Over 1700(!) hackers from around the globe showed up in force to meet, learn, and build new projects.

The Unlock team showed up in a big way, and had an incredible time meeting hundred of hackers, having great conversations, and getting a chance to bond together as well!

![unlock team selfie](/images/blog/ethsf22/unlock-team-selfie.jpeg)
photo: @julien51

More pictures and thoughts below, but first...the winners of prizes in the Unlock hackathon!

The most incredible part of ETHSanFrancisco was getting the opportunity to connect with the incredible group of hackers, learners, and new friends who stopped by for conversations in the booth over the course of the three days of the hackathon. There were over two dozen projects submitted and, when the dust cleared and the entries were judged, three projects stood out. They were...

## First Prize Winner — Smart Coupons

![smart coupons image](https://storage.googleapis.com/ethglobal-api-production/projects%2Foh282%2Fimages%2FScreenshot_2022-11-06_at_6.50.26_AM.png)

**Description:** This project is a frontend + plugin into the Salesforce (SFDC) ecosystem to manage Web3-based marketing campaigns to enable an on-ramp for web2 companies to engage their communities within their existing marketing toolset. Our frontend is a sample implementation of how a client (in this case Adidas) would implement the solution. Within their existing web2 channels, the client would offer gamified incentives for users to connect their wallet details. After connecting their wallet, the users would be able to complete additional data enrichment challenges to earn Web3-based rewards. These rewards would be generated from SFDC directly based on specified campaign goals. Once the wallet data is within Salesforce, we enrich the database with on-chain information, tied to the individual lead profile created for the user. This enables a more robust view of the customer, with the ability to create insights and make more informed decisions about campaign targeting.

**Demo:** [https://ethglobal.com/showcase/smart-coupons-oh282](https://ethglobal.com/showcase/smart-coupons-oh282)

## Second Prize Winner — HNDSHK

![hndshk image](https://storage.googleapis.com/ethglobal-api-production/projects%2Fbgqfn%2Fimages%2FSolution.png)

**Description:** HNDSHK allows you to instantly connect and nourish irreplaceable relationships through NFT handshake cards which you can create, manage, and SHK. Exchanging cards is done instantly through NFC tap (HNDSHK). And when you HNDSHK, you also connect on mutual social handles and a POAP is minted which further documents the occasion. Since NFC taps can only be done in person, HNDSHK encourages in-person interactions. In contrast to popular Social Media platforms which are often attention grabs or races to build a following, HNDSHK incentives quality over quantity connections. This is done through a gamified experience - card rarity upgrades, personal card benefits, and reach-out reminders.

**Demo:** [https://ethglobal.com/showcase/hndshk-bgqfn](https://ethglobal.com/showcase/hndshk-bgqfn)

## Third Prize Winner — Alexandria

![alexandria image](https://storage.googleapis.com/ethglobal-api-production/projects%2F3db0q%2Fimages%2Fscreenshot_3.png)

**Description:** This project allows users to borrow an access NFT that gives them access to view a book through our site. The contract allows anyone to borrow a book for however long they like (as long as you can pay the fee). Whilst giving authors royalties on their payments. We allow authors to make sure they get paid for each time their book gets read. The NFT also acts as a way for you to know all the previous borrowers of your book. Once you run out of collateral on your borrow, the NFT gets automatically transferred back to the marketplace via a liquidation function anyone can call.

**Demo:** [https://ethglobal.com/showcase/alexandria-3db0q](https://ethglobal.com/showcase/alexandria-3db0q)

## Fun and learning for everyone

Hackathons are one of our favorite ways to connect with our frens in the web3 community who are creating and building the next layer of internet infrastructure.

We say a giant THANK YOU to all of the winners and every single team that deployed Unlock to bring their vision to life.

We’re so grateful to ETHGlobal for its continued support of the web3 space and for allowing us to participate in these amazing hackathons! We look forward to seeing these projects evolve and for all the incredible connections, learning, and growth they empower.

As promised, here are a few shots from the event — can't wait for the next one!

![unlock 1](/images/blog/ethsf22/unlock-1.png)

![unlock 2](/images/blog/ethsf22/unlock-2.png)

![unlock 3](/images/blog/ethsf22/unlock-3.png)

![unlock 4](/images/blog/ethsf22/unlock-4.png)

![unlock 5](/images/blog/ethsf22/unlock-5.png)

![unlock 6](/images/blog/ethsf22/unlock-6.png)

![unlock 7](/images/blog/ethsf22/unlock-7.png)
photo: @ccarfi


Over two dozen teams built memberships into their projects using Unlock at the latest ETHGlobal Hackathon — here are the winners.

Over two dozen teams built memberships into their projects using Unlock at the latest ETHGlobal Hackathon — here are the winners

ETHSanFrancisco Hackathon's Winners

<a href="https://sf.ethglobal.com">ETHSanFrancisco</a> was the largest in-person hackathon to date from ETHGlobal, and the hackers delivered! Over 1700(!) hackers from around the globe showed up in force to meet, learn, and build new projects.
The Unlock team showed up in a big way, and had an incredible time meeting hundred of hackers, having great conversations, and getting a chance to bond together as well!
<img src="/images/blog/ethsf22/unlock-team-selfie.jpeg" alt="unlock team selfie">
photo: @julien51
More pictures and thoughts below, but first...the winners of prizes in the Unlock hackathon!
The most incredible part of ETHSanFrancisco was getting the opportunity to connect with the incredible group of hackers, learners, and new friends who stopped by for conversations in the booth over the course of the three days of the hackathon. There were over two dozen projects submitted and, when the dust cleared and the entries were judged, three projects stood out. They were...
<h2>First Prize Winner — Smart Coupons</h2>
<img src="https://storage.googleapis.com/ethglobal-api-production/projects%2Foh282%2Fimages%2FScreenshot_2022-11-06_at_6.50.26_AM.png" alt="smart coupons image">
Description: This project is a frontend + plugin into the Salesforce (SFDC) ecosystem to manage Web3-based marketing campaigns to enable an on-ramp for web2 companies to engage their communities within their existing marketing toolset. Our frontend is a sample implementation of how a client (in this case Adidas) would implement the solution. Within their existing web2 channels, the client would offer gamified incentives for users to connect their wallet details. After connecting their wallet, the users would be able to complete additional data enrichment challenges to earn Web3-based rewards. These rewards would be generated from SFDC directly based on specified campaign goals. Once the wallet data is within Salesforce, we enrich the database with on-chain information, tied to the individual lead profile created for the user. This enables a more robust view of the customer, with the ability to create insights and make more informed decisions about campaign targeting.
Demo: <a href="https://ethglobal.com/showcase/smart-coupons-oh282">https://ethglobal.com/showcase/smart-coupons-oh282</a>
<h2>Second Prize Winner — HNDSHK</h2>
<img src="https://storage.googleapis.com/ethglobal-api-production/projects%2Fbgqfn%2Fimages%2FSolution.png" alt="hndshk image">
Description: HNDSHK allows you to instantly connect and nourish irreplaceable relationships through NFT handshake cards which you can create, manage, and SHK. Exchanging cards is done instantly through NFC tap (HNDSHK). And when you HNDSHK, you also connect on mutual social handles and a POAP is minted which further documents the occasion. Since NFC taps can only be done in person, HNDSHK encourages in-person interactions. In contrast to popular Social Media platforms which are often attention grabs or races to build a following, HNDSHK incentives quality over quantity connections. This is done through a gamified experience - card rarity upgrades, personal card benefits, and reach-out reminders.
Demo: <a href="https://ethglobal.com/showcase/hndshk-bgqfn">https://ethglobal.com/showcase/hndshk-bgqfn</a>
<h2>Third Prize Winner — Alexandria</h2>
<img src="https://storage.googleapis.com/ethglobal-api-production/projects%2F3db0q%2Fimages%2Fscreenshot_3.png" alt="alexandria image">
Description: This project allows users to borrow an access NFT that gives them access to view a book through our site. The contract allows anyone to borrow a book for however long they like (as long as you can pay the fee). Whilst giving authors royalties on their payments. We allow authors to make sure they get paid for each time their book gets read. The NFT also acts as a way for you to know all the previous borrowers of your book. Once you run out of collateral on your borrow, the NFT gets automatically transferred back to the marketplace via a liquidation function anyone can call.
Demo: <a href="https://ethglobal.com/showcase/alexandria-3db0q">https://ethglobal.com/showcase/alexandria-3db0q</a>
<h2>Fun and learning for everyone</h2>
Hackathons are one of our favorite ways to connect with our frens in the web3 community who are creating and building the next layer of internet infrastructure.
We say a giant THANK YOU to all of the winners and every single team that deployed Unlock to bring their vision to life.
We’re so grateful to ETHGlobal for its continued support of the web3 space and for allowing us to participate in these amazing hackathons! We look forward to seeing these projects evolve and for all the incredible connections, learning, and growth they empower.
As promised, here are a few shots from the event — can't wait for the next one!
<img src="/images/blog/ethsf22/unlock-1.png" alt="unlock 1">
<img src="/images/blog/ethsf22/unlock-2.png" alt="unlock 2">
<img src="/images/blog/ethsf22/unlock-3.png" alt="unlock 3">
<img src="/images/blog/ethsf22/unlock-4.png" alt="unlock 4">
<img src="/images/blog/ethsf22/unlock-5.png" alt="unlock 5">
<img src="/images/blog/ethsf22/unlock-6.png" alt="unlock 6">
<img src="/images/blog/ethsf22/unlock-7.png" alt="unlock 7">
photo: @ccarfi


[thirdweb](https://thirdweb.com/) provides powerful SDKs and intuitive tools for developers to build and ship applications faster. As of today, you can deploy your Unlock membership smart contracts directly from the thirdweb UI and directly use the thirdweb SDK to interact with the contract.

You can view Unlock’s contracts on thirdweb at [https://thirdweb.com/unlock-protocol.eth/](https://thirdweb.com/unlock-protocol.eth/).

![thirdweb screenshot](/images/blog/thirdweb/thirdweb-screenshot.png)

At Unlock, we are building a membership protocol — an underlying set of smart contracts that can be used by anyone who needs to implement memberships or subscriptions. We’re making huge efforts to ensure that these contracts can be used by _any_ developer to build their own applications and platforms using the tools of _their_ choice. (Of course, we have also crafted no-code interfaces and applications to ease the use of these contracts for creators as well.)

We’re really thrilled that developers can now start building membership and subscription applications using thirdweb’s developer tools and SDK. And, as a decentralized protocol, developers could even build applications without telling anyone that they use Unlock Protocol under the hood, in the same way that most web applications don’t advertise that they use HTML or TCP to let you interact with them! That’s the beauty of open protocols and the open web.

We can’t wait to see what you end up building with thirdweb and Unlock!


You can now use thirdweb’s SDK and tooling to deploy your membership smart contracts

You can now use thirdweb’s SDK and tooling to deploy your membership smart contracts.

Unlock Contracts Now Available in thirdweb’s Registry

<a href="https://thirdweb.com/">thirdweb</a> provides powerful SDKs and intuitive tools for developers to build and ship applications faster. As of today, you can deploy your Unlock membership smart contracts directly from the thirdweb UI and directly use the thirdweb SDK to interact with the contract.
You can view Unlock’s contracts on thirdweb at <a href="https://thirdweb.com/unlock-protocol.eth/">https://thirdweb.com/unlock-protocol.eth/</a>.
<img src="/images/blog/thirdweb/thirdweb-screenshot.png" alt="thirdweb screenshot">
At Unlock, we are building a membership protocol — an underlying set of smart contracts that can be used by anyone who needs to implement memberships or subscriptions. We’re making huge efforts to ensure that these contracts can be used by any developer to build their own applications and platforms using the tools of their choice. (Of course, we have also crafted no-code interfaces and applications to ease the use of these contracts for creators as well.)
We’re really thrilled that developers can now start building membership and subscription applications using thirdweb’s developer tools and SDK. And, as a decentralized protocol, developers could even build applications without telling anyone that they use Unlock Protocol under the hood, in the same way that most web applications don’t advertise that they use HTML or TCP to let you interact with them! That’s the beauty of open protocols and the open web.
We can’t wait to see what you end up building with thirdweb and Unlock!


In the Unlock Protocol, every time a key is purchased for any lock, a small transaction is sent back to the core Unlock factory contract to keep track of all existing sales on the network. For each network (Ethereum mainnet, Polygon, etc.), we calculate what we call a Gross Network Product (GNP) that consolidates the value of all sales into a single amount of native currency (ETH for mainnet, MATIC for Polygon, etc). The GNP is a useful indicator to track the evolution of the protocol’s activity across chains.

Unlock has upgraded its price oracle to Uniswap v3 to increase accuracy and coverage when calculating the total value of sales on each network.

## The Oracle Problem

Locks across networks can be priced in a variety of ERC20-compatible tokens. Therefore, we need to convert the amount of ERC20 tokens to native currency before adding it to the GNP. In blockchain ecosystems, the system that allows you to retrieve information from a 3rd party service (such as retrieving the price of a token) is called an [oracle](https://ethereum.org/en/developers/docs/oracles/).

The main issue with smart contracts is that they can’t interact properly outside of the chain, and therefore require “oracles” to tell them what is happening outside, in the off-chain world. The famous [oracle problem](https://chain.link/education/blockchain-oracles) states that contracts on one hand can’t access data outside of the chain, but on the other hand shouldn’t rely to a single source of trust to provide data as this nullify the advantages of a decentralised security model. To mitigate this inherent risk, models of decentralised oracles have been developed.

## Using Uniswap v3’s Decentralized Oracle

Uniswap is one of the most famous decentralised exchanges operating on EVM chains. The new version (Uniswap v3) provides a neat way to query exchange data through an oracle in the form of a [simple contract](https://docs.uniswap.org/protocol/concepts/V3-overview/oracle). To date, the Unlock Protocol has been using the prior version of the Uniswap Oracle (v2), which required us to maintain a dedicated oracle. As of today, the Unlock Protocol will be upgraded to use the latest Uniswap v3, providing a more reliable and comprehensive coverage of various token prices. In this new implementation, GNP calculations will be simplified and cover a wider variety of possible tokens.

You can see the details of the changes in [this pull request](https://github.com/unlock-protocol/unlock/pull/10030), as well as use the oracle for your own needs by querying directly the deployed contract on each network.

Here are the addresses of contracts deployed on the [various networks](https://docs.uniswap.org/protocol/reference/deployments) where Uniswap is supported:

- mainnet: [`0x951A807b523cF6e178e0ab80fBd2C9B035521931`](https://etherscan.io/address/0x951A807b523cF6e178e0ab80fBd2C9B035521931)
- polygon : [`0xE77c7F14e8EB9925ca418bF80c0a81a5B9C87683`](https://polygonscan.com/address/0xE77c7F14e8EB9925ca418bF80c0a81a5B9C87683)
- arbitrum : [`0x821d830a7b9902F83359Bf3Ac727B04b10FD461d`](https://arbiscan.io/address/0x821d830a7b9902F83359Bf3Ac727B04b10FD461d)
- optimism : [`0x1FF7e338d5E582138C46044dc238543Ce555C963`](https://optimistic.etherscan.io/address/0x1FF7e338d5E582138C46044dc238543Ce555C963#code)
- celo : [`0x5108412Dd50A6ea79d2F13D5d1A23FDD9bF532db`](https://celoscan.io/address/0x5108412Dd50A6ea79d2F13D5d1A23FDD9bF532db#code)
- mumbai : [`0x5108412Dd50A6ea79d2F13D5d1A23FDD9bF532db`](https://mumbai.polygonscan.com/address/0x5108412Dd50A6ea79d2F13D5d1A23FDD9bF532db#code)
- goerli : [`0x25197CaCDE16500032EF4B35d60c6f7aEd4a38a5`](https://goerli.etherscan.io/address/0x25197CaCDE16500032EF4B35d60c6f7aEd4a38a5)


Unlock upgrades its price oracle to Uniswap v3 to increase accuracy and coverage when calculating the total value of sales on each network.

Unlock upgrades Uniswap Oracle to v3 for more accurate calculations of Unlock Gross Network Product

Using the Uniswap v3 Oracle in the Unlock Contract

In the Unlock Protocol, every time a key is purchased for any lock, a small transaction is sent back to the core Unlock factory contract to keep track of all existing sales on the network. For each network (Ethereum mainnet, Polygon, etc.), we calculate what we call a Gross Network Product (GNP) that consolidates the value of all sales into a single amount of native currency (ETH for mainnet, MATIC for Polygon, etc). The GNP is a useful indicator to track the evolution of the protocol’s activity across chains.
Unlock has upgraded its price oracle to Uniswap v3 to increase accuracy and coverage when calculating the total value of sales on each network.
<h2>The Oracle Problem</h2>
Locks across networks can be priced in a variety of ERC20-compatible tokens. Therefore, we need to convert the amount of ERC20 tokens to native currency before adding it to the GNP. In blockchain ecosystems, the system that allows you to retrieve information from a 3rd party service (such as retrieving the price of a token) is called an <a href="https://ethereum.org/en/developers/docs/oracles/">oracle</a>.
The main issue with smart contracts is that they can’t interact properly outside of the chain, and therefore require “oracles” to tell them what is happening outside, in the off-chain world. The famous <a href="https://chain.link/education/blockchain-oracles">oracle problem</a> states that contracts on one hand can’t access data outside of the chain, but on the other hand shouldn’t rely to a single source of trust to provide data as this nullify the advantages of a decentralised security model. To mitigate this inherent risk, models of decentralised oracles have been developed.
<h2>Using Uniswap v3’s Decentralized Oracle</h2>
Uniswap is one of the most famous decentralised exchanges operating on EVM chains. The new version (Uniswap v3) provides a neat way to query exchange data through an oracle in the form of a <a href="https://docs.uniswap.org/protocol/concepts/V3-overview/oracle">simple contract</a>. To date, the Unlock Protocol has been using the prior version of the Uniswap Oracle (v2), which required us to maintain a dedicated oracle. As of today, the Unlock Protocol will be upgraded to use the latest Uniswap v3, providing a more reliable and comprehensive coverage of various token prices. In this new implementation, GNP calculations will be simplified and cover a wider variety of possible tokens.
You can see the details of the changes in <a href="https://github.com/unlock-protocol/unlock/pull/10030">this pull request</a>, as well as use the oracle for your own needs by querying directly the deployed contract on each network.
Here are the addresses of contracts deployed on the <a href="https://docs.uniswap.org/protocol/reference/deployments">various networks</a> where Uniswap is supported:
<ul>
<li>mainnet: <a href="https://etherscan.io/address/0x951A807b523cF6e178e0ab80fBd2C9B035521931"><code>0x951A807b523cF6e178e0ab80fBd2C9B035521931</code></a></li>
<li>polygon : <a href="https://polygonscan.com/address/0xE77c7F14e8EB9925ca418bF80c0a81a5B9C87683"><code>0xE77c7F14e8EB9925ca418bF80c0a81a5B9C87683</code></a></li>
<li>arbitrum : <a href="https://arbiscan.io/address/0x821d830a7b9902F83359Bf3Ac727B04b10FD461d"><code>0x821d830a7b9902F83359Bf3Ac727B04b10FD461d</code></a></li>
<li>optimism : <a href="https://optimistic.etherscan.io/address/0x1FF7e338d5E582138C46044dc238543Ce555C963#code"><code>0x1FF7e338d5E582138C46044dc238543Ce555C963</code></a></li>
<li>celo : <a href="https://celoscan.io/address/0x5108412Dd50A6ea79d2F13D5d1A23FDD9bF532db#code"><code>0x5108412Dd50A6ea79d2F13D5d1A23FDD9bF532db</code></a></li>
<li>mumbai : <a href="https://mumbai.polygonscan.com/address/0x5108412Dd50A6ea79d2F13D5d1A23FDD9bF532db#code"><code>0x5108412Dd50A6ea79d2F13D5d1A23FDD9bF532db</code></a></li>
<li>goerli : <a href="https://goerli.etherscan.io/address/0x25197CaCDE16500032EF4B35d60c6f7aEd4a38a5"><code>0x25197CaCDE16500032EF4B35d60c6f7aEd4a38a5</code></a></li>
</ul>


![metadata configurator video](/images/blog/metadata-configurator/main.gif)

Most creators want to customize the attributes and add features to their NFTs. These features show up on NFT marketplaces such as OpenSea. Until now, they had to customize and manage the metadata on their own and update it on their own. It required coding and dealing with scripts. It wasn’t user friendly and added friction to working with Unlock.

To simplify this process, we are launching a no-code metadata configurator. With it, creators can add attributes such as properties, levels, stats, and other metadata to their NFT right from the Unlock Dashboard. This new feature also provides custom presets for ticketing and adding creator content such as YouTube videos, website, and animations.

## How to start

On the lock management page, you can open the metadata configurator by clicking on the `Edit NFT Properties` button. This will only be visible for lock manager.

![lock manage page](/images/blog/metadata-configurator/lock-page.png)

The configurator is split into multiple sections. Each section is collapsible from the UI.

### Basic details

The basic details section contains fields such as name, description, and the external URL for your NFT memberships.

![Basics](/images/blog/metadata-configurator/basic.png)

### Event ticketing

The event ticketing section allows event organizers to set up custom data for their tickets. Any ticket metadata changed here will show up as attributes on OpenSea and other marketplaces. This ticket data is also used by Unlock to generate a QR code ticket for NFTs and power the verification experience.

![Ticket](/images/blog/metadata-configurator/ticket.png)

#### Preview

As you are making edits, you can click on the Preview Ticket button to see what your ticket would actually look like. All fields are updated in real-time to reflect changes.

![Preview Ticket](/images/blog/metadata-configurator/preview-ticket.png)

### Advanced

Creators with a YouTube channel or a blog can use this section to display their videos and blog posts in the main preview box on OpenSea and other marketplaces. A user will be able to go to OpenSea and watch the video directly on your NFT page.

![Advanced](/images/blog/metadata-configurator/advanced.png)

### Custom Properties

You can add custom properties, levels, and stats to your NFT to truly highlight the unique characteristics of your NFTs.

Please note that each item will be displayed slightly differently on OpenSea and other marketplaces. We provide a preview of how they will be displayed but it is not a 1-1 representation.

![Custom](/images/blog/metadata-configurator/custom.png)

#### Add Properties

You can open the Add Property modal using the Add button inside the property section. On Add Property modal, you can add or remove existing properties. Each property has a trait type and value.

![Add Properties](/images/blog/metadata-configurator/add-stats.png)

#### Add Levels

Each level has a trait type, value, and max value. The value and max value are used to display a progress indicator on OpenSea and other marketplaces.

![Add Levels](/images/blog/metadata-configurator/add-levels.png)

#### Add Stats

Stats are the same as levels, but won't be displayed as a progress indicator on OpenSea and other marketplaces.

![Add Stats](/images/blog/metadata-configurator/add-stats.png)

The Unlock team is excited to bring you more no-code tools to manage your NFT memberships. We are dedicated to improving the user experience to onboard more non-technical users.

## What if I find an issue or bug in the metadata configurator?

Please open an issue on Github or tell us in Discord and we’ll fix it as soon as possible.


Configure metadata for your NFT memberships, passes, tickets, and more from the Unlock Dashboard without programming.

A Brand New Metadata Configurator

<img src="/images/blog/metadata-configurator/main.gif" alt="metadata configurator video">
Most creators want to customize the attributes and add features to their NFTs. These features show up on NFT marketplaces such as OpenSea. Until now, they had to customize and manage the metadata on their own and update it on their own. It required coding and dealing with scripts. It wasn’t user friendly and added friction to working with Unlock.
To simplify this process, we are launching a no-code metadata configurator. With it, creators can add attributes such as properties, levels, stats, and other metadata to their NFT right from the Unlock Dashboard. This new feature also provides custom presets for ticketing and adding creator content such as YouTube videos, website, and animations.
<h2>How to start</h2>
On the lock management page, you can open the metadata configurator by clicking on the <code>Edit NFT Properties</code> button. This will only be visible for lock manager.
<img src="/images/blog/metadata-configurator/lock-page.png" alt="lock manage page">
The configurator is split into multiple sections. Each section is collapsible from the UI.
<h3>Basic details</h3>
The basic details section contains fields such as name, description, and the external URL for your NFT memberships.
<img src="/images/blog/metadata-configurator/basic.png" alt="Basics">
<h3>Event ticketing</h3>
The event ticketing section allows event organizers to set up custom data for their tickets. Any ticket metadata changed here will show up as attributes on OpenSea and other marketplaces. This ticket data is also used by Unlock to generate a QR code ticket for NFTs and power the verification experience.
<img src="/images/blog/metadata-configurator/ticket.png" alt="Ticket">
<h4>Preview</h4>
As you are making edits, you can click on the Preview Ticket button to see what your ticket would actually look like. All fields are updated in real-time to reflect changes.
<img src="/images/blog/metadata-configurator/preview-ticket.png" alt="Preview Ticket">
<h3>Advanced</h3>
Creators with a YouTube channel or a blog can use this section to display their videos and blog posts in the main preview box on OpenSea and other marketplaces. A user will be able to go to OpenSea and watch the video directly on your NFT page.
<img src="/images/blog/metadata-configurator/advanced.png" alt="Advanced">
<h3>Custom Properties</h3>
You can add custom properties, levels, and stats to your NFT to truly highlight the unique characteristics of your NFTs.
Please note that each item will be displayed slightly differently on OpenSea and other marketplaces. We provide a preview of how they will be displayed but it is not a 1-1 representation.
<img src="/images/blog/metadata-configurator/custom.png" alt="Custom">
<h4>Add Properties</h4>
You can open the Add Property modal using the Add button inside the property section. On Add Property modal, you can add or remove existing properties. Each property has a trait type and value.
<img src="/images/blog/metadata-configurator/add-stats.png" alt="Add Properties">
<h4>Add Levels</h4>
Each level has a trait type, value, and max value. The value and max value are used to display a progress indicator on OpenSea and other marketplaces.
<img src="/images/blog/metadata-configurator/add-levels.png" alt="Add Levels">
<h4>Add Stats</h4>
Stats are the same as levels, but won't be displayed as a progress indicator on OpenSea and other marketplaces.
<img src="/images/blog/metadata-configurator/add-stats.png" alt="Add Stats">
The Unlock team is excited to bring you more no-code tools to manage your NFT memberships. We are dedicated to improving the user experience to onboard more non-technical users.
<h2>What if I find an issue or bug in the metadata configurator?</h2>
Please open an issue on Github or tell us in Discord and we’ll fix it as soon as possible.


The original Unlock Protocol UDT Grants program was launched in 2021 with a goal to decentralize governance of Unlock Protocol, expand the number of [integrations](https://unlock-protocol.com/guides/category/plugins/) across the Unlock ecosystem, and increase the number of applications built with Unlock.

We’ve taken the learnings from this last year, along with our mission to continue to decentralize at scale, and made significant improvements to the grants program, which we hope will mean the next year is an even bigger success! Here’s what’s new.

### Streamlining the grant process and adding new capabilities

For the revamped grants program, we’ve partnered with [Wonderverse](https://app.wonderverse.xyz/organization/unlock/boards?entity=task), a DAO tool for collaboration and organization. Adding a decentralized tool opened up the opportunity to improve workflow and communication across the Unlock grants process. Let’s take a look how!

When a prospective grantee submits their grant application, the Unlock grants committee reviews their submission. We’ve streamlined the grant review process and implemented it via Wonderverse. This should reduce the time it takes from application to committee decision, with a target of returning a decision to the grant applicant within two weeks of their submission.

For grant applications that have been accepted and their milestones have been met, we now have the ability to make UDT grant awards directly from this same integrated system. This means we’ll also be able to speed up the time it takes to distribute grant rewards, getting UDT into the hands of grantees sooner!

I’m also excited to say that it means we now have the capability and capacity to create individual grantee workspaces where we can more closely communicate, educate and support our grantees. The goal is less friction for grantees to get what they need to be successful. This should lead to shorter launch timelines and higher-quality end products.

### Improved guides & handbooks

We’ve updated all of our guides and handbooks for grantees and published them in our
[docs](https://docs.unlock-protocol.com/governance/grants-bounties/). This should improve the understanding of how the grants program works for those interested in
[applying](https://docs.unlock-protocol.com/governance/grants-bounties/udt-grantee-handbook#submitting-an-application).

In addition, our new processes should make adding new [grant committee](https://docs.unlock-protocol.com/governance/grants-bounties/grant-committee-applicant-guide)
members much easier. This will enable Unlock to scale the program as the ecosystem grows.

Using the experience gained from the over 100 grant applications we received to date, we sought to increase the impact of the projects we give grants to and have made improvements to the
[grant review](https://docs.unlock-protocol.com/governance/grants-bounties/grant-review-guide) guidance for the committee.

### What’s next?

We’re thrilled so far with all of these improvements and we’re confident this next season of grants will be even more effective at increasing network volume and adding to the credibility and visibility of Unlock Protocol. On a quarterly basis, the grants committee will review the progress of the program and make proposals to the community for iterative improvements, if needed. This will accelerate the success of the program while maintaining our commitment to decentralization.

👉 Interested in building with us? Fill out an [application](https://docs.unlock-protocol.com/governance/grants-bounties/udt-grantee-handbook#submitting-an-application) for one of grants now!

### Looking back at the last year: Unlock Protocol grant success stories

Over the past year, the grants program has had success spawning work in areas of plugins and integrations, education, showcases, events, and platform subscriptions. Some of the highlights include:

**Integrations & Plugins**

- [Guild.xyz](https://unlock-protocol.com/guides/guild-xyz/)
- [Unity Game Engine](https://github.com/thehen/unlock-unity-package)
- [Monetized](https://unlock-protocol.com/guides/how-to-token-gate-notion/) (Notion)
- [Collab.Land](https://unlock-protocol.com/guides/discord-with-collab-land/)
- [Decentraland](https://unlock-protocol.com/blog/decentraland)
- [Firebase](https://unlock-protocol.com/blog/firebase-integration)
- [Discourse](https://unlock-protocol.com/blog/discourse-plugin)
- [Drupal](https://www.drupal.org/project/unlock)

**Built with Unlock**

- [Tales of Elatora](https://unlock-protocol.com/blog/talesofelatora)
- [Content Rooms](https://contentrooms.com/)
- [Bonsai.so](https://bonsai.so/)
- [Dinner DAO](https://unlock-protocol.com/blog/dinnerdao)
- [Unfurl](https://unlock-protocol.com/blog/unfurl-connect)

**Events**

- [ETHAnglia](https://ethanglia.org/)

**Education**

- [Web3Academy](https://w3academy.io/)
- [dProgramming University](https://dprogramminguniversity.com/courses/unlock-protocol-101/)
- [Unlock Showcase](https://www.unlockshowcase.com/)

With the upgraded grants program, we can’t wait to see what the community creates next! You can fill out a grant application here!


Improvements go live to streamline processes and accelerate growth for the Unlock ecosystem.

Improvements go live to streamline processes and accelerate growth for the Unlock ecosystem

Unlock Announces Grants Program Upgrade

The original Unlock Protocol UDT Grants program was launched in 2021 with a goal to decentralize governance of Unlock Protocol, expand the number of <a href="https://unlock-protocol.com/guides/category/plugins/">integrations</a> across the Unlock ecosystem, and increase the number of applications built with Unlock.
We’ve taken the learnings from this last year, along with our mission to continue to decentralize at scale, and made significant improvements to the grants program, which we hope will mean the next year is an even bigger success! Here’s what’s new.
<h3>Streamlining the grant process and adding new capabilities</h3>
For the revamped grants program, we’ve partnered with <a href="https://app.wonderverse.xyz/organization/unlock/boards?entity=task">Wonderverse</a>, a DAO tool for collaboration and organization. Adding a decentralized tool opened up the opportunity to improve workflow and communication across the Unlock grants process. Let’s take a look how!
When a prospective grantee submits their grant application, the Unlock grants committee reviews their submission. We’ve streamlined the grant review process and implemented it via Wonderverse. This should reduce the time it takes from application to committee decision, with a target of returning a decision to the grant applicant within two weeks of their submission.
For grant applications that have been accepted and their milestones have been met, we now have the ability to make UDT grant awards directly from this same integrated system. This means we’ll also be able to speed up the time it takes to distribute grant rewards, getting UDT into the hands of grantees sooner!
I’m also excited to say that it means we now have the capability and capacity to create individual grantee workspaces where we can more closely communicate, educate and support our grantees. The goal is less friction for grantees to get what they need to be successful. This should lead to shorter launch timelines and higher-quality end products.
<h3>Improved guides &#x26; handbooks</h3>
We’ve updated all of our guides and handbooks for grantees and published them in our
<a href="https://docs.unlock-protocol.com/governance/grants-bounties/">docs</a>. This should improve the understanding of how the grants program works for those interested in
<a href="https://docs.unlock-protocol.com/governance/grants-bounties/udt-grantee-handbook#submitting-an-application">applying</a>.
In addition, our new processes should make adding new <a href="https://docs.unlock-protocol.com/governance/grants-bounties/grant-committee-applicant-guide">grant committee</a>
members much easier. This will enable Unlock to scale the program as the ecosystem grows.
Using the experience gained from the over 100 grant applications we received to date, we sought to increase the impact of the projects we give grants to and have made improvements to the
<a href="https://docs.unlock-protocol.com/governance/grants-bounties/grant-review-guide">grant review</a> guidance for the committee.
<h3>What’s next?</h3>
We’re thrilled so far with all of these improvements and we’re confident this next season of grants will be even more effective at increasing network volume and adding to the credibility and visibility of Unlock Protocol. On a quarterly basis, the grants committee will review the progress of the program and make proposals to the community for iterative improvements, if needed. This will accelerate the success of the program while maintaining our commitment to decentralization.
👉 Interested in building with us? Fill out an <a href="https://docs.unlock-protocol.com/governance/grants-bounties/udt-grantee-handbook#submitting-an-application">application</a> for one of grants now!
<h3>Looking back at the last year: Unlock Protocol grant success stories</h3>
Over the past year, the grants program has had success spawning work in areas of plugins and integrations, education, showcases, events, and platform subscriptions. Some of the highlights include:
Integrations &#x26; Plugins
<ul>
<li><a href="https://unlock-protocol.com/guides/guild-xyz/">Guild.xyz</a></li>
<li><a href="https://github.com/thehen/unlock-unity-package">Unity Game Engine</a></li>
<li><a href="https://unlock-protocol.com/guides/how-to-token-gate-notion/">Monetized</a> (Notion)</li>
<li><a href="https://unlock-protocol.com/guides/discord-with-collab-land/">Collab.Land</a></li>
<li><a href="https://unlock-protocol.com/blog/decentraland">Decentraland</a></li>
<li><a href="https://unlock-protocol.com/blog/firebase-integration">Firebase</a></li>
<li><a href="https://unlock-protocol.com/blog/discourse-plugin">Discourse</a></li>
<li><a href="https://www.drupal.org/project/unlock">Drupal</a></li>
</ul>
Built with Unlock
<ul>
<li><a href="https://unlock-protocol.com/blog/talesofelatora">Tales of Elatora</a></li>
<li><a href="https://contentrooms.com/">Content Rooms</a></li>
<li><a href="https://bonsai.so/">Bonsai.so</a></li>
<li><a href="https://unlock-protocol.com/blog/dinnerdao">Dinner DAO</a></li>
<li><a href="https://unlock-protocol.com/blog/unfurl-connect">Unfurl</a></li>
</ul>
Events
<ul>
<li><a href="https://ethanglia.org/">ETHAnglia</a></li>
</ul>
Education
<ul>
<li><a href="https://w3academy.io/">Web3Academy</a></li>
<li><a href="https://dprogramminguniversity.com/courses/unlock-protocol-101/">dProgramming University</a></li>
<li><a href="https://www.unlockshowcase.com/">Unlock Showcase</a></li>
</ul>
With the upgraded grants program, we can’t wait to see what the community creates next! You can fill out a grant application here!


Creating a compelling checkout flow for online purchases is a thorny problem. Every creator who is offering memberships, ticketing, or other experiences to their community has a wide variety of options to consider on exactly what required information may be needed from each purchaser. When you add the new experiences of web3 into the mix, checkout flows for creating or minting can get very sophisticated, very quickly, and can be very difficult to configure.

To help improve the experience of creators who are building checkout experiences in web3, Unlock has developed a Checkout Builder that provides a no-code way to build and customize a checkout experience.

The Checkout Builder greatly speeds and simplifies the process of creating checkout flows by applying no-code principles to a process that until now required technical configuration to develop checkout flows.

Let's go through step-by-step and look at the new capabilities Locksmiths have available to them to build checkout experiences for minting membership NFTs.

## Checkout Builder overview

You can access the Checkout Builder page from your lock page by clicking the "Generate URL” button, or by going directly to this URL: [https://app.unlock-protocol.com/locks/checkout-url](https://app.unlock-protocol.com/locks/checkout-url).

![Checkout Builder Link](/images/blog/checkout-builder-release/checkout-overview-1.png)

On the Checkout Builder page, we can see on the left side the preview of what your checkout experience will look like. On the right side of the page there is a form with the information you can edit to configure the experience.

![Checkout Page Link](/images/blog/checkout-builder-release/checkout-overview-2.png)

Edits made on the right side of the page will automatically update the preview on the left and give you a real-time overview of the final result.

For every field, there is also a description that provides more context about the related field.

The form to customize the checkout has 2 sections, each on its own tab:

- `Configuration`: Where we can find general configuration and setup
- `Locks`: Where we can add locks and customize them in more detail

Let’s create a customized checkout experience and generate a checkout URL that we can share!

## Headers and additional behavior

In the `Configuration` tab, we can set all the basic details about the lock. In the following example, we set the title to `Demo x Panda` and we can see it reflect on the preview. We can also set a custom icon.

In order to generate a checkout URL, we need to add one or more locks. To do this, we can switch to the `Locks` tab.

![Header Checkout](/images/blog/checkout-builder-release/header-checkout.gif)

## Add locks

To add locks, the first thing we need to do is select a `Network` and the `Lock` we want to add.

The `Lock` dropdown will automatically show the list of our locks for every network.

![Add Lock Header](/images/blog/checkout-builder-release/add-lock.png)

![Add Lock Selection](/images/blog/checkout-builder-release/add-lock-1.png)

When the lock is selected, we can see it displayed in real-time on the preview.

![Lock List](/images/blog/checkout-builder-release/lock-list.png)

As described in the previous step, we can follow the same process in order to add additional locks to our checkout page, if needed.

### Detailed membership configuration

Our membership may have a number of traits that we’ll want to represent in the smart contract. Let’s take scenario:

_"We need a Lock that sets our membership to renew 2 times, sets a maximum number of five memberships an individual user can purchase in a single wallet, and requires an email address so we can communicate with the member via email.”_

The above items are configured in the `Settings` section of the Checkout Builder:

![Lock List](/images/blog/checkout-builder-release/settings.png)

And finally, when the lock is added with the `Settings`, we can see `second lock demo` now contains all the details we added.

![Lock Settings](/images/blog/checkout-builder-release/locks-list-multiple.png)

## Removing a lock from the checkout

A lock can be removed from the checkout experience by clicking the cross icon on the lock list.

![Remove Lock Overview](/images/blog/checkout-builder-release/remove-lock.png)

![Remove Lock GIF](/images/blog/checkout-builder-release/remove-lock-animation.gif)

## Collecting metadata

When setting up a membership experience, there is often information about your members (”metadata”) that is required to communicate with them (e.g. address), reward them (e.g. t-shirt size), and otherwise have a richer understanding of who a member is.

When collecting metadata during the checkout flow, you can set metadata items to collect at checkout time by clicking `Add metadata` in the Checkout Builder.

When `Add metadata` is enabled, a form where you can add detail for the metadata will be displayed. For each item of metadata, a number of fields are required.

- `name`: the name of the field that's shown as a label
- `default value`: default value of the field
- `type`: type of the field
- `required`: specify if the field is required when true
- `placeholder`: the placeholder that's shown in the input type
- `public`: if this item of metadata should be visible to everyone

### Add metadata

![Add Metadata](/images/blog/checkout-builder-release/metadata.png)

### Metadata on preview

![Metadata Preview](/images/blog/checkout-builder-release/metadata-preview.png)

## Copy and share!

That's all! You have now configured a checkout flow that can be shared with your prospective members. You can now copy the generated URL and share it to your community on your website, via social media, through email, or by any other method you like.

![Checkout Builder Demo Animation](/images/blog/checkout-builder-release/copy-link-builder.gif)

## One more thing: Developers can download the JSON configuration for a checkout

While the above steps are especially helpful for creators who are creating memberships for their community, the Checkout Builder can be a huge time-saver for developers as well. If you are developing on top of Unlock Protocol and need to integrate a checkout configuration into your custom code, you can configure the checkout experience using the Checkout Builder and then download a fully-configured JSON file to [configure the Paywall](https://docs.unlock-protocol.com/tools/paywall/locking-page/#configure-the-paywall) in your application.

![Download JSON](/images/blog/checkout-builder-release//download-json.png)

**What if I find an issue or bug in the new checkout builder?**

Please open an issue on Github or tell us in Discord and we'll fix it ASAP.


Unlock launches a checkout builder to easily customize your checkout experience — no programming expertise needed.

Unlock Unveils No-Code Membership NFT Checkout Builder

Creating a compelling checkout flow for online purchases is a thorny problem. Every creator who is offering memberships, ticketing, or other experiences to their community has a wide variety of options to consider on exactly what required information may be needed from each purchaser. When you add the new experiences of web3 into the mix, checkout flows for creating or minting can get very sophisticated, very quickly, and can be very difficult to configure.
To help improve the experience of creators who are building checkout experiences in web3, Unlock has developed a Checkout Builder that provides a no-code way to build and customize a checkout experience.
The Checkout Builder greatly speeds and simplifies the process of creating checkout flows by applying no-code principles to a process that until now required technical configuration to develop checkout flows.
Let's go through step-by-step and look at the new capabilities Locksmiths have available to them to build checkout experiences for minting membership NFTs.
<h2>Checkout Builder overview</h2>
You can access the Checkout Builder page from your lock page by clicking the "Generate URL” button, or by going directly to this URL: <a href="https://app.unlock-protocol.com/locks/checkout-url">https://app.unlock-protocol.com/locks/checkout-url</a>.
<img src="/images/blog/checkout-builder-release/checkout-overview-1.png" alt="Checkout Builder Link">
On the Checkout Builder page, we can see on the left side the preview of what your checkout experience will look like. On the right side of the page there is a form with the information you can edit to configure the experience.
<img src="/images/blog/checkout-builder-release/checkout-overview-2.png" alt="Checkout Page Link">
Edits made on the right side of the page will automatically update the preview on the left and give you a real-time overview of the final result.
For every field, there is also a description that provides more context about the related field.
The form to customize the checkout has 2 sections, each on its own tab:
<ul>
<li><code>Configuration</code>: Where we can find general configuration and setup</li>
<li><code>Locks</code>: Where we can add locks and customize them in more detail</li>
</ul>
Let’s create a customized checkout experience and generate a checkout URL that we can share!
<h2>Headers and additional behavior</h2>
In the <code>Configuration</code> tab, we can set all the basic details about the lock. In the following example, we set the title to <code>Demo x Panda</code> and we can see it reflect on the preview. We can also set a custom icon.
In order to generate a checkout URL, we need to add one or more locks. To do this, we can switch to the <code>Locks</code> tab.
<img src="/images/blog/checkout-builder-release/header-checkout.gif" alt="Header Checkout">
<h2>Add locks</h2>
To add locks, the first thing we need to do is select a <code>Network</code> and the <code>Lock</code> we want to add.
The <code>Lock</code> dropdown will automatically show the list of our locks for every network.
<img src="/images/blog/checkout-builder-release/add-lock.png" alt="Add Lock Header">
<img src="/images/blog/checkout-builder-release/add-lock-1.png" alt="Add Lock Selection">
When the lock is selected, we can see it displayed in real-time on the preview.
<img src="/images/blog/checkout-builder-release/lock-list.png" alt="Lock List">
As described in the previous step, we can follow the same process in order to add additional locks to our checkout page, if needed.
<h3>Detailed membership configuration</h3>
Our membership may have a number of traits that we’ll want to represent in the smart contract. Let’s take scenario:
"We need a Lock that sets our membership to renew 2 times, sets a maximum number of five memberships an individual user can purchase in a single wallet, and requires an email address so we can communicate with the member via email.”
The above items are configured in the <code>Settings</code> section of the Checkout Builder:
<img src="/images/blog/checkout-builder-release/settings.png" alt="Lock List">
And finally, when the lock is added with the <code>Settings</code>, we can see <code>second lock demo</code> now contains all the details we added.
<img src="/images/blog/checkout-builder-release/locks-list-multiple.png" alt="Lock Settings">
<h2>Removing a lock from the checkout</h2>
A lock can be removed from the checkout experience by clicking the cross icon on the lock list.
<img src="/images/blog/checkout-builder-release/remove-lock.png" alt="Remove Lock Overview">
<img src="/images/blog/checkout-builder-release/remove-lock-animation.gif" alt="Remove Lock GIF">
<h2>Collecting metadata</h2>
When setting up a membership experience, there is often information about your members (”metadata”) that is required to communicate with them (e.g. address), reward them (e.g. t-shirt size), and otherwise have a richer understanding of who a member is.
When collecting metadata during the checkout flow, you can set metadata items to collect at checkout time by clicking <code>Add metadata</code> in the Checkout Builder.
When <code>Add metadata</code> is enabled, a form where you can add detail for the metadata will be displayed. For each item of metadata, a number of fields are required.
<ul>
<li><code>name</code>: the name of the field that's shown as a label</li>
<li><code>default value</code>: default value of the field</li>
<li><code>type</code>: type of the field</li>
<li><code>required</code>: specify if the field is required when true</li>
<li><code>placeholder</code>: the placeholder that's shown in the input type</li>
<li><code>public</code>: if this item of metadata should be visible to everyone</li>
</ul>
<h3>Add metadata</h3>
<img src="/images/blog/checkout-builder-release/metadata.png" alt="Add Metadata">
<h3>Metadata on preview</h3>
<img src="/images/blog/checkout-builder-release/metadata-preview.png" alt="Metadata Preview">
<h2>Copy and share!</h2>
That's all! You have now configured a checkout flow that can be shared with your prospective members. You can now copy the generated URL and share it to your community on your website, via social media, through email, or by any other method you like.
<img src="/images/blog/checkout-builder-release/copy-link-builder.gif" alt="Checkout Builder Demo Animation">
<h2>One more thing: Developers can download the JSON configuration for a checkout</h2>
While the above steps are especially helpful for creators who are creating memberships for their community, the Checkout Builder can be a huge time-saver for developers as well. If you are developing on top of Unlock Protocol and need to integrate a checkout configuration into your custom code, you can configure the checkout experience using the Checkout Builder and then download a fully-configured JSON file to <a href="https://docs.unlock-protocol.com/tools/paywall/locking-page/#configure-the-paywall">configure the Paywall</a> in your application.
<img src="/images/blog/checkout-builder-release//download-json.png" alt="Download JSON">
What if I find an issue or bug in the new checkout builder?
Please open an issue on Github or tell us in Discord and we'll fix it ASAP.


We are pleased to announce that a new version of the Unlock protocol template contract is now available.

### Whats is the PublicLock template?

In the Unlock Protocol, a “lock” is a standalone smart contract that can issue (mint) and manage membership NFTs (”keys”). Once deployed, each lock exists as an entirely separate and independent contract. Even if the protocol changes, lock contracts remain as they were when created. Since version 10, a lock can be [upgraded](./upgradeable-patterns) to a newer version which may change some of the features, without affecting the existing data.

Each new lock created is a “copy” of the main template contract, called `PublicLock`. The template contract defines the inner workings and the logic (functions, variables, etc.) of each new lock contract that is deployed. The template evolves as new use cases and features are added to the protocol.

### What changed in v12?

The version 12 contract consolidates the new features and approaches that were introduced in versions 10 and 11. The various features to set metadata (name, symbol and tokenURIs) have been regrouped into a single function called `setLockMetadata`. The configuration for a key’s default duration and available quantity (both per user and in aggregate) have also been grouped in a single `updateLockConfig` function. Additionally, several events are now fired when changes to the contract state are made — so those events are now easier to track using our [new subgraph](./subgraph-v2). Also, version 12 contains bug fixes related to locks with cancelled keys.

You can see a full list of related [issues and pull requests](https://github.com/unlock-protocol/unlock/issues?q=+label%3A%22publicLock+v12%22+) here.

### How to deploy or upgrade an existing smart contract

The version 12 template has been published and will soon be available as the default version for all new locks. Meanwhile, you can upgrade an existing version 11 lock by using the `upgradeLock` function from the Unlock factory contract. (To determine the current version of your lock, please check the `publicLockVersion` of your lock in your block explorer.)

As always, if you have any questions, please reach out to us on Discord and we’ll be happy to help you with the upgrade!

**Implementation note:** Version upgrades are only permitted to bump a single digit at a time. For example, if you have a v10 lock, you will have to upgrade first to v11, and then to v12.


New capabilities and improvements come to Unlock’s template smart contract for managing memberships.

Unlock Releases PublicLock v12 Smart Contract

We are pleased to announce that a new version of the Unlock protocol template contract is now available.
<h3>Whats is the PublicLock template?</h3>
In the Unlock Protocol, a “lock” is a standalone smart contract that can issue (mint) and manage membership NFTs (”keys”). Once deployed, each lock exists as an entirely separate and independent contract. Even if the protocol changes, lock contracts remain as they were when created. Since version 10, a lock can be <a href="./upgradeable-patterns">upgraded</a> to a newer version which may change some of the features, without affecting the existing data.
Each new lock created is a “copy” of the main template contract, called <code>PublicLock</code>. The template contract defines the inner workings and the logic (functions, variables, etc.) of each new lock contract that is deployed. The template evolves as new use cases and features are added to the protocol.
<h3>What changed in v12?</h3>
The version 12 contract consolidates the new features and approaches that were introduced in versions 10 and 11. The various features to set metadata (name, symbol and tokenURIs) have been regrouped into a single function called <code>setLockMetadata</code>. The configuration for a key’s default duration and available quantity (both per user and in aggregate) have also been grouped in a single <code>updateLockConfig</code> function. Additionally, several events are now fired when changes to the contract state are made — so those events are now easier to track using our <a href="./subgraph-v2">new subgraph</a>. Also, version 12 contains bug fixes related to locks with cancelled keys.
You can see a full list of related <a href="https://github.com/unlock-protocol/unlock/issues?q=+label%3A%22publicLock+v12%22+">issues and pull requests</a> here.
<h3>How to deploy or upgrade an existing smart contract</h3>
The version 12 template has been published and will soon be available as the default version for all new locks. Meanwhile, you can upgrade an existing version 11 lock by using the <code>upgradeLock</code> function from the Unlock factory contract. (To determine the current version of your lock, please check the <code>publicLockVersion</code> of your lock in your block explorer.)
As always, if you have any questions, please reach out to us on Discord and we’ll be happy to help you with the upgrade!
Implementation note: Version upgrades are only permitted to bump a single digit at a time. For example, if you have a v10 lock, you will have to upgrade first to v11, and then to v12.


It was **1971** when Ray Tomlinson invented and developed electronic mail, as we know it today, by creating ARPANET's networked email system. It is one of the Internet’s oldest and (still!) most widely-used applications, with four [billion daily emails](https://blog.hubspot.com/marketing/email-marketing-stats)! Email predates the web, and predates the blockchain era. Over the years, it has seen many competing platforms come and go, but, for better or worse, email has remained the most frequently-used communication tool because it relies on open and decentralized protocols like [POP](https://en.wikipedia.org/wiki/Post_Office_Protocol), [SMTP](https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol) and [IMAP](https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol).

![Email required](/images/blog/email-required/email-required-share.png)

As of now, web3 still does not have a widely-used alternative messaging protocol, which means that email is the best option for creators to reach to their members and communities.

At Unlock, when using our [checkout flow](https://docs.unlock-protocol.com/tools/checkout/) (which is [completely optional](https://docs.unlock-protocol.com/getting-started/unlock-without-frontend)), creators can choose to require purchasers to enter their email addresses at purchase (mint) time. This has been possible for a long time through the use of our [“metadata” collection mechanism](https://docs.unlock-protocol.com/tools/checkout/collecting-metadata), and we now have simplified this experience for creators by making email address collection an option when building a checkout URL by using `emailRequired` in the lock options.

![Email required](/images/blog/email-required/collecting-email.png)

You can test it out by getting a free Unlock community membership, if you don't already have one! [Click here](https://app.unlock-protocol.com/checkout?redirectUri=https%3A%2F%2Funlock-protocol.com%2Fblog%2Femail-required&paywallConfig=%7B%22network%22%3A1%2C%22pessimistic%22%3Atrue%2C%22locks%22%3A%7B%220xCE62D71c768aeD7EA034c72a1bc4CF58830D9894%22%3A%7B%22name%22%3A%22Unlock%20Community%22%2C%22network%22%3A100%2C%22emailRequired%22%3Atrue%7D%7D%2C%22icon%22%3A%22https%3A%2F%2Fraw.githubusercontent.com%2Funlock-protocol%2Funlock%2Fmaster%2Fdesign%2Fbrand%2F1808-Unlock-Identity_Unlock-WordMark.svg%22%2C%22callToAction%22%3A%7B%22default%22%3A%22Get%20an%20Unlock%20membership%20to%20access%20our%20Discord%2C%20blog%20comments%20and%20more!%20No%20xDAI%20to%20pay%20for%20gas%3F%20Click%20the%20Claim%20button.%22%7D%7D)!

Once collected, the email address is tied to the NFT owner address, and is only accessible by the lock manager through the Unlock Dashboard or through our Locksmith API.

One of the common questions that creators have in the web3 space is “how do I stay connected and engaged with my members and NFT-holders?” We know that this new feature can help!

**Implementation note:** Of course, since the email address is tied to the NFT owner’s wallet address, if the NFT is transferred, the email address is not accessible anymore.


Lock managers can configure Unlock's checkout UI to collect their members' email addresses.

Now there's a way to keep in touch with your members!

New Feature! Easy Email Collection for Creators

It was 1971 when Ray Tomlinson invented and developed electronic mail, as we know it today, by creating ARPANET's networked email system. It is one of the Internet’s oldest and (still!) most widely-used applications, with four <a href="https://blog.hubspot.com/marketing/email-marketing-stats">billion daily emails</a>! Email predates the web, and predates the blockchain era. Over the years, it has seen many competing platforms come and go, but, for better or worse, email has remained the most frequently-used communication tool because it relies on open and decentralized protocols like <a href="https://en.wikipedia.org/wiki/Post_Office_Protocol">POP</a>, <a href="https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol">SMTP</a> and <a href="https://en.wikipedia.org/wiki/Internet_Message_Access_Protocol">IMAP</a>.
<img src="/images/blog/email-required/email-required-share.png" alt="Email required">
As of now, web3 still does not have a widely-used alternative messaging protocol, which means that email is the best option for creators to reach to their members and communities.
At Unlock, when using our <a href="https://docs.unlock-protocol.com/tools/checkout/">checkout flow</a> (which is <a href="https://docs.unlock-protocol.com/getting-started/unlock-without-frontend">completely optional</a>), creators can choose to require purchasers to enter their email addresses at purchase (mint) time. This has been possible for a long time through the use of our <a href="https://docs.unlock-protocol.com/tools/checkout/collecting-metadata">“metadata” collection mechanism</a>, and we now have simplified this experience for creators by making email address collection an option when building a checkout URL by using <code>emailRequired</code> in the lock options.
<img src="/images/blog/email-required/collecting-email.png" alt="Email required">
You can test it out by getting a free Unlock community membership, if you don't already have one! <a href="https://app.unlock-protocol.com/checkout?redirectUri=https%3A%2F%2Funlock-protocol.com%2Fblog%2Femail-required&#x26;paywallConfig=%7B%22network%22%3A1%2C%22pessimistic%22%3Atrue%2C%22locks%22%3A%7B%220xCE62D71c768aeD7EA034c72a1bc4CF58830D9894%22%3A%7B%22name%22%3A%22Unlock%20Community%22%2C%22network%22%3A100%2C%22emailRequired%22%3Atrue%7D%7D%2C%22icon%22%3A%22https%3A%2F%2Fraw.githubusercontent.com%2Funlock-protocol%2Funlock%2Fmaster%2Fdesign%2Fbrand%2F1808-Unlock-Identity_Unlock-WordMark.svg%22%2C%22callToAction%22%3A%7B%22default%22%3A%22Get%20an%20Unlock%20membership%20to%20access%20our%20Discord%2C%20blog%20comments%20and%20more!%20No%20xDAI%20to%20pay%20for%20gas%3F%20Click%20the%20Claim%20button.%22%7D%7D">Click here</a>!
Once collected, the email address is tied to the NFT owner address, and is only accessible by the lock manager through the Unlock Dashboard or through our Locksmith API.
One of the common questions that creators have in the web3 space is “how do I stay connected and engaged with my members and NFT-holders?” We know that this new feature can help!
Implementation note: Of course, since the email address is tied to the NFT owner’s wallet address, if the NFT is transferred, the email address is not accessible anymore.


![CSV airdrop](/images/blog/unlock-csv-airdrop/main.png)

Many creators and event organizers want to airdrop NFTs in bulk. To make this easier, we’ve added the ability to upload a spreadsheet (CSV) containing recipients and metadata.

After you upload the spreadsheet, we will show you a list of addresses with the number of NFT keys to be airdropped to them. We automatically remove duplicates, invalid entries, resolve ENS names, and run validation before showing the members.

![Members](/images/blog/unlock-csv-airdrop/members.png)

If you want to store additional metadata, you can put it as a column and fill in the value, which will be automatically added. To make it public, `.public` suffix can also be added.

We’re excited to bring more no-code tools to lock managers so they can easily manage members!


Creators can now upload a spreadsheet of recipients and metadata to airdrop NFTs directly to multiple recipients.

Creators can now upload a spreadsheet of recipients and metadata to airdrop NFTs directly to multiple recipients

Unlock Dashboard Now Supports Airdropping NFTs in Bulk

<img src="/images/blog/unlock-csv-airdrop/main.png" alt="CSV airdrop">
Many creators and event organizers want to airdrop NFTs in bulk. To make this easier, we’ve added the ability to upload a spreadsheet (CSV) containing recipients and metadata.
After you upload the spreadsheet, we will show you a list of addresses with the number of NFT keys to be airdropped to them. We automatically remove duplicates, invalid entries, resolve ENS names, and run validation before showing the members.
<img src="/images/blog/unlock-csv-airdrop/members.png" alt="Members">
If you want to store additional metadata, you can put it as a column and fill in the value, which will be automatically added. To make it public, <code>.public</code> suffix can also be added.
We’re excited to bring more no-code tools to lock managers so they can easily manage members!