
![](/images/blog/unlock-authentication-modal/main.png)

We're excited to announce the addition of unlock authentication modal which can be used through the paywall library to login users without building your own login modal.

Take a look at the example below.

```typescript
import { Paywall } from '@unlock-protocol/paywall'
import { networks } from '@unlock-protocol/networks'

const paywall = new Paywall(networks)
// Now, you can utilize the provider for tasks such as signing messages and sending transactions.
const provider = paywall.getProvider()
await provider.connect() // This step will initiate the login modal
```

To delve deeper into integrating the provider seamlessly within your application using "wagmi", we have prepared a [comprehensive tutorial](https://docs.unlock-protocol.com/tutorials/front-end/paywall/provider/).

Stay tuned for more updates as we continue to enhance our authentication features and empower developers and users alike with seamless access to our application.


Developers can now integrate the Unlock authentication modal into their applications to enable users to login without building their own login modal.

🔒 Introducing Unlock Authentication Modal for Seamless User Login and Library Integration

<p><img src="/images/blog/unlock-authentication-modal/main.png" alt=""></p>
<p>We're excited to announce the addition of unlock authentication modal which can be used through the paywall library to login users without building your own login modal.</p>
<p>Take a look at the example below.</p>
<pre><code class="language-typescript">import { Paywall } from '@unlock-protocol/paywall'
import { networks } from '@unlock-protocol/networks'

const paywall = new Paywall(networks)
// Now, you can utilize the provider for tasks such as signing messages and sending transactions.
const provider = paywall.getProvider()
await provider.connect() // This step will initiate the login modal
</code></pre>
<p>To delve deeper into integrating the provider seamlessly within your application using "wagmi", we have prepared a <a href="https://docs.unlock-protocol.com/tutorials/front-end/paywall/provider/">comprehensive tutorial</a>.</p>
<p>Stay tuned for more updates as we continue to enhance our authentication features and empower developers and users alike with seamless access to our application.</p>



The Unlock Protocol has a unique feature that lets developers change the behavior of an Unlock [membership contract](https://docs.unlock-protocol.com/core-protocol/public-lock/) while still leveraging most of its logic. These additional pieces of functionality are accessed via “[hooks](https://docs.unlock-protocol.com/core-protocol/public-lock/hooks)”. One of the hooks is the [`onKeyPurchaseHook`](https://docs.unlock-protocol.com/core-protocol/public-lock/hooks#onkeypurchase-hook) and it is triggered when new members are purchasing a membership NFT.

One of the most frequent feature requests for Unlock has been the ability to restrict who can purchase a membership. Last year, we introduced a [CaptchaHook](https://github.com/unlock-protocol/captcha-hook) which requires users to go through a Recaptcha validation and prevents bots from being able to buy NFTs in bulk. We also introduced a hook to [require a password](https://unlock-protocol.com/blog/password-required-hook) when going through the checkout.

But we are still seeing demand for a more flexible approach, where a smart contract administrator (who is called a “lock manager” in the Unlock ecosystem) wants to only allow people in a specific allow-list, or people who own a certain amount of a specific token, or even users who have minted an NFT of a special kind to have access to mint or claim a membership.

Rather than build this complicated logic ourselves, we partnered with our friends at [Guild.xyz](https://guild.xyz) to build a general-purpose Guild Hook! With the Guild Hook, a lock manager can point to any Guild they created and Guilds are extremely flexible!

Let’s go ahead and create an example!

## Guild and Unlock Protocol integration using the Guild Hook

Let’s say I only want people who [follow Unlock on Twitter](https://twitter.com/UnlockProtocol) to be able to claim a membership [from this membership contract.](https://goerli.etherscan.io/address/0xd36695BDF1A17BC4B0aA318d02c60F6e108CB653)

1. First, I will go to [Guild.xyz](http://Guild.xyz) and create a Guild whose **requirement** is to follow Unlock on Twitter.

![Guild.xyz Requirements](/images/blog/guild-hook/requirements.png)

2. Then, once the [Guild has been created](https://guild.xyz/the-unlock-followers), I come back to the Unlock dashboard, go to the advanced settings for my lock, and select the Hooks section.

![Guild.xyz Settings](/images/blog/guild-hook/unlock-hook-settings.png)

3. I can then save the changes and my membership contract is now **hooked** to the Guild of the Unlock Protocol followers on Twitter!

Now the requirements are set, and there is one more step to go.

The last step is to build a checkout URL, [like this one](https://app.unlock-protocol.com/checkout?id=23d15cce-8423-4761-ba48-6dd5ab5a048c), through which users are prompted to join the Guild if they are not already members. Once someone is a member of the Guild, they can mint their NFT membership!

![Guild.xyz Settings](/images/blog/guild-hook/unlock-guild-checkout.png)

Like always, we’re excited to see what creators, conference organizers and others are doing with this! We also want to inspire developers to create more hooks that can change the behavior of the lock contract based on their own needs and requirements!


By leveraging a new kind of smart contract hook, you can easily create all kinds of allow-list on your lock using Guild.xyz.

Easily create all kinds of allow-list on your lock using Guild.xyz!

Guild.xyz hook

<p>The Unlock Protocol has a unique feature that lets developers change the behavior of an Unlock <a href="https://docs.unlock-protocol.com/core-protocol/public-lock/">membership contract</a> while still leveraging most of its logic. These additional pieces of functionality are accessed via “<a href="https://docs.unlock-protocol.com/core-protocol/public-lock/hooks">hooks</a>”. One of the hooks is the <a href="https://docs.unlock-protocol.com/core-protocol/public-lock/hooks#onkeypurchase-hook"><code>onKeyPurchaseHook</code></a> and it is triggered when new members are purchasing a membership NFT.</p>
<p>One of the most frequent feature requests for Unlock has been the ability to restrict who can purchase a membership. Last year, we introduced a <a href="https://github.com/unlock-protocol/captcha-hook">CaptchaHook</a> which requires users to go through a Recaptcha validation and prevents bots from being able to buy NFTs in bulk. We also introduced a hook to <a href="https://unlock-protocol.com/blog/password-required-hook">require a password</a> when going through the checkout.</p>
<p>But we are still seeing demand for a more flexible approach, where a smart contract administrator (who is called a “lock manager” in the Unlock ecosystem) wants to only allow people in a specific allow-list, or people who own a certain amount of a specific token, or even users who have minted an NFT of a special kind to have access to mint or claim a membership.</p>
<p>Rather than build this complicated logic ourselves, we partnered with our friends at <a href="https://guild.xyz">Guild.xyz</a> to build a general-purpose Guild Hook! With the Guild Hook, a lock manager can point to any Guild they created and Guilds are extremely flexible!</p>
<p>Let’s go ahead and create an example!</p>
<h2>Guild and Unlock Protocol integration using the Guild Hook</h2>
<p>Let’s say I only want people who <a href="https://twitter.com/UnlockProtocol">follow Unlock on Twitter</a> to be able to claim a membership <a href="https://goerli.etherscan.io/address/0xd36695BDF1A17BC4B0aA318d02c60F6e108CB653">from this membership contract.</a></p>
<ol>
<li>First, I will go to <a href="http://Guild.xyz">Guild.xyz</a> and create a Guild whose <strong>requirement</strong> is to follow Unlock on Twitter.</li>
</ol>
<p><img src="/images/blog/guild-hook/requirements.png" alt="Guild.xyz Requirements"></p>
<ol start="2">
<li>Then, once the <a href="https://guild.xyz/the-unlock-followers">Guild has been created</a>, I come back to the Unlock dashboard, go to the advanced settings for my lock, and select the Hooks section.</li>
</ol>
<p><img src="/images/blog/guild-hook/unlock-hook-settings.png" alt="Guild.xyz Settings"></p>
<ol start="3">
<li>I can then save the changes and my membership contract is now <strong>hooked</strong> to the Guild of the Unlock Protocol followers on Twitter!</li>
</ol>
<p>Now the requirements are set, and there is one more step to go.</p>
<p>The last step is to build a checkout URL, <a href="https://app.unlock-protocol.com/checkout?id=23d15cce-8423-4761-ba48-6dd5ab5a048c">like this one</a>, through which users are prompted to join the Guild if they are not already members. Once someone is a member of the Guild, they can mint their NFT membership!</p>
<p><img src="/images/blog/guild-hook/unlock-guild-checkout.png" alt="Guild.xyz Settings"></p>
<p>Like always, we’re excited to see what creators, conference organizers and others are doing with this! We also want to inspire developers to create more hooks that can change the behavior of the lock contract based on their own needs and requirements!</p>



![cross-chain-share.png](/images/blog/crosschain/cross-chain-share.png)

## What is cross-chain governance?

The Unlock Protocol moved its governance to a [DAO](https://docs.unlock-protocol.com/governance/unlock-dao) almost two years ago. The protocol has since grown and now supports more than 10 different chains, leading to more complex ways to enforce decisions taken by the community. When all the votes are happening on Ethereum mainnet, how can we make sure that all DAO decisions are reflected correctly across all of the chains where Unlock Protocol is supported? That’s why our team has been working a cross-chain governance toolkit, in order to maintain and upgrade the protocol in a decentralized and automated fashion.

## Life across multiple chains

Technology derived from the original Ethereum experiment has gained momentum and lead to a vast array of new chains being deployed, each with their own characteristics. Under the hood, many of these chains have added the ability to execute contract calls by following the original Ethereum Virtual Machine implementation (EVM). The EVM provides a blueprint and ensures compatibility of the code that can be deployed across different chains.

At Unlock Labs, we have long thought that we need to meet our community where they are, and that meant deploying the protocol on [multiple chains](https://docs.unlock-protocol.com/core-protocol/unlock/networks).

Our role is not to choose which chain/L2 on which developers choose to deploy their membership contracts — as an open protocol, that decision should be theirs, and that decision should be permissionless.

At the same time, it is also critical that the protocol acts the same across the board, regardless of what chain it is being run on.

## Why cross-chain governance?

While a simple upgrade or change in protocol settings on one network may require just a single call, living across 10+ disparate networks means that even a simple settings tweak quickly becomes quite a tedious process to manage and deploy. We decided to work towards the automation of a cross-chain solution for a number of reasons:

1. **Consistency**: We need to make sure that any change that happens somewhere is replicated everywhere, so the experience of using the protocol is consistent across chains.
2. **Reduce risk of deployment errors**: On each chain, the set of contracts are deployed at [different addresses](https://www.npmjs.com/package/@unlock-protocol/networks). To make all upgrades manually introduces the possibility of errors. Even if to err is human, we love to avoid it as much as we can.
3. **Transparency**: While changes in the protocol are [voted on in the Unlock DAO](https://unlock-protocol.com/guides/delegation/), the execution and enforcement of these changes is left entirely to human discretion. We pursue the goal of making Unlock a decentralised organization and therefore like to transfer that burden to auditable smart contracts.

## How it works: the Unlock Owner

Our design relies on a straightforward idea: the DAO on Ethereum mainnet is the authority that all contracts should listen to. When a proposal is executed, the DAO should send instructions across the bridge to all other instances of Unlock. To enable the cross-chain governance process, we have to pass contract calls and data across chains. For that, we rely on the [Connext Bridge](https://www.connext.network/).

A new contract called `UnlockOwner` acts as a relay in this process, receiving the calls from the DAO across the bridge (or directly on mainnet) and passing it down to the local Unlock contract. It has mainly two functions: 1) upgrade the Unlock contract (core of the protocol) and 2) change settings of the Unlock contract itself (e.g. add a new template or tweak a parameter).

In technical terms, `UnlockOwner` is deployed on each network. It owns (as in owner of an [Ownable contract](https://docs.openzeppelin.com/contracts/4.x/access-control#ownership-and-ownable)) both the Unlock contract instance and the ProxyAdmin (that controls the proxy upgrades).

![cross-chain-napkin.png](/images/blog/crosschain/cross-chain-napkin.png)

_Original sketch of how calls could circulate across the bridge and through Unlock Manager on multiple chains_

## Risks and safeguards

Automating the governance process facilitates the propagation of decisions. This also means a bad actor could introduce malicious actions that then spread faster to the entire protocol. We set up all relevant origin and destination checks within the contracts themselves, but we also took extra precautions.

To mitigate the risks of a protocol-wide attack, we set up two main tools:

1. **A safety delay**: Every contract call arriving from the DAO across the bridge will be quarantined for a duration of at least two days. That leaves some room to act if any malicious calls were to be sent. Note that this time period comes _after_ the delay introduced by the DAO itself. For that, we rely on [OpenZeppelin's Timelock contract](https://docs.openzeppelin.com/contracts/4.x/governance#timelock) that has been audited multiple times.
2. **Multisigs**: On each chain, a multisig owned by our team and trusted members of the Unlock community retains the ability to trigger actions through the `UnlockOwner` contract. We believe this is still a requirement at this stage as a safeguard. Performing a protocol-wide upgrade across chains is a radically new approach. As such processes of governance are maturing, we hope multisigs could become obsolete and we have built a way in the `UnlockOwner` to remove them. We believe this will happen in due time.

## Try it now !

As of today, the cross-chain governance process is already deployed on ETH Goerli and Polygon Mumbai testnets. We redeployed a DAO on Goerli (which acts as a "mainnet" for testnets) and are still testing how various calls behave and how our current approach could be improved.

We encourage you to check proposals on our [Unlock Test DAO](https://www.tally.xyz/gov/unlock-test-dao). Any feedback will be warmly welcome!

Below are the addresses of deployed test instances (nb. these may change over time as we redeploy the contracts).

### Goerli Contracts

- **Unlock:** [https://goerli.etherscan.io/address/0x7fA9F695856269E1415b2d373b35037159E2F94C](https://goerli.etherscan.io/address/0x7fA9F695856269E1415b2d373b35037159E2F94C)
- **UDT:** [https://goerli.etherscan.io/address/0xaB82D702A4e0cD165072C005dc504A21c019718F#readProxyContract](https://goerli.etherscan.io/address/0xaB82D702A4e0cD165072C005dc504A21c019718F#readProxyContract)
- **Gov:** [https://goerli.etherscan.io/address/0xDcDE260Df00ba86889e8B112DfBe1A4945B35CA9](https://goerli.etherscan.io/address/0xDcDE260Df00ba86889e8B112DfBe1A4945B35CA9)
- **Timelock:** [https://goerli.etherscan.io/address/0xD7477B7c0CdA4204Cf860e4c27486061b15a5AC3](https://goerli.etherscan.io/address/0xD7477B7c0CdA4204Cf860e4c27486061b15a5AC3)
- **Unlock Owner:** [https://goerli.etherscan.io/address/0x6E74DC46EbF2cDB75B72Ab1dCAe3C98c7E9d28a1](https://goerli.etherscan.io/address/0x6E74DC46EbF2cDB75B72Ab1dCAe3C98c7E9d28a1)

### Mumbai Contracts

- **Unlock:** [https://mumbai.polygonscan.com/address/0x8db6eE991C6C3CB2b6228b558c1b3D6EA474cB42#writeProxyContract](https://mumbai.polygonscan.com/address/0x8db6eE991C6C3CB2b6228b558c1b3D6EA474cB42#writeProxyContract)
- **Unlock Owner:** [https://mumbai.polygonscan.com/address/0xdc230F9A08918FaA5ae48B8E13647789A8B6dD46](https://mumbai.polygonscan.com/address/0x8db6eE991C6C3CB2b6228b558c1b3D6EA474cB42#writeProxyContract)

### Test DAO Dashboard

- **Tally:** [https://www.tally.xyz/gov/unlock-test-dao](https://www.tally.xyz/gov/unlock-test-dao)


This cross-chain governance design relies on a straightforward idea. The DAO on Ethereum mainnet is the authority that all contracts should listen to. When a proposal is executed, the DAO should send instructions, pass contract calls, and send data across a bridge to all other instances of the DAO on other chains.

How the Unlock DAO Implemented Cross-chain Governance

<p><img src="/images/blog/crosschain/cross-chain-share.png" alt="cross-chain-share.png"></p>
<h2>What is cross-chain governance?</h2>
<p>The Unlock Protocol moved its governance to a <a href="https://docs.unlock-protocol.com/governance/unlock-dao">DAO</a> almost two years ago. The protocol has since grown and now supports more than 10 different chains, leading to more complex ways to enforce decisions taken by the community. When all the votes are happening on Ethereum mainnet, how can we make sure that all DAO decisions are reflected correctly across all of the chains where Unlock Protocol is supported? That’s why our team has been working a cross-chain governance toolkit, in order to maintain and upgrade the protocol in a decentralized and automated fashion.</p>
<h2>Life across multiple chains</h2>
<p>Technology derived from the original Ethereum experiment has gained momentum and lead to a vast array of new chains being deployed, each with their own characteristics. Under the hood, many of these chains have added the ability to execute contract calls by following the original Ethereum Virtual Machine implementation (EVM). The EVM provides a blueprint and ensures compatibility of the code that can be deployed across different chains.</p>
<p>At Unlock Labs, we have long thought that we need to meet our community where they are, and that meant deploying the protocol on <a href="https://docs.unlock-protocol.com/core-protocol/unlock/networks">multiple chains</a>.</p>
<p>Our role is not to choose which chain/L2 on which developers choose to deploy their membership contracts — as an open protocol, that decision should be theirs, and that decision should be permissionless.</p>
<p>At the same time, it is also critical that the protocol acts the same across the board, regardless of what chain it is being run on.</p>
<h2>Why cross-chain governance?</h2>
<p>While a simple upgrade or change in protocol settings on one network may require just a single call, living across 10+ disparate networks means that even a simple settings tweak quickly becomes quite a tedious process to manage and deploy. We decided to work towards the automation of a cross-chain solution for a number of reasons:</p>
<ol>
<li><strong>Consistency</strong>: We need to make sure that any change that happens somewhere is replicated everywhere, so the experience of using the protocol is consistent across chains.</li>
<li><strong>Reduce risk of deployment errors</strong>: On each chain, the set of contracts are deployed at <a href="https://www.npmjs.com/package/@unlock-protocol/networks">different addresses</a>. To make all upgrades manually introduces the possibility of errors. Even if to err is human, we love to avoid it as much as we can.</li>
<li><strong>Transparency</strong>: While changes in the protocol are <a href="https://unlock-protocol.com/guides/delegation/">voted on in the Unlock DAO</a>, the execution and enforcement of these changes is left entirely to human discretion. We pursue the goal of making Unlock a decentralised organization and therefore like to transfer that burden to auditable smart contracts.</li>
</ol>
<h2>How it works: the Unlock Owner</h2>
<p>Our design relies on a straightforward idea: the DAO on Ethereum mainnet is the authority that all contracts should listen to. When a proposal is executed, the DAO should send instructions across the bridge to all other instances of Unlock. To enable the cross-chain governance process, we have to pass contract calls and data across chains. For that, we rely on the <a href="https://www.connext.network/">Connext Bridge</a>.</p>
<p>A new contract called <code>UnlockOwner</code> acts as a relay in this process, receiving the calls from the DAO across the bridge (or directly on mainnet) and passing it down to the local Unlock contract. It has mainly two functions: 1) upgrade the Unlock contract (core of the protocol) and 2) change settings of the Unlock contract itself (e.g. add a new template or tweak a parameter).</p>
<p>In technical terms, <code>UnlockOwner</code> is deployed on each network. It owns (as in owner of an <a href="https://docs.openzeppelin.com/contracts/4.x/access-control#ownership-and-ownable">Ownable contract</a>) both the Unlock contract instance and the ProxyAdmin (that controls the proxy upgrades).</p>
<p><img src="/images/blog/crosschain/cross-chain-napkin.png" alt="cross-chain-napkin.png"></p>
<p><em>Original sketch of how calls could circulate across the bridge and through Unlock Manager on multiple chains</em></p>
<h2>Risks and safeguards</h2>
<p>Automating the governance process facilitates the propagation of decisions. This also means a bad actor could introduce malicious actions that then spread faster to the entire protocol. We set up all relevant origin and destination checks within the contracts themselves, but we also took extra precautions.</p>
<p>To mitigate the risks of a protocol-wide attack, we set up two main tools:</p>
<ol>
<li><strong>A safety delay</strong>: Every contract call arriving from the DAO across the bridge will be quarantined for a duration of at least two days. That leaves some room to act if any malicious calls were to be sent. Note that this time period comes <em>after</em> the delay introduced by the DAO itself. For that, we rely on <a href="https://docs.openzeppelin.com/contracts/4.x/governance#timelock">OpenZeppelin's Timelock contract</a> that has been audited multiple times.</li>
<li><strong>Multisigs</strong>: On each chain, a multisig owned by our team and trusted members of the Unlock community retains the ability to trigger actions through the <code>UnlockOwner</code> contract. We believe this is still a requirement at this stage as a safeguard. Performing a protocol-wide upgrade across chains is a radically new approach. As such processes of governance are maturing, we hope multisigs could become obsolete and we have built a way in the <code>UnlockOwner</code> to remove them. We believe this will happen in due time.</li>
</ol>
<h2>Try it now !</h2>
<p>As of today, the cross-chain governance process is already deployed on ETH Goerli and Polygon Mumbai testnets. We redeployed a DAO on Goerli (which acts as a "mainnet" for testnets) and are still testing how various calls behave and how our current approach could be improved.</p>
<p>We encourage you to check proposals on our <a href="https://www.tally.xyz/gov/unlock-test-dao">Unlock Test DAO</a>. Any feedback will be warmly welcome!</p>
<p>Below are the addresses of deployed test instances (nb. these may change over time as we redeploy the contracts).</p>
<h3>Goerli Contracts</h3>
<ul>
<li><strong>Unlock:</strong> <a href="https://goerli.etherscan.io/address/0x7fA9F695856269E1415b2d373b35037159E2F94C">https://goerli.etherscan.io/address/0x7fA9F695856269E1415b2d373b35037159E2F94C</a></li>
<li><strong>UDT:</strong> <a href="https://goerli.etherscan.io/address/0xaB82D702A4e0cD165072C005dc504A21c019718F#readProxyContract">https://goerli.etherscan.io/address/0xaB82D702A4e0cD165072C005dc504A21c019718F#readProxyContract</a></li>
<li><strong>Gov:</strong> <a href="https://goerli.etherscan.io/address/0xDcDE260Df00ba86889e8B112DfBe1A4945B35CA9">https://goerli.etherscan.io/address/0xDcDE260Df00ba86889e8B112DfBe1A4945B35CA9</a></li>
<li><strong>Timelock:</strong> <a href="https://goerli.etherscan.io/address/0xD7477B7c0CdA4204Cf860e4c27486061b15a5AC3">https://goerli.etherscan.io/address/0xD7477B7c0CdA4204Cf860e4c27486061b15a5AC3</a></li>
<li><strong>Unlock Owner:</strong> <a href="https://goerli.etherscan.io/address/0x6E74DC46EbF2cDB75B72Ab1dCAe3C98c7E9d28a1">https://goerli.etherscan.io/address/0x6E74DC46EbF2cDB75B72Ab1dCAe3C98c7E9d28a1</a></li>
</ul>
<h3>Mumbai Contracts</h3>
<ul>
<li><strong>Unlock:</strong> <a href="https://mumbai.polygonscan.com/address/0x8db6eE991C6C3CB2b6228b558c1b3D6EA474cB42#writeProxyContract">https://mumbai.polygonscan.com/address/0x8db6eE991C6C3CB2b6228b558c1b3D6EA474cB42#writeProxyContract</a></li>
<li><strong>Unlock Owner:</strong> <a href="https://mumbai.polygonscan.com/address/0x8db6eE991C6C3CB2b6228b558c1b3D6EA474cB42#writeProxyContract">https://mumbai.polygonscan.com/address/0xdc230F9A08918FaA5ae48B8E13647789A8B6dD46</a></li>
</ul>
<h3>Test DAO Dashboard</h3>
<ul>
<li><strong>Tally:</strong> <a href="https://www.tally.xyz/gov/unlock-test-dao">https://www.tally.xyz/gov/unlock-test-dao</a></li>
</ul>



Today, we’re excited to introduce a new way to purchase Unlock memberships with Stripe!

![Credit card NFT Onramp](/images/blog/credit-card-onramp.png)

Stripe [recently announced](https://stripe.com/blog/crypto-onramp) a new onramp mechanism and it is a great match for our membership contracts. You can test it today by [buying a membership on this lock](https://app.unlock-protocol.com/checkout?id=498f16e7-b9d3-4f80-93ec-74271d772b5d). (We’re happy to refund you if you ask!)

We have had [support for credit card payments](https://unlock-protocol.com/guides/enabling-credit-cards/) for a few years now. However, this legacy credit card payment implementation required lock managers (who deployed the membership contracts) to connect their smart contract(s) to Stripe’s payment gateway using Stripe Connect. This works great, and we’re keeping this option, but is limited in scope as [Stripe Connect](https://stripe.com/connect) is not available in every country or for any kind of business.

With Stripe onramp, we’re adding support for credit card payments on a lock, even if the lock manager themselves has not connected with Stripe! For now, this feature works only for locks deployed on _Polygon_ and _Ethereum Mainnet_, and only for locks priced in USDC, but soon, using our [swap and purchase](https://unlock-protocol.com/blog/swap-and-purchase) capabilities, this will be available for locks in _any_ currency, provided that there is a way to convert from USDC to that currency, and for all the networks that Stripe will add support for.

## How does it work?

First, I should mention that it works for both for users who have their own wallets, as well as for users who don’t have a wallet (using their [Unlock Account](https://docs.unlock-protocol.com/tools/sign-in-with-ethereum/unlock-accounts/)).

When the user selects the option to checkout with Stripe’s onramp, we ask them to sign two messages (these are just signatures, without any gas spent). The first message to sign is an **approval** to spend the funds they will receive from Stripe, immediately after they received them. The second one is a confirmation that they want to spend these funds for a **specific** membership contract.

These two signatures are critical for security and helps ensure the funds they receive from Stripe cannot be spent for anything else.

Once they have signed these two transactions, they will follow the Stripe checkout flow (the one that you already find on many websites around the world). At the end of it, Stripe sends [USDC](https://www.circle.com/en/usdc) to their address and Unlock Labs triggers a transaction that uses the two signatures they provided earlier to use these USDC tokens to purchase the NFT membership.

## Next Steps

Like always in the crypto space, we’re learning as we explore! The obvious next step for us is to add support for our “swap and purchase” flow. This would add support to memberships priced in **any** currency, not just USDC. The flow would be nearly identical from a user’s perspective, but instead of using the USDC to purchase the membership, our contract will instantly swap it for the right amount of tokens required to purchase the membership.

Stripe has indicated that they will add support for more chains and L2s. We will of course add support for these chains as soon as they do! Finally, Stripe has also indicated that they want to explore support for recurring purchases, which we would be thrilled to add support for, on top of our native [crypto recurring payments](https://unlock-protocol.com/guides/recurring-memberships/).


Today, we’re excited to introduce a new way to purchase Unlock memberships with Stripe!

Purchase any membership using your payment card!

Stripe Onramp Support!

<p>Today, we’re excited to introduce a new way to purchase Unlock memberships with Stripe!</p>
<p><img src="/images/blog/credit-card-onramp.png" alt="Credit card NFT Onramp"></p>
<p>Stripe <a href="https://stripe.com/blog/crypto-onramp">recently announced</a> a new onramp mechanism and it is a great match for our membership contracts. You can test it today by <a href="https://app.unlock-protocol.com/checkout?id=498f16e7-b9d3-4f80-93ec-74271d772b5d">buying a membership on this lock</a>. (We’re happy to refund you if you ask!)</p>
<p>We have had <a href="https://unlock-protocol.com/guides/enabling-credit-cards/">support for credit card payments</a> for a few years now. However, this legacy credit card payment implementation required lock managers (who deployed the membership contracts) to connect their smart contract(s) to Stripe’s payment gateway using Stripe Connect. This works great, and we’re keeping this option, but is limited in scope as <a href="https://stripe.com/connect">Stripe Connect</a> is not available in every country or for any kind of business.</p>
<p>With Stripe onramp, we’re adding support for credit card payments on a lock, even if the lock manager themselves has not connected with Stripe! For now, this feature works only for locks deployed on <em>Polygon</em> and <em>Ethereum Mainnet</em>, and only for locks priced in USDC, but soon, using our <a href="https://unlock-protocol.com/blog/swap-and-purchase">swap and purchase</a> capabilities, this will be available for locks in <em>any</em> currency, provided that there is a way to convert from USDC to that currency, and for all the networks that Stripe will add support for.</p>
<h2>How does it work?</h2>
<p>First, I should mention that it works for both for users who have their own wallets, as well as for users who don’t have a wallet (using their <a href="https://docs.unlock-protocol.com/tools/sign-in-with-ethereum/unlock-accounts/">Unlock Account</a>).</p>
<p>When the user selects the option to checkout with Stripe’s onramp, we ask them to sign two messages (these are just signatures, without any gas spent). The first message to sign is an <strong>approval</strong> to spend the funds they will receive from Stripe, immediately after they received them. The second one is a confirmation that they want to spend these funds for a <strong>specific</strong> membership contract.</p>
<p>These two signatures are critical for security and helps ensure the funds they receive from Stripe cannot be spent for anything else.</p>
<p>Once they have signed these two transactions, they will follow the Stripe checkout flow (the one that you already find on many websites around the world). At the end of it, Stripe sends <a href="https://www.circle.com/en/usdc">USDC</a> to their address and Unlock Labs triggers a transaction that uses the two signatures they provided earlier to use these USDC tokens to purchase the NFT membership.</p>
<h2>Next Steps</h2>
<p>Like always in the crypto space, we’re learning as we explore! The obvious next step for us is to add support for our “swap and purchase” flow. This would add support to memberships priced in <strong>any</strong> currency, not just USDC. The flow would be nearly identical from a user’s perspective, but instead of using the USDC to purchase the membership, our contract will instantly swap it for the right amount of tokens required to purchase the membership.</p>
<p>Stripe has indicated that they will add support for more chains and L2s. We will of course add support for these chains as soon as they do! Finally, Stripe has also indicated that they want to explore support for recurring purchases, which we would be thrilled to add support for, on top of our native <a href="https://unlock-protocol.com/guides/recurring-memberships/">crypto recurring payments</a>.</p>



![alphatweet-share.png](/images/blog/alphatweet/alphatweet-share.png)

_**ALPHA by Unlock Labs** is an initiative to explore new business models and opportunities enabled by blockchain technologies and using Unlock Protocol. It is an iterative series of experiments with the intended goals of learning and sharing information and experiences as part of the open-source Unlock Protocol project._

## This experiment is called ALPHAtweet

ALPHAtweet enables you and your followers to make money through your content and sharing. It’s powered by Unlock Protocol. Going a bit deeper into this experiment, an “Alpha” is a piece of paid content that is being shared, where **both the creator and the sharer participate in the benefits of sharing when someone unlocks the Alpha**.

While this first experiment emphasizes sharing on Twitter, the magic is that these items of Alpha can be shared _anywhere_ by way of share links and, in every case, the creators and sharers **both** have the opportunity to be compensated across _any_ platform, every time an Alpha is shared. 🤯

This is not something that could be done before today.

Creators set their own price for unlocking their exclusive content, the Alpha. They also set a referral percentage bonus that is split with those who share or amplify the content.

In this model, the creator can set the referral percentage bonus to any level they want, based on the creator’s own goals. For example:

- A creator could set the referral bonus to 100% (giving **all** revenue received to the sharer) to optimize for reach, awareness, exposure, and virality of their content, which means that those doing the sharing get 100% of the fees collected when the creator’s content is unlocked.
- Or, the creator could set the sharing referral bonus percentage to 0% and take all fees, but then there would be no economic benefit to those who do the sharing (which, to be fair, is the way sharing on social works today).
- Or, the creator could set the referral bonus somewhere in the middle (50/50 or any other amount; it’s up to the creator). We may find out that ALPHAtweet and this model work best when set to something like 20/80 or 10/90 where the distribution is heavily incentivized (but we don’t know — that’s why it’s an experiment!).

Here’s a walkthrough diagram of how money flows to pay both creators and sharers.

<div style="position: relative; overflow: hidden; width: 100%; padding-top: 0%;"><iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQ-m3vul5u2NS39QptD70hBy1ib3AzNGWaSO0Znk7sigAuYZayhN9MdR5MWJU_hMT5cqyJKUsiyh8dc/embed?start=false&loop=false&delayms=60000" frameborder="0" width="680" height="411" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></div>

The revenue sharing mechanism is the big deal here. Creators set their terms, and sharers can participate in the upside. (It’s also completely configurable, so the platforms could participate in the upside, too.)

At the outset, we’re starting with a small cohort of creators as we shake out bugs and get feedback on the overall experience. That said, _anyone_ can choose to unlock, share, and amplify Alpha (and participate in rewards!), and _everyone_ can view the snippets/teasers of Alpha.

Want to see what ALPHAtweet looks like in action? Here’s what the experience looks like for a sharer of Alpha. (Thanks to Michael Joseph for the video walkthrough!)

<div style="position: relative; overflow: hidden; width: 100%; padding-top: 56.25%;"><iframe style="position: absolute; top: 0; left: 0; bottom: 0; right: 0; width: 100%; height: 100%;" src="https://www.youtube.com/embed/sUTaz7-MakY" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div>

Want to check it out today? Check out these posts from some Alpha creators:

- Michael C. Joseph, "[Coordinape Deep Dive](https://twitter.com/michaelcjoseph/status/1655633679794962432)"
- Julien Genestoux, "[Layers of (De)centralization](https://alphatweet.xyz/posts/ed023c92-8dfd-4060-984c-bc5acdd02436)"
- Stephen Wolfson, "[The Complex World of Style, Copyright, and Generative AI](https://twitter.com/ccarfi/status/1655662240006295553)" (via Creative Commons)

ALPHAtweet is part of the ongoing series of experiments in future business models that Unlock Protocol is exploring for the web. Thanks for being a part of it!

_Interested in becoming a creator on ALPHAtweet or have a question? Reach out to the Unlock Labs team in our [Discord](https://discord.unlock-protocol.com)._


ALPHAtweet is an experiment in web3 business models where creators and their community both share in the upside of creating and sharing content across social networks.

Unlock Labs Launches the ALPHAtweet Experiment

<p><img src="/images/blog/alphatweet/alphatweet-share.png" alt="alphatweet-share.png"></p>
<p><em><strong>ALPHA by Unlock Labs</strong> is an initiative to explore new business models and opportunities enabled by blockchain technologies and using Unlock Protocol. It is an iterative series of experiments with the intended goals of learning and sharing information and experiences as part of the open-source Unlock Protocol project.</em></p>
<h2>This experiment is called ALPHAtweet</h2>
<p>ALPHAtweet enables you and your followers to make money through your content and sharing. It’s powered by Unlock Protocol. Going a bit deeper into this experiment, an “Alpha” is a piece of paid content that is being shared, where <strong>both the creator and the sharer participate in the benefits of sharing when someone unlocks the Alpha</strong>.</p>
<p>While this first experiment emphasizes sharing on Twitter, the magic is that these items of Alpha can be shared <em>anywhere</em> by way of share links and, in every case, the creators and sharers <strong>both</strong> have the opportunity to be compensated across <em>any</em> platform, every time an Alpha is shared. 🤯</p>
<p>This is not something that could be done before today.</p>
<p>Creators set their own price for unlocking their exclusive content, the Alpha. They also set a referral percentage bonus that is split with those who share or amplify the content.</p>
<p>In this model, the creator can set the referral percentage bonus to any level they want, based on the creator’s own goals. For example:</p>
<ul>
<li>A creator could set the referral bonus to 100% (giving <strong>all</strong> revenue received to the sharer) to optimize for reach, awareness, exposure, and virality of their content, which means that those doing the sharing get 100% of the fees collected when the creator’s content is unlocked.</li>
<li>Or, the creator could set the sharing referral bonus percentage to 0% and take all fees, but then there would be no economic benefit to those who do the sharing (which, to be fair, is the way sharing on social works today).</li>
<li>Or, the creator could set the referral bonus somewhere in the middle (50/50 or any other amount; it’s up to the creator). We may find out that ALPHAtweet and this model work best when set to something like 20/80 or 10/90 where the distribution is heavily incentivized (but we don’t know — that’s why it’s an experiment!).</li>
</ul>
<p>Here’s a walkthrough diagram of how money flows to pay both creators and sharers.</p>
<div style="position: relative; overflow: hidden; width: 100%; padding-top: 0%;"><iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQ-m3vul5u2NS39QptD70hBy1ib3AzNGWaSO0Znk7sigAuYZayhN9MdR5MWJU_hMT5cqyJKUsiyh8dc/embed?start=false&loop=false&delayms=60000" frameborder="0" width="680" height="411" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></div>
<p>The revenue sharing mechanism is the big deal here. Creators set their terms, and sharers can participate in the upside. (It’s also completely configurable, so the platforms could participate in the upside, too.)</p>
<p>At the outset, we’re starting with a small cohort of creators as we shake out bugs and get feedback on the overall experience. That said, <em>anyone</em> can choose to unlock, share, and amplify Alpha (and participate in rewards!), and <em>everyone</em> can view the snippets/teasers of Alpha.</p>
<p>Want to see what ALPHAtweet looks like in action? Here’s what the experience looks like for a sharer of Alpha. (Thanks to Michael Joseph for the video walkthrough!)</p>
<div style="position: relative; overflow: hidden; width: 100%; padding-top: 56.25%;"><iframe style="position: absolute; top: 0; left: 0; bottom: 0; right: 0; width: 100%; height: 100%;" src="https://www.youtube.com/embed/sUTaz7-MakY" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe></div>
<p>Want to check it out today? Check out these posts from some Alpha creators:</p>
<ul>
<li>Michael C. Joseph, "<a href="https://twitter.com/michaelcjoseph/status/1655633679794962432">Coordinape Deep Dive</a>"</li>
<li>Julien Genestoux, "<a href="https://alphatweet.xyz/posts/ed023c92-8dfd-4060-984c-bc5acdd02436">Layers of (De)centralization</a>"</li>
<li>Stephen Wolfson, "<a href="https://twitter.com/ccarfi/status/1655662240006295553">The Complex World of Style, Copyright, and Generative AI</a>" (via Creative Commons)</li>
</ul>
<p>ALPHAtweet is part of the ongoing series of experiments in future business models that Unlock Protocol is exploring for the web. Thanks for being a part of it!</p>
<p><em>Interested in becoming a creator on ALPHAtweet or have a question? Reach out to the Unlock Labs team in our <a href="https://discord.unlock-protocol.com">Discord</a>.</em></p>



The [Events by Unlock Labs](https://events.unlock-protocol.com/) page has an updated, modern and fresh look!

There are a number of changes included with the redesign:

- Cover image
- Walletless RSVP
- URL slugs for your event page (this also applies to [certifications](https://certifications.unlock-protocol.com)!)

## Cover image

You now have the option to add a cover image for your event page! Simply click the `Upload Image` button and follow the steps from the modal.

![add cover](/images/blog/event-page-redesign/add-cover-image.png)

Once the modal is open, you can pick an image or set the URL to see the preview; if you are done, you can just click `Save` and be done!

![cover image upload](/images/blog/event-page-redesign/cover-image-upload.png)

Once saved, the image will be set as the cover image for your events page.
You can change it anytime you want by following the previous steps.

## Walletless RSVP

The walletless, RSVP-by-email form is now visible when on the side of the event's details.

![rsvp form](/images/blog/event-page-redesign/rsvp-form.png)

## Custom URL slugs

Great news — you can now define a custom slug for your events page. Instead of a long URL, you can now specify a much shorter URL for your event.

![Custom URL slug](/images/blog/event-page-redesign/add-slug.png)

## What if I find an issue or bug in new event page redesign?

Please [open an issue on Github](https://github.com/unlock-protocol/unlock) or tell us [in the Discord](https://discord.unlock-protocol.com/) and we'll fix it ASAP.


A re-designed events page with a modern and fresh look!

Events by Unlock Labs Re-design

<p>The <a href="https://events.unlock-protocol.com/">Events by Unlock Labs</a> page has an updated, modern and fresh look!</p>
<p>There are a number of changes included with the redesign:</p>
<ul>
<li>Cover image</li>
<li>Walletless RSVP</li>
<li>URL slugs for your event page (this also applies to <a href="https://certifications.unlock-protocol.com">certifications</a>!)</li>
</ul>
<h2>Cover image</h2>
<p>You now have the option to add a cover image for your event page! Simply click the <code>Upload Image</code> button and follow the steps from the modal.</p>
<p><img src="/images/blog/event-page-redesign/add-cover-image.png" alt="add cover"></p>
<p>Once the modal is open, you can pick an image or set the URL to see the preview; if you are done, you can just click <code>Save</code> and be done!</p>
<p><img src="/images/blog/event-page-redesign/cover-image-upload.png" alt="cover image upload"></p>
<p>Once saved, the image will be set as the cover image for your events page.
You can change it anytime you want by following the previous steps.</p>
<h2>Walletless RSVP</h2>
<p>The walletless, RSVP-by-email form is now visible when on the side of the event's details.</p>
<p><img src="/images/blog/event-page-redesign/rsvp-form.png" alt="rsvp form"></p>
<h2>Custom URL slugs</h2>
<p>Great news — you can now define a custom slug for your events page. Instead of a long URL, you can now specify a much shorter URL for your event.</p>
<p><img src="/images/blog/event-page-redesign/add-slug.png" alt="Custom URL slug"></p>
<h2>What if I find an issue or bug in new event page redesign?</h2>
<p>Please <a href="https://github.com/unlock-protocol/unlock">open an issue on Github</a> or tell us <a href="https://discord.unlock-protocol.com/">in the Discord</a> and we'll fix it ASAP.</p>



![v13-cover.png](/images/blog/v13/v13-cover.png)

We are pleased to announce that a **new version of the Unlock Protocol** is now available. These improvements and new capabilities are sure to make the Unlock Protocol even more powerful and user-friendly than before. We fixed a few bugs, added some gas optimisations and shipped a bunch of new features.

You can review the original conversation in the Unlock DAO community forum regarding these features [here](https://unlock.community/t/unlock-protocol-upgrade-proposal/368).

If you are a Lock Manager, you can upgrade your lock directly from the [Unlock Dashboard](https://app.unlock-protocol.com/locks). Remember, even though this new version is made available by us, we certainly cannot upgrade your locks. Only a lock manager can upgrade their lock(s)!

## A general upgrade of the base Unlock smart contracts

Unlock Protocol has recently undergone two important smart contract upgrades.

First, a new version of the [Unlock factory contract](https://docs.unlock-protocol.com/core-protocol/unlock/) has been released. This contract takes care of deploying and upgrading new locks, as well as tracking growth of protocol usage. The new version added the _ability_ for the protocol to include a protocol fee on transactions, while leaving its _activation_ to the discretion of the governance DAO.

Within the Unlock core contract, we also improved gas consumption of most functions (by using [Solidity custom errors](https://blog.soliditylang.org/2021/04/21/custom-errors/) instead of require statements).

The second important upgrade was the release of a new version of the [PublicLock contract](https://docs.unlock-protocol.com/core-protocol/public-lock/). This contract acts as a template for each lock deployed. This latest version (v13) fixes issues that appeared when canceling or burning membership keys, and makes renewals easier. It is now available as the default version for all new locks and the Unlock Dashboard naturally supports them! You also able [upgrade](https://docs.unlock-protocol.com/core-protocol/public-lock/deploying-locks/#upgrading-locks) an existing version 12 lock to version 13. (The version of your lock is displayed on the Unlock dashboard and can also be found on a block explorer.)

## Upgrading across chains

The Unlock Protocol is currently available on [9 different production chains](https://docs.unlock-protocol.com/core-protocol/unlock/networks) and several test networks. To perform a protocol upgrade means to redeploy contracts on all chains. We are very careful about consistency of the protocol across the board, so we can offer the best experience for users of various communities. To make the process smoother and more transparent, we are currently working on a way to unify our governance across the various chains we supported and handle it all to the DAO (more on that soon).

The only noticeable change this time happened on the Ethereum mainnet, where the main Unlock contract has been redeployed to reflect a change in the way [UDT token rewards](https://docs.unlock-protocol.com/governance/unlock-dao-tokens) are distributed. While we originally minted new UDT for referrers, we now distribute tokens directly from our existing supply.

## Upgrading your lock contract

If you are a lock manager, you will need to upgrade your lock contract to take advantage of the new features and improvements. To do so, follow the instructions provided in the [Unlock documentation](https://unlock-protocol.com/blog/lock-v12-release).

![v13-cover.png](/images/blog/v13/upgrading.gif)

**What if I find an issue or bug in the Unlock Protocol v13 upgrade?**

Please [open an issue on Github](https://github.com/unlock-protocol/unlock) or [tell us in Discord](https://discord.unlock-protocol.com/)!


An updated version of Unlock’s core contract and a new template contract for managing memberships

Unlock Protocol Smart Contracts Upgrade v13

<p><img src="/images/blog/v13/v13-cover.png" alt="v13-cover.png"></p>
<p>We are pleased to announce that a <strong>new version of the Unlock Protocol</strong> is now available. These improvements and new capabilities are sure to make the Unlock Protocol even more powerful and user-friendly than before. We fixed a few bugs, added some gas optimisations and shipped a bunch of new features.</p>
<p>You can review the original conversation in the Unlock DAO community forum regarding these features <a href="https://unlock.community/t/unlock-protocol-upgrade-proposal/368">here</a>.</p>
<p>If you are a Lock Manager, you can upgrade your lock directly from the <a href="https://app.unlock-protocol.com/locks">Unlock Dashboard</a>. Remember, even though this new version is made available by us, we certainly cannot upgrade your locks. Only a lock manager can upgrade their lock(s)!</p>
<h2>A general upgrade of the base Unlock smart contracts</h2>
<p>Unlock Protocol has recently undergone two important smart contract upgrades.</p>
<p>First, a new version of the <a href="https://docs.unlock-protocol.com/core-protocol/unlock/">Unlock factory contract</a> has been released. This contract takes care of deploying and upgrading new locks, as well as tracking growth of protocol usage. The new version added the <em>ability</em> for the protocol to include a protocol fee on transactions, while leaving its <em>activation</em> to the discretion of the governance DAO.</p>
<p>Within the Unlock core contract, we also improved gas consumption of most functions (by using <a href="https://blog.soliditylang.org/2021/04/21/custom-errors/">Solidity custom errors</a> instead of require statements).</p>
<p>The second important upgrade was the release of a new version of the <a href="https://docs.unlock-protocol.com/core-protocol/public-lock/">PublicLock contract</a>. This contract acts as a template for each lock deployed. This latest version (v13) fixes issues that appeared when canceling or burning membership keys, and makes renewals easier. It is now available as the default version for all new locks and the Unlock Dashboard naturally supports them! You also able <a href="https://docs.unlock-protocol.com/core-protocol/public-lock/deploying-locks/#upgrading-locks">upgrade</a> an existing version 12 lock to version 13. (The version of your lock is displayed on the Unlock dashboard and can also be found on a block explorer.)</p>
<h2>Upgrading across chains</h2>
<p>The Unlock Protocol is currently available on <a href="https://docs.unlock-protocol.com/core-protocol/unlock/networks">9 different production chains</a> and several test networks. To perform a protocol upgrade means to redeploy contracts on all chains. We are very careful about consistency of the protocol across the board, so we can offer the best experience for users of various communities. To make the process smoother and more transparent, we are currently working on a way to unify our governance across the various chains we supported and handle it all to the DAO (more on that soon).</p>
<p>The only noticeable change this time happened on the Ethereum mainnet, where the main Unlock contract has been redeployed to reflect a change in the way <a href="https://docs.unlock-protocol.com/governance/unlock-dao-tokens">UDT token rewards</a> are distributed. While we originally minted new UDT for referrers, we now distribute tokens directly from our existing supply.</p>
<h2>Upgrading your lock contract</h2>
<p>If you are a lock manager, you will need to upgrade your lock contract to take advantage of the new features and improvements. To do so, follow the instructions provided in the <a href="https://unlock-protocol.com/blog/lock-v12-release">Unlock documentation</a>.</p>
<p><img src="/images/blog/v13/upgrading.gif" alt="v13-cover.png"></p>
<p><strong>What if I find an issue or bug in the Unlock Protocol v13 upgrade?</strong></p>
<p>Please <a href="https://github.com/unlock-protocol/unlock">open an issue on Github</a> or <a href="https://discord.unlock-protocol.com/">tell us in Discord</a>!</p>



![certification-cover-min.png](/images/blog/certifications/certification-cover-min.png)

Unlock has launched an easy way to issue certifications and credentials on-chain. Every certification held is a proof of a course completion and has its own verifiable NFT.

Let's see how to create a certification or credential and distribute it to participants.

## Certifications powered by Unlock Protocol

First, visit [https://certifications.unlock-protocol.com](https://certifications.unlock-protocol.com), where you can learn about the benefits of certification and credentialing NFTs powered by Unlock Protocol.

## Enter information about your certification

Click "Create your certification now” to go to the form to build your certification. You’ll put in a few pieces of information to set up your certification.

### Basic certification information

Enter the basic information for your certification including:

- **Certification name**: The program or course name that was completed by the recipient of the certification.
- **Description**: The description for the certification. This will be part of the NFT metadata.
- **Official issuer name**: This is the name of the issuing organization for this certification. This is part of NFT metadata.
- **External URL**: Include a link to the URL of the organization that performed the certification. This will be included in the NFT metadata.
- **Image**: The main image logo that will be shown for the on-chain certificate NFT.
- **Certification duration:** How long the certification will be valid for. Certifications have an unlimited duration by default. This duration can be changed during setup to whatever timeframe is appropriate for your situation.

![basic-info-min.png](/images/blog/certifications/basic-info-min.png)

### Price and quantity

By default, your certification can't be purchased: it can only be granted (”airdropped”) to a recipient. (We’ll explore how to perform the airdrop later in this article.)

![price-quantity-min.png](/images/blog/certifications/price-quantity-min.png)

In case you do choose to make your certification purchasable, you will need to set a price and a maximum supply of certifications.

![price-quantity-2-min.png](/images/blog/certifications/price-quantity-2-min.png)

### Network

This is the network on which your certification smart contract will be deployed.

![network-min.png](/images/blog/certifications/network-min.png)

Once the above settings are specified, you can deploy the certificate and see the preview.

![certifica-deploy-gif.gif](/images/blog/certifications/certifica-deploy-gif.gif)

## Certificate overview

Each certification has a dedicated page where information for that certification is visible.

An individual who holds a certificate will be able to download it or share it via social networks.

### Certification template

![certification-template-min.png](/images/blog/certifications/certification-template-min.png)

### Issued certification

![certification-view-min.png](/images/blog/certifications/certification-view-min.png)

### Transferable certificate

In most cases, a certification should not be able to be transferred to another user. Certifications will be non-transferable by default, and a notification will be shown in the user interface if a certification is able to be transferred. This notification is displayed to help ensure that the ability to transfer certifications is the intention of the creator of the certification program.

![non-transfer-min.png](/images/blog/certifications/non-transfer-min.png)

## Airdrop

As a [Lock Manager](https://docs.unlock-protocol.com/core-protocol/public-lock/access-control/#lockmanager) and creator of a certification, you can [airdrop](https://unlock-protocol.com/guides/how-to-airdrop-memberships/) certificates to your users either to their crypto wallet address or to their email address.

![certification-airdrop-min.png](/images/blog/certifications/certification-airdrop-min.png)

Thats all! Visit [https://certifications.unlock-protocol.com](https://certifications.unlock-protocol.com) and start to deploy your first certificate!

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

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


Unlock introduces an easy way to issue transparent, provable credentials for professional certifications, continuing education credits, industry expertise, and more.

Oh Yeah? Prove it! Certifications by Unlock

<p><img src="/images/blog/certifications/certification-cover-min.png" alt="certification-cover-min.png"></p>
<p>Unlock has launched an easy way to issue certifications and credentials on-chain. Every certification held is a proof of a course completion and has its own verifiable NFT.</p>
<p>Let's see how to create a certification or credential and distribute it to participants.</p>
<h2>Certifications powered by Unlock Protocol</h2>
<p>First, visit <a href="https://certifications.unlock-protocol.com">https://certifications.unlock-protocol.com</a>, where you can learn about the benefits of certification and credentialing NFTs powered by Unlock Protocol.</p>
<h2>Enter information about your certification</h2>
<p>Click "Create your certification now” to go to the form to build your certification. You’ll put in a few pieces of information to set up your certification.</p>
<h3>Basic certification information</h3>
<p>Enter the basic information for your certification including:</p>
<ul>
<li><strong>Certification name</strong>: The program or course name that was completed by the recipient of the certification.</li>
<li><strong>Description</strong>: The description for the certification. This will be part of the NFT metadata.</li>
<li><strong>Official issuer name</strong>: This is the name of the issuing organization for this certification. This is part of NFT metadata.</li>
<li><strong>External URL</strong>: Include a link to the URL of the organization that performed the certification. This will be included in the NFT metadata.</li>
<li><strong>Image</strong>: The main image logo that will be shown for the on-chain certificate NFT.</li>
<li><strong>Certification duration:</strong> How long the certification will be valid for. Certifications have an unlimited duration by default. This duration can be changed during setup to whatever timeframe is appropriate for your situation.</li>
</ul>
<p><img src="/images/blog/certifications/basic-info-min.png" alt="basic-info-min.png"></p>
<h3>Price and quantity</h3>
<p>By default, your certification can't be purchased: it can only be granted (”airdropped”) to a recipient. (We’ll explore how to perform the airdrop later in this article.)</p>
<p><img src="/images/blog/certifications/price-quantity-min.png" alt="price-quantity-min.png"></p>
<p>In case you do choose to make your certification purchasable, you will need to set a price and a maximum supply of certifications.</p>
<p><img src="/images/blog/certifications/price-quantity-2-min.png" alt="price-quantity-2-min.png"></p>
<h3>Network</h3>
<p>This is the network on which your certification smart contract will be deployed.</p>
<p><img src="/images/blog/certifications/network-min.png" alt="network-min.png"></p>
<p>Once the above settings are specified, you can deploy the certificate and see the preview.</p>
<p><img src="/images/blog/certifications/certifica-deploy-gif.gif" alt="certifica-deploy-gif.gif"></p>
<h2>Certificate overview</h2>
<p>Each certification has a dedicated page where information for that certification is visible.</p>
<p>An individual who holds a certificate will be able to download it or share it via social networks.</p>
<h3>Certification template</h3>
<p><img src="/images/blog/certifications/certification-template-min.png" alt="certification-template-min.png"></p>
<h3>Issued certification</h3>
<p><img src="/images/blog/certifications/certification-view-min.png" alt="certification-view-min.png"></p>
<h3>Transferable certificate</h3>
<p>In most cases, a certification should not be able to be transferred to another user. Certifications will be non-transferable by default, and a notification will be shown in the user interface if a certification is able to be transferred. This notification is displayed to help ensure that the ability to transfer certifications is the intention of the creator of the certification program.</p>
<p><img src="/images/blog/certifications/non-transfer-min.png" alt="non-transfer-min.png"></p>
<h2>Airdrop</h2>
<p>As a <a href="https://docs.unlock-protocol.com/core-protocol/public-lock/access-control/#lockmanager">Lock Manager</a> and creator of a certification, you can <a href="https://unlock-protocol.com/guides/how-to-airdrop-memberships/">airdrop</a> certificates to your users either to their crypto wallet address or to their email address.</p>
<p><img src="/images/blog/certifications/certification-airdrop-min.png" alt="certification-airdrop-min.png"></p>
<p>Thats all! Visit <a href="https://certifications.unlock-protocol.com">https://certifications.unlock-protocol.com</a> and start to deploy your first certificate!</p>
<p><strong>What if I find an issue or bug in the new certification builder?</strong></p>
<p>Please open an issue on Github or tell us in Discord and we'll fix it ASAP.</p>



![Checkout Payments page](/images/blog/swap-and-purchase/swap-and-purchase.png)

We're thrilled to announce the latest addition to Unlock: Swap & Purchase in Unlock Checkout.

By leveraging an external contract powered by Uniswap, Swap & Purchase in Unlock Checkout enables a user to buy a membership NFT even if it’s priced in a different currency than the currency a purchaser holds in their wallet. There's no need for users to perform the swap, as it happens natively. For example, if an NFT is priced in USDC but the purchaser only holds MATIC in their wallet, Swap & Purchase will swap enough MATIC for the correct amount of USDC in a single step, making things easier for the purchaser and enabling the creator to be paid in the currency of their choice. This simplifies the process and reduces friction for both creators and purchasers.

[Try it out now](https://app.unlock-protocol.com/checkout?id=bb4a2ae0-2fca-4bdf-bd40-f0c41cde2510)

In Swap & Purchase, the Unlock interface will show options to buy the NFT membership in alternative tokens to users automatically on the payment screen. Currently, we will display stable-coin as options such as USDC or USDT. In future, we might open up to checking more routes and enabling more arbitrary swaps.

### How does this work?

We created a new `UnlockSwapPurchaser` contract which facilitates exchanging tokens and purchasing NFTs on behalf of users in a single transaction. This contract has been deployed on all the [networks supported by Unlock](https://docs.unlock-protocol.com/core-protocol/unlock/networks). When a user loads the checkout UI, we immediately check what other currencies they have in their wallets and see if any could be used to perform the purchase. We encode the Lock contract function with parameters as `callData` and pass it to the `swapAndCall` function on the `UnlockSwapPurchaser` contract. This then does the swap, and uses `callData` to call the function with parameters on the PublicLock contract.

This allows us to make the currency swap work with any function on our PublicLock contract if it requires a payment.


Buy NFTs priced in any token you hold using swap and purchase

Introducing Swap & Purchase: Streamlined NFT Buying Experience in Unlock Checkout

<p><img src="/images/blog/swap-and-purchase/swap-and-purchase.png" alt="Checkout Payments page"></p>
<p>We're thrilled to announce the latest addition to Unlock: Swap &#x26; Purchase in Unlock Checkout.</p>
<p>By leveraging an external contract powered by Uniswap, Swap &#x26; Purchase in Unlock Checkout enables a user to buy a membership NFT even if it’s priced in a different currency than the currency a purchaser holds in their wallet. There's no need for users to perform the swap, as it happens natively. For example, if an NFT is priced in USDC but the purchaser only holds MATIC in their wallet, Swap &#x26; Purchase will swap enough MATIC for the correct amount of USDC in a single step, making things easier for the purchaser and enabling the creator to be paid in the currency of their choice. This simplifies the process and reduces friction for both creators and purchasers.</p>
<p><a href="https://app.unlock-protocol.com/checkout?id=bb4a2ae0-2fca-4bdf-bd40-f0c41cde2510">Try it out now</a></p>
<p>In Swap &#x26; Purchase, the Unlock interface will show options to buy the NFT membership in alternative tokens to users automatically on the payment screen. Currently, we will display stable-coin as options such as USDC or USDT. In future, we might open up to checking more routes and enabling more arbitrary swaps.</p>
<h3>How does this work?</h3>
<p>We created a new <code>UnlockSwapPurchaser</code> contract which facilitates exchanging tokens and purchasing NFTs on behalf of users in a single transaction. This contract has been deployed on all the <a href="https://docs.unlock-protocol.com/core-protocol/unlock/networks">networks supported by Unlock</a>. When a user loads the checkout UI, we immediately check what other currencies they have in their wallets and see if any could be used to perform the purchase. We encode the Lock contract function with parameters as <code>callData</code> and pass it to the <code>swapAndCall</code> function on the <code>UnlockSwapPurchaser</code> contract. This then does the swap, and uses <code>callData</code> to call the function with parameters on the PublicLock contract.</p>
<p>This allows us to make the currency swap work with any function on our PublicLock contract if it requires a payment.</p>



Earlier this year we announced a feature we called [wallet-less airdrops](https://unlock-protocol.com/blog/email-recipient). We realized that too many web3 experiences required users to first go through too many complicated steps before they could start enjoying the fun experiences web3 provides. So we introduced wallet-less airdrops, through which users receive an NFT *before* they actually configure a wallet.

Similarly, a few weeks ago, we announced our [web3 event hosting application](https://unlock-protocol.com/blog/events-launch)! It was used by a dozen events at [ETHDenver](https://unlock-protocol.com/blog/ethdenver2023), from DIDDay, to a very cool ShakeShack activation!

One of the pieces of feedback we received from several organizers was that they wanted to also make it trivial for non-crypto users to quickly RSVP for their events, provided that these events were indeed free. So today, we're introducing wallet-less RSVP!

You can try it by [registering for this virtual launch party](https://app.unlock-protocol.com/event?lockAddress=0x069d50f18f13426f7ba74bd20ea04c1fc1943c43&network=5)!

We also added the ability to set the end time for events, and added a calendar invite in the confirmation emails! [Get started now](https://app.unlock-protocol.com/event): organize your web3 meetup, crypto party, or other event using Unlock!


We’ve got a number of new features for events that use Unlock: registering for events without a wallet, event end dates and calendar invites!

Walletless RSVP

<p>Earlier this year we announced a feature we called <a href="https://unlock-protocol.com/blog/email-recipient">wallet-less airdrops</a>. We realized that too many web3 experiences required users to first go through too many complicated steps before they could start enjoying the fun experiences web3 provides. So we introduced wallet-less airdrops, through which users receive an NFT <em>before</em> they actually configure a wallet.</p>
<p>Similarly, a few weeks ago, we announced our <a href="https://unlock-protocol.com/blog/events-launch">web3 event hosting application</a>! It was used by a dozen events at <a href="https://unlock-protocol.com/blog/ethdenver2023">ETHDenver</a>, from DIDDay, to a very cool ShakeShack activation!</p>
<p>One of the pieces of feedback we received from several organizers was that they wanted to also make it trivial for non-crypto users to quickly RSVP for their events, provided that these events were indeed free. So today, we're introducing wallet-less RSVP!</p>
<p>You can try it by <a href="https://app.unlock-protocol.com/event?lockAddress=0x069d50f18f13426f7ba74bd20ea04c1fc1943c43&#x26;network=5">registering for this virtual launch party</a>!</p>
<p>We also added the ability to set the end time for events, and added a calendar invite in the confirmation emails! <a href="https://app.unlock-protocol.com/event">Get started now</a>: organize your web3 meetup, crypto party, or other event using Unlock!</p>
