Thousands of people participate in the [IndieWeb](https://indieweb.org): a growing movement that encourages people to publish on their own site rather than "silo" networks like Facebook and Twitter. [As The New Yorker put it](https://www.newyorker.com/tech/annals-of-technology/can-indie-social-media-save-us):

> Proponents of the IndieWeb offer a fairly straightforward analysis of our current social-media crisis. They frame it in terms of a single question: Who owns the servers? The bulk of our online activity takes places on servers owned by a small number of massive companies. Servers cost money to run. If you’re using a company’s servers without paying for the privilege, then that company must be finding other ways to “extract value” from you—and it’s that quest for large-scale value extraction, they argue, that leads directly to the crises of compromised privacy and engineered addictiveness with which we’re currently grappling.

[Known](https://withknown.com) was one of the first indieweb publishing platforms. It lets anyone host a social media profile on their own webspace. You can respond to posts on other indieweb platforms, or invite visitors to discuss directly on your posts.

Integrating Unlock with Known means allowing these indieweb users to sell memberships to aspects of their sites. Disclaimer: I'm the co-founder of Known and its first user. [I still use it on my website](https://werd.io) - and I want to use Unlock there, too. So it was in my interest to create a plugin.

Here's what I wanted to achieve:

- I want to restrict access to long-form content
- I want to restrict access to commenting
- I don't want Known users to have to write a single line of code

In other words, I want to add a paywall to my long-form posts (but just my long-form posts), and I want comments on _all_ posts to be limited to people who have bought access with Unlock.

If you don't care about how I built this, you can stop now: [the plugin is available to download on GitHub](https://github.com/benwerd/unlock), and you can install it as a plugin in the latest Known platform. Everything is powered using a simple admin panel.

![The Unlock admin panel in Known.](/images/blog/known/unlock-admin.png)

To build the plugin, I used two aspects of Unlock in tandem: the paywall and the Unlock JavaScript API.

![The Unlock paywall on Known.](/images/blog/known/known-unlock.png)

## 1. The paywall.

I added the site-wide ability to attach a lock to my Known site. When this is present, all long-form posts will be protected by that Unlock lock.

![Unlock fields](/images/blog/known/unlock-fields.png)

I also added a per-post lock field. Instead of using a site-wide lock, I could choose to add a lock address to just one or two particularly valuable posts. Then most of my site would remain free, but these posts would be restricted. I could _also_ keep the whole site protected under one lock, but then use a different lock address for a handful of posts. That would allow me to charge extra for access to those.

When Known finds a lock on the page - either site-wide or relating to the post we're trying to view - it loads the paywall code, which looks like this:

```

<script src="https://paywall.unlock-protocol.com/paywall.min.js"
 data-unlock-url="https://paywall.unlock-protocol.com"></script>
<meta name="lock" content="<?= $lockAddress ?>"/>
```

Note that this is identical to the paywall code that anyone can use. The only difference is that we're retrieving the lock
address from the site or post configuration with a short snippet of PHP.

## 2. The Unlock API.

On every post, I restricted access to commenting.

Here, I wanted to display my own UI, rather than using a built-in Unlock app. So I needed to use a combination of the
Unlock JavaScript API and Known's back-end PHP library.

To begin with, I made sure both the Unlock configuration and library were loaded in the `<head />` section of each page appropriately.

First the configuration object:

```
<script>
 var unlockProtocolConfig = {
 locks: {
 '<?=$lockAddress?>': {
 name: '<?=\Idno\Core\Idno::site()->config()->getTitle()?> Members',
 },
 },
 icon: 'https://unlock-protocol.com/images/svg/unlock-word-mark.svg',
 callToAction: {
 default:
 'Members can leave comments and participate in discussion.',
 },
 }
</script>
```

And then the library itself:

```
<script>
 (function (d, s) {
 var js = d.createElement(s),
 sc = d.getElementsByTagName(s)[0];
 js.src = "https://paywall.unlock-protocol.com/unlock.latest.min.js";
 sc.parentNode.insertBefore(js, sc);
 }(document, "script"));
</script>
```

I then created a replacement comment template in Known. Here, I loaded HTML for the comment form into a variable called `commentForm`; I also added HTML for a link with a call to action into a variable called `commentCta`.

```
<div id="comment-form"></div>
<script>
 // Load JS variable values from PHP variables
 var commentForm = <?=json_encode($commentForm)?>;
 var commentCta = <?=json_encode($commentCta)?>;

 // Listen to Unlock protocol API
 window.addEventListener('unlockProtocol', function (e) {
 var state = e.detail
 if (state === 'unlocked') {
 $('#comment-form').html(commentForm);
 }
 if (state === 'locked') {
 $('#comment-form').html(commentCta)
 }
 })
</script>
```

What's happening here? Once the Unlock protocol handler is loaded (which we did by adding the library and configuration above), all we need to do is listen for events generated by `unlockProtocol`. If `event.detail` is equal to `unlocked`, we know the current user has access to the lock. Conversely, if `event.detail` is equal to `locked`, we know the current user _doesn't_ have access.

The form HTML is purely for Known, so I won't go into it here, but it's worth looking more closely at the CTA:

```
<div class="unlock-cta">
 <a href="#" onclick="window.unlockProtocol && unlockProtocol.loadCheckoutModal()">
 Purchase access to leave comments.</a>
</div>
```

On click, I check that `window.unlockProtocol` exists (i.e., the library has been loaded), and then load a provided method called `unlockProtocol.loadCheckoutModal()` that loads a modal containing the Unlock lock. The text shouldn't be a surprise: I set it in the `callToAction` of my configuration section.

![Unlock modal](/images/blog/known/unlock-modal.png)

And that's all I need to do. The Unlock API manages the purchase process and all of the access control. It's as lightweight as it can be.

Have you integrated Unlock into your application? We'd love to hear from you. You can email us at [hello@unlock-protocol.com](mailto:hello@unlock-protocol.com) or come say hi on [our Discord](https://discord.gg/Ah6ZEJyTDp).

The Unlock API is flexible and easy to use. Now any Known user can use Unlock on their website with a simple plugin. Here's how we did it.

How I added the Unlock protocol to an open source publishing platform quickly and easily.

Integrating Unlock with Known

Thousands of people participate in the <a href="https://indieweb.org">IndieWeb</a>: a growing movement that encourages people to publish on their own site rather than "silo" networks like Facebook and Twitter. <a href="https://www.newyorker.com/tech/annals-of-technology/can-indie-social-media-save-us">As The New Yorker put it</a>:
<blockquote>
Proponents of the IndieWeb offer a fairly straightforward analysis of our current social-media crisis. They frame it in terms of a single question: Who owns the servers? The bulk of our online activity takes places on servers owned by a small number of massive companies. Servers cost money to run. If you’re using a company’s servers without paying for the privilege, then that company must be finding other ways to “extract value” from you—and it’s that quest for large-scale value extraction, they argue, that leads directly to the crises of compromised privacy and engineered addictiveness with which we’re currently grappling.
</blockquote>
<a href="https://withknown.com">Known</a> was one of the first indieweb publishing platforms. It lets anyone host a social media profile on their own webspace. You can respond to posts on other indieweb platforms, or invite visitors to discuss directly on your posts.
Integrating Unlock with Known means allowing these indieweb users to sell memberships to aspects of their sites. Disclaimer: I'm the co-founder of Known and its first user. <a href="https://werd.io">I still use it on my website</a> - and I want to use Unlock there, too. So it was in my interest to create a plugin.
Here's what I wanted to achieve:
<ul>
<li>I want to restrict access to long-form content</li>
<li>I want to restrict access to commenting</li>
<li>I don't want Known users to have to write a single line of code</li>
</ul>
In other words, I want to add a paywall to my long-form posts (but just my long-form posts), and I want comments on all posts to be limited to people who have bought access with Unlock.
If you don't care about how I built this, you can stop now: <a href="https://github.com/benwerd/unlock">the plugin is available to download on GitHub</a>, and you can install it as a plugin in the latest Known platform. Everything is powered using a simple admin panel.
<img src="/images/blog/known/unlock-admin.png" alt="The Unlock admin panel in Known.">
To build the plugin, I used two aspects of Unlock in tandem: the paywall and the Unlock JavaScript API.
<img src="/images/blog/known/known-unlock.png" alt="The Unlock paywall on Known.">
<h2>1. The paywall.</h2>
I added the site-wide ability to attach a lock to my Known site. When this is present, all long-form posts will be protected by that Unlock lock.
<img src="/images/blog/known/unlock-fields.png" alt="Unlock fields">
I also added a per-post lock field. Instead of using a site-wide lock, I could choose to add a lock address to just one or two particularly valuable posts. Then most of my site would remain free, but these posts would be restricted. I could also keep the whole site protected under one lock, but then use a different lock address for a handful of posts. That would allow me to charge extra for access to those.
When Known finds a lock on the page - either site-wide or relating to the post we're trying to view - it loads the paywall code, which looks like this:
<pre><code>&#x3C;!-- Include this script in the &#x3C;head> section of your page -->
&#x3C;script src="https://paywall.unlock-protocol.com/paywall.min.js"
 data-unlock-url="https://paywall.unlock-protocol.com">&#x3C;/script>
&#x3C;meta name="lock" content="&#x3C;?= $lockAddress ?>"/>
</code></pre>
Note that this is identical to the paywall code that anyone can use. The only difference is that we're retrieving the lock
address from the site or post configuration with a short snippet of PHP.
<h2>2. The Unlock API.</h2>
On every post, I restricted access to commenting.
Here, I wanted to display my own UI, rather than using a built-in Unlock app. So I needed to use a combination of the
Unlock JavaScript API and Known's back-end PHP library.
To begin with, I made sure both the Unlock configuration and library were loaded in the <code>&#x3C;head /></code> section of each page appropriately.
First the configuration object:
<pre><code>&#x3C;script>
 var unlockProtocolConfig = {
 locks: {
 '&#x3C;?=$lockAddress?>': {
 name: '&#x3C;?=\Idno\Core\Idno::site()->config()->getTitle()?> Members',
 },
 },
 icon: 'https://unlock-protocol.com/images/svg/unlock-word-mark.svg',
 callToAction: {
 default:
 'Members can leave comments and participate in discussion.',
 },
 }
&#x3C;/script>
</code></pre>
And then the library itself:
<pre><code>&#x3C;script>
 (function (d, s) {
 var js = d.createElement(s),
 sc = d.getElementsByTagName(s)[0];
 js.src = "https://paywall.unlock-protocol.com/unlock.latest.min.js";
 sc.parentNode.insertBefore(js, sc);
 }(document, "script"));
&#x3C;/script>
</code></pre>
I then created a replacement comment template in Known. Here, I loaded HTML for the comment form into a variable called <code>commentForm</code>; I also added HTML for a link with a call to action into a variable called <code>commentCta</code>.
<pre><code>&#x3C;div id="comment-form">&#x3C;/div>
&#x3C;script>
 // Load JS variable values from PHP variables
 var commentForm = &#x3C;?=json_encode($commentForm)?>;
 var commentCta = &#x3C;?=json_encode($commentCta)?>;

 // Listen to Unlock protocol API
 window.addEventListener('unlockProtocol', function (e) {
 var state = e.detail
 if (state === 'unlocked') {
 $('#comment-form').html(commentForm);
 }
 if (state === 'locked') {
 $('#comment-form').html(commentCta)
 }
 })
&#x3C;/script>
</code></pre>
What's happening here? Once the Unlock protocol handler is loaded (which we did by adding the library and configuration above), all we need to do is listen for events generated by <code>unlockProtocol</code>. If <code>event.detail</code> is equal to <code>unlocked</code>, we know the current user has access to the lock. Conversely, if <code>event.detail</code> is equal to <code>locked</code>, we know the current user doesn't have access.
The form HTML is purely for Known, so I won't go into it here, but it's worth looking more closely at the CTA:
<pre><code>&#x3C;div class="unlock-cta">
 &#x3C;a href="#" onclick="window.unlockProtocol &#x26;&#x26; unlockProtocol.loadCheckoutModal()">
 Purchase access to leave comments.&#x3C;/a>
&#x3C;/div>
</code></pre>
On click, I check that <code>window.unlockProtocol</code> exists (i.e., the library has been loaded), and then load a provided method called <code>unlockProtocol.loadCheckoutModal()</code> that loads a modal containing the Unlock lock. The text shouldn't be a surprise: I set it in the <code>callToAction</code> of my configuration section.
<img src="/images/blog/known/unlock-modal.png" alt="Unlock modal">
And that's all I need to do. The Unlock API manages the purchase process and all of the access control. It's as lightweight as it can be.
Have you integrated Unlock into your application? We'd love to hear from you. You can email us at <a href="mailto:hello@unlock-protocol.com">hello@unlock-protocol.com</a> or come say hi on <a href="https://discord.gg/Ah6ZEJyTDp">our Discord</a>.


A recipe to go from zero to one cannot exist. Creating a company, a team, a product or a protocol require a lot of work and faith. Our goal is ambitious, but it can only be achieved an incredible amount of small steps (4000 [Pull Requests](https://github.com/unlock-protocol/unlock/pulls) as of Tuesday!).

This week, we took some time to think about our **mission**, which is what we do, our **vision**, which is why we do it, and our **values**, which describe how we do it. We got some help and it took us a full day, but this work will help us in each decision and will act as a "scaffold" for the whole team.

## Our Vision

We believe that, now, most creators are not able to capture enough of the value that they create. Open source developers, musicians, writers, or even curators provide incredible value for all users of the internet and beyond. But we also have to acknowledge that most of them are not being rewarded for that work, and when they are, it is often through gatekeepers: middlemen who set the terms and too often end up competing with them.

We know there is a better way. This is our vision:

> “Every creator can make a sustainable living from their work, while respecting the time, privacy and health of their community.”

## Our Mission

In order to make that vision a reality, we believe it starts with creators and this is why our mission is the following:

> "We empower creators to capture the value they create for their community, on their own terms."

## Our Values

Values define "how" we want to achieve our mission and realize the vision. They provide principles that we want to live by, both internally, but also externally, with users of the protocol and members of our own community. Here are the ones we chose:

- Collaborative
- Human Centered
- Mission Driven
- Simple
- Transparent

Of course, in that list there are things that we already apply, and others which are, at least for now, more aspirational.

Based on that list, it should be pretty clear that your input matters to us. We hope that you'll provide us guidance on how to adopt these principles during our journey! Please, reach out to us, in comments below, on [Discord](https://discord.gg/Ah6ZEJyTDp), or even privately using the Intercom widget in the lower right corner of this page.


Identifying Mission, Vision and Values informs business strategy and paints a holistic and accurate picture of a business.

We empower creators to capture the value they create for their community, on their own terms

Mission, Vision and Values

A recipe to go from zero to one cannot exist. Creating a company, a team, a product or a protocol require a lot of work and faith. Our goal is ambitious, but it can only be achieved an incredible amount of small steps (4000 <a href="https://github.com/unlock-protocol/unlock/pulls">Pull Requests</a> as of Tuesday!).
This week, we took some time to think about our mission, which is what we do, our vision, which is why we do it, and our values, which describe how we do it. We got some help and it took us a full day, but this work will help us in each decision and will act as a "scaffold" for the whole team.
<h2>Our Vision</h2>
We believe that, now, most creators are not able to capture enough of the value that they create. Open source developers, musicians, writers, or even curators provide incredible value for all users of the internet and beyond. But we also have to acknowledge that most of them are not being rewarded for that work, and when they are, it is often through gatekeepers: middlemen who set the terms and too often end up competing with them.
We know there is a better way. This is our vision:
<blockquote>
“Every creator can make a sustainable living from their work, while respecting the time, privacy and health of their community.”
</blockquote>
<h2>Our Mission</h2>
In order to make that vision a reality, we believe it starts with creators and this is why our mission is the following:
<blockquote>
"We empower creators to capture the value they create for their community, on their own terms."
</blockquote>
<h2>Our Values</h2>
Values define "how" we want to achieve our mission and realize the vision. They provide principles that we want to live by, both internally, but also externally, with users of the protocol and members of our own community. Here are the ones we chose:
<ul>
<li>Collaborative</li>
<li>Human Centered</li>
<li>Mission Driven</li>
<li>Simple</li>
<li>Transparent</li>
</ul>
Of course, in that list there are things that we already apply, and others which are, at least for now, more aspirational.
Based on that list, it should be pretty clear that your input matters to us. We hope that you'll provide us guidance on how to adopt these principles during our journey! Please, reach out to us, in comments below, on <a href="https://discord.gg/Ah6ZEJyTDp">Discord</a>, or even privately using the Intercom widget in the lower right corner of this page.


On June 21st, 2019, the team at [Betaworks Studios](https://betaworks-studios.com/) invited us to talk about Non Fungible Tokens.

They are a type of crypto token which aims at represented unique (or rare) "things". This is intentionnaly vague because they can be used to represent many many things, both virtual and physical.

For example, Non Fungible Tokens can be used to represent membership. If you are a member to Unlock's blog, then you own a Non Fungible Token called a "key".

Among other things, this key will let you access access the slides of the presentation below!


Non Fungible are one of the largest emerging token categories in the crypto asset world. We presented an intro to them at Betaworks Studios!

Non Fungible are one of the largest emerging token categories in the crypto asset world.

Non Fungible Tokens at Betaworks Studios

On June 21st, 2019, the team at <a href="https://betaworks-studios.com/">Betaworks Studios</a> invited us to talk about Non Fungible Tokens.
They are a type of crypto token which aims at represented unique (or rare) "things". This is intentionnaly vague because they can be used to represent many many things, both virtual and physical.
For example, Non Fungible Tokens can be used to represent membership. If you are a member to Unlock's blog, then you own a Non Fungible Token called a "key".
Among other things, this key will let you access access the slides of the presentation below!


The difference between the web and native applications is the presence of **links**. These links are the reason why the web is a "network", as they connect pages together, making a graph. Google and its PageRank algorithm have leveraged that graph to rank websites, by assuming that the sites which have the most links are the most relevant.

![Use one Unlock lock for a variety of services and products.](/images/blog/protocol-for-memberships.png)

## Memberships > Attention

However, since the beginning, these links have also formed **communities**. Websites which discuss the same topics tend to link to each other, creating de-facto communities of interest. The social web reinforced that trend: people following each other formed more communities. Creators gathered groups of users around their work. Whether they are blogger or journalists, musician or even developers, they formed groups which attracted users because of their values, the content they produce, or even the tools that were offered to the members of the community.

Up until now, _we monetized the web through attention_. The creators who were able to "steal" the most would be paid the most. We're obviously reaching the limits of that model. It is time to start considering that these communities have value for their members... and that these members actually want to contribute to their communities as well.

## A protocol for memberships

Unlock is a protocol for memberships. Creators have locks which define the terms of the membership (price, duration, quantity, or even currency!) and consumers can purchase keys to these locks.

In practice, that means that the protocol empowers creators (or anyone, really!) to create locks for their communities. It's an open protocol, so anyone can participate: there is no gatekeeper or middleman.

Locks themselves can be used for many different things, limiting access to content (paywall...), to features (software licenses...), or even status (patronage...).

## Leading by example!

We're putting [our money where our mouth is](/blog/crypto-first/). Starting today, we've added a lock to this website. We decided to **limit access to the comments** to the members of the community.

You can unlock your membership by clicking on the bar at the bottom below (we actually set a price of 0 Ether, so you only pay for gas fees). Once you have a key, you will be able to read and write comments.

An important thing to note is that once the transaction has been confirmed, you will receive a Non Fungible Token on your crypto wallet. Like any other token, it is yours, and you can sell it, using [OpenSea](https://opensea.io/), for example.


The Unlock protocol provides a way for people to show their support and access exclusive content, features, or even status. It is a web-native way for creators to monetize their work.

Monetizing creation by leveraging membership to communities

A Protocol for Membership

The difference between the web and native applications is the presence of links. These links are the reason why the web is a "network", as they connect pages together, making a graph. Google and its PageRank algorithm have leveraged that graph to rank websites, by assuming that the sites which have the most links are the most relevant.
<img src="/images/blog/protocol-for-memberships.png" alt="Use one Unlock lock for a variety of services and products.">
<h2>Memberships > Attention</h2>
However, since the beginning, these links have also formed communities. Websites which discuss the same topics tend to link to each other, creating de-facto communities of interest. The social web reinforced that trend: people following each other formed more communities. Creators gathered groups of users around their work. Whether they are blogger or journalists, musician or even developers, they formed groups which attracted users because of their values, the content they produce, or even the tools that were offered to the members of the community.
Up until now, we monetized the web through attention. The creators who were able to "steal" the most would be paid the most. We're obviously reaching the limits of that model. It is time to start considering that these communities have value for their members... and that these members actually want to contribute to their communities as well.
<h2>A protocol for memberships</h2>
Unlock is a protocol for memberships. Creators have locks which define the terms of the membership (price, duration, quantity, or even currency!) and consumers can purchase keys to these locks.
In practice, that means that the protocol empowers creators (or anyone, really!) to create locks for their communities. It's an open protocol, so anyone can participate: there is no gatekeeper or middleman.
Locks themselves can be used for many different things, limiting access to content (paywall...), to features (software licenses...), or even status (patronage...).
<h2>Leading by example!</h2>
We're putting <a href="/blog/crypto-first/">our money where our mouth is</a>. Starting today, we've added a lock to this website. We decided to limit access to the comments to the members of the community.
You can unlock your membership by clicking on the bar at the bottom below (we actually set a price of 0 Ether, so you only pay for gas fees). Once you have a key, you will be able to read and write comments.
An important thing to note is that once the transaction has been confirmed, you will receive a Non Fungible Token on your crypto wallet. Like any other token, it is yours, and you can sell it, using <a href="https://opensea.io/">OpenSea</a>, for example.

![Dashboard Lock](/images/blog/erc20-locks/use-dai.jpg)

When creators deploy their locks using our dashboard, they can chose the following:

- the name of their locks
- how long each key is valid (from seconds to centuries!)
- how many keys they are selling (with the ability to sell an unlimited amount)
- and more importantly, the price of keys

Up until today, the price of the keys had to be in Ether. Today, we're happy to announce that we now support any ERC20 token as the currency for the price. As a creator you can now sell access to your content or features inside of your (d)applications using BNB, MKR or even BAT...

## Using stable coins

Out of ERC20 tokens, there is a category of tokens which is special: stable coins. These tokens have a value that is designed to be stable, most often against US dollars. Some of them are actually backed by financial organizations who guarantee a 1 to 1 exchange (such as USDC for example), while others are based on onchain collaterals (DAI is a good example of that!), while finally, a 3rd category is based on seigniorage: the supply expands and retracts based on price fluctuations. Learn more about stable coins with [this overview](https://multicoin.capital/2018/01/17/an-overview-of-stablecoins/) from Multicoin.

A lot of the creators that we spoke to were worried about the use of fluctuating currencies. If the price went down, they would lose some of their revenues, and if it went up, they were rightfully worried that their customers may not end up buying keys from them... as they could be waiting for appreciation of their tokens.

We believe that many locks will end up being priced using stable coins, which is why our dashboard UI will let creators pick DAI as the currency1.

## Bringing utility to utility coins!

We also strongly believe that many ERC20 currencies are "community" currencies. Their value is rooted in the fact that it is a very specific use. For example, MKR is a governance token which lets owners of it vote on changes in the Maker systems.

Now, nothing says that the MKR tokens, which are actively traded on several exchanges could not be used for other purposes, such as purchasing access keys. For example, Maker could organize a launch party for their upcoming multi-collateral currency where tickets are sold using MKR. For this, they could use Unlock's [ticket application](https://tickets.unlock-protocol.com/)...

## Get started today

Head out to the [creator dashboard](https://unlock-protocol.com/) now and click on the _Create Lock_ Button:

![Create a Lock](/images/blog/erc20-locks/create-lock.png)

Then, select DAI as the currency when picking up a price:

![Create a Lock](/images/blog/erc20-locks/select-dai.png)

Choose how much you want to charge (you can still change that later, but not the currency...). And hit submit. Once that transaction has been mined, your lock has been deployed!

Once you have embedded the lock on your page, your readers are offered the ability to Unlock it:

![A DAI lock](/images/blog/erc20-locks/dai-lock.png)

When clicking on it, they are required to approve 2 transactions (the ERC20 could be a bit simpler... but we have ideas on how to solve that!):

1. They need to approve the lock to withdraw some of their DAI (just the amount for the key purchase!):

![Approve the ERC20 transfer](/images/blog/erc20-locks/approve-withdraw-erc20.png)

2. Actually purchase the key (the lock contract will withdraw the right ERC20 balance):

![Purchasing the key](/images/blog/erc20-locks/purchase-key.png)

Once the transaction as been confirmed, the customer will receive their non fungible token!

We're very excited about this release, because it opens the door to several other releases in the next coming weeks! Stay tuned ;)

1 Reach out if you need to deploy a lock using another ERC20 of your choice: we can help, even if we wanted to keep our UI minimalistic.

A lot of the creators that we spoke with were concerned by the volatile nature of Ether when using it to price their keys: we needed to support stable coins. The ERC20 standard is a way to create tokens which are all compatible, even though they may have different implementations.

Creators can chose any Ethereum based token when they sell keys to their locks.

Introducing ERC20 Locks

<img src="/images/blog/erc20-locks/use-dai.jpg" alt="Dashboard Lock">
When creators deploy their locks using our dashboard, they can chose the following:
<ul>
<li>the name of their locks</li>
<li>how long each key is valid (from seconds to centuries!)</li>
<li>how many keys they are selling (with the ability to sell an unlimited amount)</li>
<li>and more importantly, the price of keys</li>
</ul>
Up until today, the price of the keys had to be in Ether. Today, we're happy to announce that we now support any ERC20 token as the currency for the price. As a creator you can now sell access to your content or features inside of your (d)applications using BNB, MKR or even BAT...
<h2>Using stable coins</h2>
Out of ERC20 tokens, there is a category of tokens which is special: stable coins. These tokens have a value that is designed to be stable, most often against US dollars. Some of them are actually backed by financial organizations who guarantee a 1 to 1 exchange (such as USDC for example), while others are based on onchain collaterals (DAI is a good example of that!), while finally, a 3rd category is based on seigniorage: the supply expands and retracts based on price fluctuations. Learn more about stable coins with <a href="https://multicoin.capital/2018/01/17/an-overview-of-stablecoins/">this overview</a> from Multicoin.
A lot of the creators that we spoke to were worried about the use of fluctuating currencies. If the price went down, they would lose some of their revenues, and if it went up, they were rightfully worried that their customers may not end up buying keys from them... as they could be waiting for appreciation of their tokens.
We believe that many locks will end up being priced using stable coins, which is why our dashboard UI will let creators pick DAI as the currency1.
<h2>Bringing utility to utility coins!</h2>
We also strongly believe that many ERC20 currencies are "community" currencies. Their value is rooted in the fact that it is a very specific use. For example, MKR is a governance token which lets owners of it vote on changes in the Maker systems.
Now, nothing says that the MKR tokens, which are actively traded on several exchanges could not be used for other purposes, such as purchasing access keys. For example, Maker could organize a launch party for their upcoming multi-collateral currency where tickets are sold using MKR. For this, they could use Unlock's <a href="https://tickets.unlock-protocol.com/">ticket application</a>...
<h2>Get started today</h2>
Head out to the <a href="https://unlock-protocol.com/">creator dashboard</a> now and click on the Create Lock Button:
<img src="/images/blog/erc20-locks/create-lock.png" alt="Create a Lock">
Then, select DAI as the currency when picking up a price:
<img src="/images/blog/erc20-locks/select-dai.png" alt="Create a Lock">
Choose how much you want to charge (you can still change that later, but not the currency...). And hit submit. Once that transaction has been mined, your lock has been deployed!
Once you have embedded the lock on your page, your readers are offered the ability to Unlock it:
<img src="/images/blog/erc20-locks/dai-lock.png" alt="A DAI lock">
When clicking on it, they are required to approve 2 transactions (the ERC20 could be a bit simpler... but we have ideas on how to solve that!):
<ol>
<li>They need to approve the lock to withdraw some of their DAI (just the amount for the key purchase!):</li>
</ol>
<img src="/images/blog/erc20-locks/approve-withdraw-erc20.png" alt="Approve the ERC20 transfer">
<ol start="2">
<li>Actually purchase the key (the lock contract will withdraw the right ERC20 balance):</li>
</ol>
<img src="/images/blog/erc20-locks/purchase-key.png" alt="Purchasing the key">
Once the transaction as been confirmed, the customer will receive their non fungible token!
We're very excited about this release, because it opens the door to several other releases in the next coming weeks! Stay tuned ;)
1 Reach out if you need to deploy a lock using another ERC20 of your choice: we can help, even if we wanted to keep our UI minimalistic.


![Use one Unlock lock for a variety of services and products.](/images/blog/multiuselocks/hero.jpg)

One incredibly powerful thing about using Unlock is that one key can access anything that's behind a lock it has access to. That means you can place the same lock in multiple places or even use it for different purposes (as we did) and let a user who as that one key access everything. So what did we do?

![The NFT Dev Meetup ticket page.](/images/blog/multiuselocks/nft-ticket-page.jpg)

We sold tickets to the NFT Dev Meetup during NYC Blockchain Week through [our ticket app](https://tickets.unlock-protocol.com/event/0x5865Ff2CBd045Ef1cfE19739df19E83B32b783b4) (still in beta) and then allowed ticket holders to also access [the livestream of the event](https://unlock-protocol.com/blog/nft-dev-meetup/).

Without Unlock, complicated. With Unlock piece of cake.

We created a lock on the Unlock dashboard …

![The NFT events lock on the dashboard.](/images/blog/multiuselocks/nft-lock-dashboard.jpg)

We used that lock to create a ticket page …

![Creating an event page with the lock.](/images/blog/multiuselocks/nft-event-creation.jpg)

… and then used the embed code from that same lock on [the event blog post](https://unlock-protocol.com/blog/nft-dev-meetup/).

![The lock's embed code.](/images/blog/multiuselocks/nft-lock-embed.jpg)

Checkout the [tickets page](https://tickets.unlock-protocol.com/event/0x5865Ff2CBd045Ef1cfE19739df19E83B32b783b4) and [the locked blog post](https://unlock-protocol.com/blog/nft-dev-meetup/) with the event video. Want to really try it out? You can still buy a ticket to unlock the video (disclaimer: the sound isn’t great – and it mostly serves as proof of concept for locking the page).

Want to do this for your event or content? [We’re all ears!](mailto:hello@unlock-protocol.com)


Find out how a single key together with your wallet can unlock anything from tickets to content.

One key can serve many purposes

Multi Use Locks

<img src="/images/blog/multiuselocks/hero.jpg" alt="Use one Unlock lock for a variety of services and products.">
One incredibly powerful thing about using Unlock is that one key can access anything that's behind a lock it has access to. That means you can place the same lock in multiple places or even use it for different purposes (as we did) and let a user who as that one key access everything. So what did we do?
<img src="/images/blog/multiuselocks/nft-ticket-page.jpg" alt="The NFT Dev Meetup ticket page.">
We sold tickets to the NFT Dev Meetup during NYC Blockchain Week through <a href="https://tickets.unlock-protocol.com/event/0x5865Ff2CBd045Ef1cfE19739df19E83B32b783b4">our ticket app</a> (still in beta) and then allowed ticket holders to also access <a href="https://unlock-protocol.com/blog/nft-dev-meetup/">the livestream of the event</a>.
Without Unlock, complicated. With Unlock piece of cake.
We created a lock on the Unlock dashboard …
<img src="/images/blog/multiuselocks/nft-lock-dashboard.jpg" alt="The NFT events lock on the dashboard.">
We used that lock to create a ticket page …
<img src="/images/blog/multiuselocks/nft-event-creation.jpg" alt="Creating an event page with the lock.">
… and then used the embed code from that same lock on <a href="https://unlock-protocol.com/blog/nft-dev-meetup/">the event blog post</a>.
<img src="/images/blog/multiuselocks/nft-lock-embed.jpg" alt="The lock&#x27;s embed code.">
Checkout the <a href="https://tickets.unlock-protocol.com/event/0x5865Ff2CBd045Ef1cfE19739df19E83B32b783b4">tickets page</a> and <a href="https://unlock-protocol.com/blog/nft-dev-meetup/">the locked blog post</a> with the event video. Want to really try it out? You can still buy a ticket to unlock the video (disclaimer: the sound isn’t great – and it mostly serves as proof of concept for locking the page).
Want to do this for your event or content? <a href="mailto:hello@unlock-protocol.com">We’re all ears!</a>

![Optimistic Unlocking in action.](/images/blog/nftdevmeetup/hero.jpg)

We’re doing something different! By now you’ve probably been to a few too many after-parties. Let's not even talk about Consensus - did you see how packed the hallways were?

Instead, we’re going to have an informal gameshow party where we pit eight blockchain fanatics against each other to debate fiery topics from within the industry. All in good fun and all for laughs!

Meet us at 6:30PM on May 16th, at the Bushwick Generator.

If you need any help (or Eth) to purchase your ticket, please get in touch with us via the Telegram group below.

Bushwick Generator, 215 Moore St, Brooklyn

<figure class="video_container">
<iframe width="560" height="315" src="https://www.youtube.com/embed/Qq4bBs-zPZw" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</figure>

More info and a livestream for registred participants.

Livestream of the NFT Dev Meetup

NFT Dev Meetup

<img src="/images/blog/nftdevmeetup/hero.jpg" alt="Optimistic Unlocking in action.">
We’re doing something different! By now you’ve probably been to a few too many after-parties. Let's not even talk about Consensus - did you see how packed the hallways were?
Instead, we’re going to have an informal gameshow party where we pit eight blockchain fanatics against each other to debate fiery topics from within the industry. All in good fun and all for laughs!
Meet us at 6:30PM on May 16th, at the Bushwick Generator.
If you need any help (or Eth) to purchase your ticket, please get in touch with us via the Telegram group below.
Bushwick Generator, 215 Moore St, Brooklyn
<figure class="video_container">
<iframe width="560" height="315" src="https://www.youtube.com/embed/Qq4bBs-zPZw" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</figure>


![NFT meetup during crypto week 2019](https://s3.amazonaws.com/assets.unlock-protocol.com/NFTEventLogos.png)

We are mission driven: we strongly believe that the [web's business model is broken](https://unlock-protocol.com/blog/ad-supported-web/), but more importantly, that it can be replaced with a [much healthier one](https://unlock-protocol.com/blog/its-time-to-unlock-the-web/), and we're building it, key after key, lock after lock.

As technologists, we also know that _dogfooding_ is important: it's by using the technology we build that we can understand it better. We are building new mental models as we actually experience these new products and protocols.

For example, we strongly believe that the Unlock Protocol can be used to **sell tickets** to concerts, conferences, or parties. To test that hypothesis, we are co-organizing an event here, in NYC during blockchain week, with our friends at [Dapper Labs](https://www.dapperlabs.com/), [OpenSea](https://opensea.io/), [SuperRare](https://superrare.co/) or [Quantstamp](https://quantstamp.com/).

We’re going to have an informal gameshow party where we pit eight blockchain fanatics (us!) against each other to debate fiery topics from within the industry. All in good fun and all for laughs: you [should get a ticket](https://tickets.unlock-protocol.com/event/0x5865Ff2CBd045Ef1cfE19739df19E83B32b783b4)!

As you've understood by now, this event is locked by a lock, at [0x5865ff2cbd045ef1cfe19739df19e83b32b783b4](https://etherscan.io/address/0x5865ff2cbd045ef1cfe19739df19e83b32b783b4). When you purchase a ticket, you actually acquire a Non Fungible Token, which you could trade on OpenSea, for example...

Of course, this is a fairly new experience, but if you already have your crypto wallet (hint: you should!), then, it is actually a lot more straightforward than getting using one of the "legacy" ticket companies: we do not ask for anything and no need to type these 16 credit card digits.
Now that you own a NFT, your ticket (or your key as we call it), on top of being tradable, can also be used to unlock more things with the same lock!

We'd love to see you there, and, maybe even more importantly to hear your feedback. What are things we should make better?


At Unlock, like many in the crypto and blockchain world, we believe that a better web is possible... and we're building it. But we also understand that dreaming and building is not enough.

Be the change you want to see in the world

Crypto First

<img src="https://s3.amazonaws.com/assets.unlock-protocol.com/NFTEventLogos.png" alt="NFT meetup during crypto week 2019">
We are mission driven: we strongly believe that the <a href="https://unlock-protocol.com/blog/ad-supported-web/">web's business model is broken</a>, but more importantly, that it can be replaced with a <a href="https://unlock-protocol.com/blog/its-time-to-unlock-the-web/">much healthier one</a>, and we're building it, key after key, lock after lock.
As technologists, we also know that dogfooding is important: it's by using the technology we build that we can understand it better. We are building new mental models as we actually experience these new products and protocols.
For example, we strongly believe that the Unlock Protocol can be used to sell tickets to concerts, conferences, or parties. To test that hypothesis, we are co-organizing an event here, in NYC during blockchain week, with our friends at <a href="https://www.dapperlabs.com/">Dapper Labs</a>, <a href="https://opensea.io/">OpenSea</a>, <a href="https://superrare.co/">SuperRare</a> or <a href="https://quantstamp.com/">Quantstamp</a>.
We’re going to have an informal gameshow party where we pit eight blockchain fanatics (us!) against each other to debate fiery topics from within the industry. All in good fun and all for laughs: you <a href="https://tickets.unlock-protocol.com/event/0x5865Ff2CBd045Ef1cfE19739df19E83B32b783b4">should get a ticket</a>!
As you've understood by now, this event is locked by a lock, at <a href="https://etherscan.io/address/0x5865ff2cbd045ef1cfe19739df19e83b32b783b4">0x5865ff2cbd045ef1cfe19739df19e83b32b783b4</a>. When you purchase a ticket, you actually acquire a Non Fungible Token, which you could trade on OpenSea, for example...
Of course, this is a fairly new experience, but if you already have your crypto wallet (hint: you should!), then, it is actually a lot more straightforward than getting using one of the "legacy" ticket companies: we do not ask for anything and no need to type these 16 credit card digits.
Now that you own a NFT, your ticket (or your key as we call it), on top of being tradable, can also be used to unlock more things with the same lock!
We'd love to see you there, and, maybe even more importantly to hear your feedback. What are things we should make better?


![Optimistic Unlocking in action.](/images/blog/hellooptimisticunlocking/hero.jpg)

At Unlock we’re all about making transactions on the web seamless and effortless. Blockchain transactions have lots of incredible features, from low cost to permissionless, but the strong suit of blockchain technology – its safety features around immutable data also means every transaction needs to be confirmed by miners. This can take time. Generally Ethereum transactions are considered final after they’ve been confirmed by 12 miners, which can take a few minutes and longer depending on how busy the network is. This presents 2 challenges: not only is this slow, but it is very hard to predict accurately.

The reason we do this is to ensure that funds aren’t double spent (accidentally or purposefully). Theoretically users could spend their Ether in one place and while that transaction is still being confirmed spend it in another place. In this instance the transaction that’s confirmed first would go through and the other would fail.

![Optimistic Unlocking in action.](/images/blog/hellooptimisticunlocking/locked.jpg)

One of our core beliefs is that the challenge most creators are facing is not so much fraud than it is friction. Increasing conversion rates will have a much larger impact on their revenue than fighting the rare cases of fraud. So instead of adding friction or delays to all of the benevolent users in order to stop a few fraudsters, we believe it’s much more beneficial to make it easier to unlock content, even if that means that a small number of people will find ways to “cheat” creators by a few dollars.

We want to trust people! And we’re optimistic that they actually want the content and are willing to pay for it fair and square. Meet Optimistic Unlocking!

We’re working on an algorithm that will determine if a transaction is likely to go through or not, based on the user's balance, their previous transactions, and a few other factors. If it’s likely to go through, the content immediately unlocks while it’s still being mined and confirmed in the background. We display a status bar and notifications, and a confirmation once the transaction went through.

![Optimistic Unlocking in action.](/images/blog/hellooptimisticunlocking/confirming.jpg)

A confirmed purchase will soon show a new flag with the duration of your subscription and let you click through to your keychain where you can review your purchases.

![Optimistic Unlocking in action.](/images/blog/hellooptimisticunlocking/subscribed.jpg)

Should something unexpected happen – like the transaction is taking longer than usual to be confirmed, as would happen if funds were accidentally double spent, the content gets automatically locked again. The user is informed that there was an issue with the transaction and is led through the default purchase flow.

We could also detect new transactions sent by users with a pending transaction, and immediately re-lock the content because we then know that their key purchase is likely to not go through!

If the algorithm determined this is a transaction that is unlikely to be confirmed (hopefully a rare case), the user is presented with the default purchase flow where they have to wait for the transaction to be confirmed by 12 miners. Not the worst of scenarios - it just requires a bit of patience.

![Optimistic Unlocking in action.](/images/blog/hellooptimisticunlocking/stages.jpg)

In a nutshell, Optimistic Unlocking makes the entire purchasing experience better by allowing instant unlocking while still maintaining a high degree of security. A much nicer user experience gives users more freedom and creators more conversion, all with minimal risk.

That’s Optimistic Unlocking – and one step towards our bigger goal of removing barriers in the purchasing flow. We hope you find this mechanism just as exciting and useful as we do and we’d love to hear from you – email us, or join the conversation on telegram.


Introducing Optimistic Unlocking, which overcomes the slow confirmation times and provides a better user experience for blockchain transactions.

Creating a smoother, faster and a more secure online purchase experience

Hello Optimistic Unlocking

<img src="/images/blog/hellooptimisticunlocking/hero.jpg" alt="Optimistic Unlocking in action.">
At Unlock we’re all about making transactions on the web seamless and effortless. Blockchain transactions have lots of incredible features, from low cost to permissionless, but the strong suit of blockchain technology – its safety features around immutable data also means every transaction needs to be confirmed by miners. This can take time. Generally Ethereum transactions are considered final after they’ve been confirmed by 12 miners, which can take a few minutes and longer depending on how busy the network is. This presents 2 challenges: not only is this slow, but it is very hard to predict accurately.
The reason we do this is to ensure that funds aren’t double spent (accidentally or purposefully). Theoretically users could spend their Ether in one place and while that transaction is still being confirmed spend it in another place. In this instance the transaction that’s confirmed first would go through and the other would fail.
<img src="/images/blog/hellooptimisticunlocking/locked.jpg" alt="Optimistic Unlocking in action.">
One of our core beliefs is that the challenge most creators are facing is not so much fraud than it is friction. Increasing conversion rates will have a much larger impact on their revenue than fighting the rare cases of fraud. So instead of adding friction or delays to all of the benevolent users in order to stop a few fraudsters, we believe it’s much more beneficial to make it easier to unlock content, even if that means that a small number of people will find ways to “cheat” creators by a few dollars.
We want to trust people! And we’re optimistic that they actually want the content and are willing to pay for it fair and square. Meet Optimistic Unlocking!
We’re working on an algorithm that will determine if a transaction is likely to go through or not, based on the user's balance, their previous transactions, and a few other factors. If it’s likely to go through, the content immediately unlocks while it’s still being mined and confirmed in the background. We display a status bar and notifications, and a confirmation once the transaction went through.
<img src="/images/blog/hellooptimisticunlocking/confirming.jpg" alt="Optimistic Unlocking in action.">
A confirmed purchase will soon show a new flag with the duration of your subscription and let you click through to your keychain where you can review your purchases.
<img src="/images/blog/hellooptimisticunlocking/subscribed.jpg" alt="Optimistic Unlocking in action.">
Should something unexpected happen – like the transaction is taking longer than usual to be confirmed, as would happen if funds were accidentally double spent, the content gets automatically locked again. The user is informed that there was an issue with the transaction and is led through the default purchase flow.
We could also detect new transactions sent by users with a pending transaction, and immediately re-lock the content because we then know that their key purchase is likely to not go through!
If the algorithm determined this is a transaction that is unlikely to be confirmed (hopefully a rare case), the user is presented with the default purchase flow where they have to wait for the transaction to be confirmed by 12 miners. Not the worst of scenarios - it just requires a bit of patience.
<img src="/images/blog/hellooptimisticunlocking/stages.jpg" alt="Optimistic Unlocking in action.">
In a nutshell, Optimistic Unlocking makes the entire purchasing experience better by allowing instant unlocking while still maintaining a high degree of security. A much nicer user experience gives users more freedom and creators more conversion, all with minimal risk.
That’s Optimistic Unlocking – and one step towards our bigger goal of removing barriers in the purchasing flow. We hope you find this mechanism just as exciting and useful as we do and we’d love to hear from you – email us, or join the conversation on telegram.


![ocean scene](/images/blog/waystounlocktheweb/hero.jpg)

Imagine if paying for content had been built into the web from day one.

A few days ago, Julien Genestoux wrote [an introduction to Unlock](/blog/what-is-unlock): a decentralized, permission-less protocol that allows anyone to sell access to their work. It’s a great high-level introduction to our philosophy and approach. Hopefully, it also explains why Unlock is such a radical idea; something that has never been built on the web before. If you haven’t read it, [it’s a great place to start](/blog/what-is-unlock).

In this post, we’ll bring it down to earth. Now that we’ve explored the implications of an open protocol for payments — what can you do with Unlock?

Here are just a few examples.

## An open paywall

As publishers move away from advertising-based business models, they’re increasingly looking to replace ads with direct revenue. Paywalls are the most common way to do this.

![paywall screenshot](/images/blog/waystounlocktheweb/paywalldesktop.png)

Let’s say you’re a writer who publishes on your own site, independently. Most of your content is free, but some of your content is so valuable to a particular group of people — maybe you analyze the tech industry, or you’ve got a unique insight into the future of journalism — that you know some people will pay for it. By adding a hard paywall, you give your readers a small preview of that content, but require them to pay to access the whole thing.

Or, you’re the largest newspapers in the world. Newsrooms across the world, from the [New York Times](https://www.nytimes.com/) to [Die Zeit](https://www.zeit.de/index), use paywalls to meter access to their content and drive membership revenue. You could set up a hard paywall and require payment for all content — or you could require payment after a user has read four or five articles.

As a publisher, you could negotiate with a paywall solutions provider, or work with a payments processor. The process could take months and cost you tens of thousands of dollars. In contrast, Unlock doesn’t require you to ask anyone for permission, and you can start taking payments on your content in just a handful of minutes.

This is the first application we’ve built using Unlock. It’s live right now. In fact, if you have [Metamask](https://metamask.io/) installed, you can try it yourself on [Julien’s site](https://www.ouvre-boite.com/members/), and [on my own](https://werd.io/2019/testing-the-unlock-paywall--protocolcom). In both cases, we’ll double any money spent and donate it to [she256](https://www.she256.io/).

## Recognizing your community

Let’s say you’re running a local newsroom. You produce journalism in the public interest, so you don’t want to lock your content away with a paywall — but you want to give your readers who can afford it the opportunity to support you. To be clear, you _need_ that support.

Instead of a paywall, you place a patronage ribbon on your site. Visitors with the means can support you — and you can display their names (if they want). With this kind of patronage, you get revenue, and your supporters are publicly recognized in their community for having supported an important resource. It’s win-win.

Just as with the paywall, there’s no need to sign up for an account somewhere, or wait to be approved for a patronage service that will take a hefty cut. You can build this level of community reward right into your website, either by embedding a patronage widget from us or another host, or by integrating directly with the protocol using your own code.

This model [has worked well for the Guardian](https://www.theguardian.com/membership/2018/nov/12/katharine-viner-guardian-million-reader-funding) and Wikipedia, among others, and Unlock makes it available to everyone. We’ll be releasing our patronage widget soon, but anyone can build one on top of the Unlock protocol today.

## Licensing software

Unlock isn’t just for content. The same principle that makes a paywall work can be used for software licensing. As an independent developer, I can allow you to unlock a license for my application in just one click, without having to depend on a centralized provider — or giving them a giant 30% cut. Because Unlock is a permission-less, decentralized protocol, developers get to keep 100% of the price of a license, and there’s no approval or banning process.

Unlock allows you to experiment with revenue models. Maybe licenses or subscriptions aren’t right for you —every business is different. You could use patronage to allow your community to support development. Developers could choose to automatically embed the names of supporters on their websites or GitHub pages.

Most importantly, you don’t need to fit someone else’s service into your software user experience. You can use the Unlock protocol to built a licensing or support system that fits right into what you’ve already built.

## Selling tickets to your hot event

Imagine you’re running an arts event in your town. You want to take home 100% of the ticket price, but you also want to customize the ticket buying process: the standard form just isn’t going to cut it. It’s got to be unique to you — and it’s got to capture exactly the information you need to give the attendee a personalized experience.

You’re in luck. Just as Unlock isn’t just for content, it’s not just for access to the digital world, either.

Unlock can be used to sell tickets to real-world events. Attendees purchase “keys” to attend, from the event’s own website — and then show up with a QR code representing the key at the event itself. (Who knew QR codes would come in handy after all?) Event hosts can check people in using a very similar mechanism to other event services.

Most importantly, because Unlock is an open protocol, you don’t need to use our event app. Anyone can write an event service or app on top of the protocol. That means each kind of event, or each event owner, can run their own code (and capture attendee data) that best suits their context.

## Reaching a premium newsletter audience

Finally, Unlock can be used to create premium newsletters. Email is a decentralized open standard, so paid newsletters should be too. Best of all, mailing list owners can continue to use the email service of their choice.

Here, readers buy a “key” to the mailing list, leaving their email address as part of the process. All it takes is one click. At any time, the mailing list owner can export the complete list of email addresses, and import it into Mailchimp, HubSpot, or whatever they use for mailing lists (including their own software).

The result is that paid newsletters can use an ecosystem of different apps and services, rather than squeeze themselves into a one-size-fits-all model.

## And more

The beauty of Unlock is that you can think of our initial apps as proofs of concept. The only limit is what you can build: the open protocol will be there for you. And if you just want a friction-less service that works really well, with the bare minimum of setup and technical integration, we’ll provide a great suite of apps which meets that need.

We’re always interested in hearing from you. If you have questions or comments, reach out to us at [hello@unlock-protocol.com](mailto:hello@unlock-protocol.com).


We’re building an open protocol to allow anyone on the web to earn money from their work. The possibilities are endless. Here are some of them.

Ways to Unlock the Web

<img src="/images/blog/waystounlocktheweb/hero.jpg" alt="ocean scene">
Imagine if paying for content had been built into the web from day one.
A few days ago, Julien Genestoux wrote <a href="/blog/what-is-unlock">an introduction to Unlock</a>: a decentralized, permission-less protocol that allows anyone to sell access to their work. It’s a great high-level introduction to our philosophy and approach. Hopefully, it also explains why Unlock is such a radical idea; something that has never been built on the web before. If you haven’t read it, <a href="/blog/what-is-unlock">it’s a great place to start</a>.
In this post, we’ll bring it down to earth. Now that we’ve explored the implications of an open protocol for payments — what can you do with Unlock?
Here are just a few examples.
<h2>An open paywall</h2>
As publishers move away from advertising-based business models, they’re increasingly looking to replace ads with direct revenue. Paywalls are the most common way to do this.
<img src="/images/blog/waystounlocktheweb/paywalldesktop.png" alt="paywall screenshot">
Let’s say you’re a writer who publishes on your own site, independently. Most of your content is free, but some of your content is so valuable to a particular group of people — maybe you analyze the tech industry, or you’ve got a unique insight into the future of journalism — that you know some people will pay for it. By adding a hard paywall, you give your readers a small preview of that content, but require them to pay to access the whole thing.
Or, you’re the largest newspapers in the world. Newsrooms across the world, from the <a href="https://www.nytimes.com/">New York Times</a> to <a href="https://www.zeit.de/index">Die Zeit</a>, use paywalls to meter access to their content and drive membership revenue. You could set up a hard paywall and require payment for all content — or you could require payment after a user has read four or five articles.
As a publisher, you could negotiate with a paywall solutions provider, or work with a payments processor. The process could take months and cost you tens of thousands of dollars. In contrast, Unlock doesn’t require you to ask anyone for permission, and you can start taking payments on your content in just a handful of minutes.
This is the first application we’ve built using Unlock. It’s live right now. In fact, if you have <a href="https://metamask.io/">Metamask</a> installed, you can try it yourself on <a href="https://www.ouvre-boite.com/members/">Julien’s site</a>, and <a href="https://werd.io/2019/testing-the-unlock-paywall--protocolcom">on my own</a>. In both cases, we’ll double any money spent and donate it to <a href="https://www.she256.io/">she256</a>.
<h2>Recognizing your community</h2>
Let’s say you’re running a local newsroom. You produce journalism in the public interest, so you don’t want to lock your content away with a paywall — but you want to give your readers who can afford it the opportunity to support you. To be clear, you need that support.
Instead of a paywall, you place a patronage ribbon on your site. Visitors with the means can support you — and you can display their names (if they want). With this kind of patronage, you get revenue, and your supporters are publicly recognized in their community for having supported an important resource. It’s win-win.
Just as with the paywall, there’s no need to sign up for an account somewhere, or wait to be approved for a patronage service that will take a hefty cut. You can build this level of community reward right into your website, either by embedding a patronage widget from us or another host, or by integrating directly with the protocol using your own code.
This model <a href="https://www.theguardian.com/membership/2018/nov/12/katharine-viner-guardian-million-reader-funding">has worked well for the Guardian</a> and Wikipedia, among others, and Unlock makes it available to everyone. We’ll be releasing our patronage widget soon, but anyone can build one on top of the Unlock protocol today.
<h2>Licensing software</h2>
Unlock isn’t just for content. The same principle that makes a paywall work can be used for software licensing. As an independent developer, I can allow you to unlock a license for my application in just one click, without having to depend on a centralized provider — or giving them a giant 30% cut. Because Unlock is a permission-less, decentralized protocol, developers get to keep 100% of the price of a license, and there’s no approval or banning process.
Unlock allows you to experiment with revenue models. Maybe licenses or subscriptions aren’t right for you —every business is different. You could use patronage to allow your community to support development. Developers could choose to automatically embed the names of supporters on their websites or GitHub pages.
Most importantly, you don’t need to fit someone else’s service into your software user experience. You can use the Unlock protocol to built a licensing or support system that fits right into what you’ve already built.
<h2>Selling tickets to your hot event</h2>
Imagine you’re running an arts event in your town. You want to take home 100% of the ticket price, but you also want to customize the ticket buying process: the standard form just isn’t going to cut it. It’s got to be unique to you — and it’s got to capture exactly the information you need to give the attendee a personalized experience.
You’re in luck. Just as Unlock isn’t just for content, it’s not just for access to the digital world, either.
Unlock can be used to sell tickets to real-world events. Attendees purchase “keys” to attend, from the event’s own website — and then show up with a QR code representing the key at the event itself. (Who knew QR codes would come in handy after all?) Event hosts can check people in using a very similar mechanism to other event services.
Most importantly, because Unlock is an open protocol, you don’t need to use our event app. Anyone can write an event service or app on top of the protocol. That means each kind of event, or each event owner, can run their own code (and capture attendee data) that best suits their context.
<h2>Reaching a premium newsletter audience</h2>
Finally, Unlock can be used to create premium newsletters. Email is a decentralized open standard, so paid newsletters should be too. Best of all, mailing list owners can continue to use the email service of their choice.
Here, readers buy a “key” to the mailing list, leaving their email address as part of the process. All it takes is one click. At any time, the mailing list owner can export the complete list of email addresses, and import it into Mailchimp, HubSpot, or whatever they use for mailing lists (including their own software).
The result is that paid newsletters can use an ecosystem of different apps and services, rather than squeeze themselves into a one-size-fits-all model.
<h2>And more</h2>
The beauty of Unlock is that you can think of our initial apps as proofs of concept. The only limit is what you can build: the open protocol will be there for you. And if you just want a friction-less service that works really well, with the bare minimum of setup and technical integration, we’ll provide a great suite of apps which meets that need.
We’re always interested in hearing from you. If you have questions or comments, reach out to us at <a href="mailto:hello@unlock-protocol.com">hello@unlock-protocol.com</a>.