With Unlock, users and publishers don't go through a middleman. This means lower friction for the user, and both better conversions and prices for the publisher. It also means that anyone can run Unlock's code - you don't have to use our services.
Our first version of Unlock is for technical publishers who also control their technology platform, and whose audience is technical early adopters who use a cryptocurrency wallet.
As part of our roadmap, we plan on allowing users who do not know of cryptocurrencies or have a crypto wallet to pay us (Unlock Inc) with their credit card in order to perform the transaction on chain for them. In that context we will charge a convenience fee on top of the (crypto) price of the keys. This convenience fee will cover the gas price, the credit card transaction and a small margin for us.
Unlock is powered by Ethereum, which means that you can use your own wallet to purchase memberships (we call them keys).
February 2020: We are working on adding support for WalletConnect. Please reach out if you can help!
If you do not have your own cryptocurrency wallet, you can create an account with Unlock and purchase memberships with your traditional payment (credit or debit) cards on selected locks.
We are working to provide lower level integrations which will make it harder to bypass limitations set by creators, but as always these will come at the expense of some usability for creators and consumers.
We strongly believe that, at this point, the biggest revenue loss for creators online is not because of fraud, but because of inconvenience.
When you purchase a lock and you see a Confirming Purchase notification we're using Optimistic Unlocking to confirm your purchase.
Usually a transaction needs to be confirmed on the Ethereum Blockchain before it is validated – this can take a few minutes, depending on how busy the network is. Optimistic Unlocking provides you access while the transactions is confirming rather than after. We do this to create a faster purchase and more seamless user experience. Read more about it in our release blog post.
No. We will hire an independent team to perform an audit of our smart contracts, but we have decided that it is too early for this. We decided to take a very incremental approach to implementing the full protocol and we believe that there will be a lot of changes which would make an audit irrelevant at this point.
We strongly advise lock owners to frequently withdraw funds on their locks. Funds are safer when "owned" by an address than by a contract, even if audited. We will also make what it takes in case of fraud to help recover lost revenue until the contracts have been under audit.
Yes! Even though our earliest iterations are around paywalls for text, we are designing and building the protocol so that it can be applied to any kind of media (audio, video) or even software. This will require more integration points (not all content is just HTML in a web page), and we're happy to take suggestions and contributions!
Right now: yes.
Eventually: no. Our roadmap is to start with the most "crypto-friendly" crowds because they know and understand some of the constraints that arise from using cryptocurrencies ... but it is our goal to make it trivial for anyone to use Unlock, whether they want, care or even know about cryptocurrencies.
Right now: yes.
Eventually: no. We plan on making it easy for people who do not have a crypto wallet to use an Unlock application which can help them manage their keys.
Yes - if you are using an Ethereum-enabled web browser such as Opera or Coinbase's Wallet.
Our production application available at https://app.unlock-protocol.com/ is connected to our mainnet deployment.
You can interract with our Rinkeby deployment by going to https://staging.unlock-protocol.com/
Yes! The "lock" itself does not include the logic for recurring memberships, but we provide another contract, called the KeyPurchaser, whose logic enables recurring membership. At a high level, this only works for ERC20 locks, and leverages the allowance mechanism of the ERC20 specification. Instead of purchasing a key themselves, members have approve the
keyPurchaser contract to spend some of the ERC20 tokens. They will approve a multiple of the key price, which will let the creator (or a third party, like Unlock Inc) call the
keyPurchaser contract to purchase keys for them. The
keyPurchaser contract guarantees that not all ERC20 tokens are withdrawn at once, by only performing successful key purchases when a an existing key is soon to be expired.
When purchasing a key to a lock, the member has to also pay for gas to the Ethereum network in order to get the transation mined. Here are rough indication of the gas amount to be paid to purchase a key a a lock when the purchases did not have a key previously (this can vary base on some lock specific parameters, such as the lock version):
ETH lock: 160,000 gas,
ERC20 lock: 175,000 gas, to which we should add 45,000 for the ERC20 approval
When performing renewals, the user should expect to spend 70,000 gas.
Note for ERC20 locks, if your application uses the key purchaser pattern, then, the user only has to pay for the ERC20 approval, while the entity sending the transaction has to pay for the key purchase gas.