The first question people usually ask about Web3 is what it is/ stands for. The short answer I commonly provide is that it is a new form of the internet that is decentralized, accessible, and governed by the many (to keep it easy).
Unlock Protocol represents those values (and more) in its ultimate form. The protocol was built to empower creators, developers, and community organizers to seamlessly bring their projects onchain in the form of event ticketing, memberships, certifications, and recurring subscriptions.
Unlock Protocol is easy to use, even for beginners/ attendees who don’t have a wallet yet. We support multiple L2s on Ethereum as well as Mainnet and even have a Stripe integration that allows for fiat payments (if necessary). The ticket is an NFT issued through an ERC-721 smart contract, allowing for onchain proof of attendance. Every ticket comes with a generated QR code that can be scanned for attendance to check the ticket’s validity (regular phones can scan those). The protocol itself is open-source and can be forked and embedded seamlessly. There is more to tell, but the important message is:
I am currently the Lead Steward at Unlock Protocol DAO, and I know for a fact that our community would love to support Devconnect this year for ticketing by using a peer-governed protocol over a platform that showcases true empowerment through Web3 tooling!
Does unlock have a compatibility with zuPass right now? We have use-cases like Meerkat that depend on zuPass - and we really want that privacy preserving way of proving you have a certain ticket.
I have used Unlock Protocol many times to create immutable ticketing. In June 2024, we used it in Colombia to create the first NFT-based ticketing system for an international electronic music event: Drumcode by Adam Beyer.
Additionally, I had a great experience with Zupass in Bangkok, primarily using my email and wallet. I strongly support protecting information about event attendance—sometimes, simply being at a certain place can create differences, just like voting decisions.
In my opinion, Unlock Protocol offers an excellent UX/UI for managing events that contribute to public social reputation, while Zupass ensures privacy and security regarding my interests and attendance at certain events.
Hey Ligi. I would need to understand better what you call “compatibility” with ZuPass. Can you elaborate please?
I guess it should be possible to create a ZuPass easily for anyone who owns a spcific NFT, knowing that the ZuPass itself would not be “pointing” to the specific NFT/Ticket. Is that what you are referring to?
yes - for me “compatibility” with ZuPass means that you get a ZuPass with your ticket. Currently this is heavily relying on an e-mail connection - so wondering how this would work together with unlock.
I think anyway for DEVConnect it is a bit late now - we are quite far with the Daimo collaboration so you can pay with a huge set of (chain-token) combinations but receive the tokens on one token@one chain with good UX - also a thing that AFAIK is currently not the case with unlock?
I believe ZuPass could be linked since Unlock is entirely open-source. With Unlock you can demand email collection (actually the standard setup does that).
Unlock allows you to pay with various tokens and across multiple chains btw. and as mentioned above has one of the most straightforward UIs possible. Maybe a demo would help as I don’t think it is very late @ligi.
I have used infinite times Unlock for Ethereum Bolivia’s events: meetups, workshops, Buildathons; and we have also issued certifications for our Solidity Workshops, Conversatory and Conferences at ETH Bolivia 2024 Buildathon as well as active hackers at our last Buildathon.
Many of the participants were new commers into Web3 and they easily minted their ticket with just an email (wallet address field is optional), this has given us a great onboarding experience, and once people are confortable using a wallet address they can access those NFTs and transfer them to their wallet at any time
Set a price for your ticket with a huge set of chains, even enable to pay with credit card,
Users can mint the ticket just with an email,
At the venue you will be able to set as many lock managers to scan ticket QR codes,
AND if that wouldn’t be all, you can create a certification as NFT soulbound token for a certain event during Devconnect, let’s say Devconnet Ethereum World’s Fair and airdrop the certification only to the people who attended the Fair, so you can do it just by downloading the csv file of your event ticket and airdrop it right away.
This can set a real difference from any other ecosystem event and set a standard to completely be a Web3 event using a permissionless, transparent and open source protocol.
I prefer Unlock for ticketing and events. The open source protocol and onchain data supports composability, which gives event sponsors, partners and participants opportunities that aren’t available in closed source apps with data stored on private clouds.
The biggest win for my events is the Icebreaker networking integration. Privacy conscious and opt in, this integration provides event partners and participants an easy way to network even after the event is over.Here is a blog about how it works.
Unlock also supports tiered ticketing, which individual events from the community could take advantage of. Here is an example.. And Unlock Collections feature would provide Devconnect an onchain and open source way to bring all the Devconnect events into one page, for easy discoverability. Here is an example.
Exactly! @ligi check out these examples on how Unlock Protocol could be the best tool as ticketing and certificactions for attendees at Devconnect.
And regarding privacy, I would say Unlock has a better privacy feature as attendees can choose to mint their ticket with only a wallet, stay completely anonymous and safeguard their personal data.
@ligi@BorrowLucid is describing it very well in her blog entries and is a long term user of the protocol for her different online and offline events. It would be great to get a better review on what else we can do to be present at Devconnect this year <3
Would any of you be open to join the DEVCon(nect) team for our web3office hours?
The next free one would be Monday 28.4. 17:00 CET
And regarding privacy, I would say Unlock has a better privacy feature as attendees can choose to mint their ticket with only a wallet, stay completely anonymous and safeguard their personal data.
can you elaborate how this would provide better privacy than zuPass? FYI: We need to be able to contact people via email as you cannot reliably contact people via a wallet address currently. Under this constraint as far as I see the combination pretix (self hosted) + zuPass is more privacy friendly than unlock.
But we can discuss details in the W3OH.
Hey there @ligi yes that sounds great. Let me wheel in @Julien_Genestoux so we can both be present.
As for email collection, this can be activated as a feature within Unlock and you can ask people to use their wallet and email. But when it comes to privacy details I will also have to hand it over to Julien.
Where are the office hours being held so we can join on time in the right channel?
