◱ ◱hazu (@hazuflorin) • Hey

just a regular guy

Stats

Publications

Looking for some great web3 podcasts? Look no further than Lens 🌿 Here are *some* of our favorites: @rehash.lens @watase.lens @thefutureofmusic.lens @ethdaily.lens @marcus.lens @violetverse.lens @bankless.lens @web3academy.lens @thesymmetrical.lens @thisisvoya.lens Tag your favorite podcasters below 💚
Very excited to share that I've partnered with KarmaVioletta for my frist pay-to-collect podcast! All collectors of this podcast will receive private access to an exclusive DJ mix recorded during Art Basel '22, the week that I met them! I'll also send the transcript of the podcast and the AI-generated summary and notes to any collectors who want it. All proceeds will be split evenly between the the podcast and KarmaVioletta. Karma and Violetta are artists, partners, world builders, and more. They are both independent musicians who make music together and individually. And they’ve been a core part of the broader web3 music scene for a while. Together, they started the Wave World community, a music community focused on creating intimate experiences for artists to connect with the most engaged fans. I met Karma and Violetta at Art Basel in Miami last year and they have since become good friends. This podcast was recorded in person at ETH Denver in March, my first podcast recorded in person and it was incredibly fun. We talked about their backgrounds in music and web three, their experiences with song camp and with music collaboration in general, what wave world is all about, their thoughts on how AI and other emerging technologies will affect music in the future, and so much more. I hope you learn something new from today’s episode. Find KarmaVioletta here: All socials and links- https://linktr.ee/KarmaVioletta Find the podcast here: Twitter- https://twitter.com/futuremusicpod Instagram- https://www.instagram.com/thefutureofmusicpod/?hl=en Lens- https://lenster.xyz/u/web3musicpod Jake- https://twitter.com/cryptabel Find Phlote here: Website: https://www.phlote.co/ Phlote TV Youtube- https://www.youtube.com/@phlotetv Twitter: https://twitter.com/teamphlote Instagram: https://www.instagram.com/teamphlote/ Lens: https://lenster.xyz/u/phlote
Help me to be part of **Yasai Lens Festival** collecting this post and you have as a reward this flower. (🌸) #Yasai
#GIVEAWAY 🚨💚💜💚💜🚨 #FOLLOW Do YOU want to get your HANDS on a HOODIE similar to this? FOLLOW @gotenks ✅ COLLECT this POST ✅ MIRROR this POST ✅ *Just testing the waters to see the traction is gets
🔥🔥
First time uploading audio to Lens! New Track - LensFrens Free to collect! Please #LMCC (like mirror collect comment) Must be following to collect #lensfrens
Folks don't follow or collect paid follows that you don't know what the project is. Lensbeat is a good example that simply didn't tell anything what they were up to (they weren't associated with anyone) and disappeared. Simply promising random airdrop. IMO everyone who is promising an airdrop should be approached with caution.
Today we conquered the Castel, Red bull Castle
Yesterday Lens Protocol announced the CultivatorDAO (👩‍🌾,👨‍🌾) to establish community driven content curation for Trust & Safety. Going to share our vision below on how we see the web3 social stack evolve 🧵 First, Lens Protocol is a decentralized social media protocol that acts as a registry to point content and followers. Users can link to any content which can be stored on-chain & off-chain. Most of the content is off-chain (stored in IPFS or Arweave etc). The Protocol is flexible enough to link the content even to a private cloud or to a self-hosted environment. This is an interesting use case for follower and token gated content. It's up to the applications and users to choose how they use Lens Protocol. Lens Protocol design guarantees users the access to their own social network. You don't need to trust centralized or off-chain platforms with your followers. Meaning every user has their own social network. Not only you own your own network, but you also have the ability to broadcast content in a permissionless and censorship resistant way. Anyone you grant the access to your content has the ability to explore your creativity and self expression. This is decentralization by design. While decentralization is groundbreaking for web3 social, the amount of information and finding relevant peers and content for you to discover would be a time consuming mission. This reason is why we would see another stack evolve - the middleware - where curation lives. The middleware layer already exists on Lens Protocol, there are tools such as Graph Protocol, RSS3, Sepana and the Lens API. The middleware layer consists from widely decentralized appoaches to being progressively decentralized depending on the use cases they serve. The latest addition to the middleware are communities such as the CultivatorDAO, focusing on curation with Trust & Safety in mind. Where code cannot solve everything, we need communities to reflect their values and govern. The DAOs of the Lensverse will serve the application layer for various tasks ranging from building discovery algorithms, content moderation and solving various challenges that social media faces today. The key difference between the web2 and web3 social stack is that in web3, the stack is completely open. When you don't like a policy or an experience, as a user you should be able to find a new experience without leaving behind your accumulated social capital. Hopefully we will see small communities evolve across the web3 social ecosystem, being utilized for tasks that would benefit from community governance. I would even imagine that every social media application built on top of Lens Protocol would have its own DAO consisting of its community members voted by the community that reflects the their own values. Most importantly, these DAOs can operate transparently and since the measures taken by these DAOs are public, there should not be any shadow banning (see here: https://lenster.xyz/posts/0x05-0x0417). By ensuring human assessment and the design that leads to decentralization, we are able to ensure that web3 social doesn't become a closed platform and users are able to access to open social networks that are driven by community engagement & stewardship. Building a decentralized stack is a harder exercise than starting from a centralized approach, but brings the benefit of fully verified content linking on-chain wherever you store your content, ownership to your social graph, ability to use timestamps and create programmability. And most importantly: decentralized and on-chain content and follower registries opens up the programmability and composability to another level. Imagine pairing Lens with tools like Simo, Lit Protocol, DeFi, NFTs, ReFi and DAO governance. Besides reachitecturing the social stack, part of the mission for the Lens team is to make the social stack more accessible. Now with all interactions across the Lens Protocol, users do not need to sign or pay any gas. Blockchain on the backend, party on the frontend 🥳 Next Monday, you will be able to vote for CultivatorDAO with your Lens Profile to signal your support for community driven stewardship https://snapshot.org/#/cultivatordao.eth/proposal/0xd512345eb6c9b7bbf57b28a8b4f7dc46d31ab6c19ac8ad5de4605fa52fcb9e98 If you love our vision and what we are building, collect and mirror this post to retain your early user flexing rights 🌿
gm all! 👋 Today I wanted to introduce you to Sismo and explain you what ZK Badges are 🧵⬇️ (stay until the end, there might be a badge to mint 👀🎁) What is Sismo? Sismo is « a modular Attestations Protocol focused on decentralization, privacy and usability. » But what concretely does it mean? Sismo enable you to prove on Ethereum to anyone, thanks to one of your addresses, that you are, have or did something. Theses proofs are represented by badges, which are non-transferable NFTs (ERC-1155 tokens). To be allowed to mint a badge, your address must be in the group of eligible addresses associated to it. But now what if you could prove something with an address but receive the badge on another without any link between these two 👀 So proving something without doxing the address you used to prove it. That’s what ZK Badges allow us to do! With Sismo you prove directly in your browser that your address is part of a group of eligible addresses. It uses zk-SNARK technology. Let’s take a simple example: you can prove, on an anon address (destination address), that you own a conference POAP, by using your ENS address (source address) which contain that POAP. And vice versa. But of course your source address allow you to only mint one badge on the destination address of your choice, no more. This is a simple example but you can imagine much more useful ones! There are obvious uses cases for Sismo and ZK Badges such as Sybil resistance. By the way Sismo has already shipped a “Sybil resistance” ZK Badge using Proof Of Humanity, go check this out: https://twitter.com/Sismo_eth/status/1569668644497510402?s=20&t=texAnda3oLd9C1iRjfFCdQ So this allow you to prove that you are a human on an anon address using your POH registration (doxed) address. It’s not perfect yet but it’s a start and it shows how ZK Badges can be powerfull! 🔥 Privacy is necessary in the IT world and even more in an ecosystem like Ethereum where all our interaction are public. That’s why Sismo will help us to create anonymity on top of these concepts and more… Now lt’s time for the little gift! 🎁 If you want to try out Sismo and get your very first ZK Badge ➡️ **Mirror** this post Then, from 02/10/2022 you will be able to mint the badge associated to the proof that you Mirrored this post. I will let you now when it’s available and the steps to follow to mint it :)) Thanks for reading this thread and welcome to Sismo anon! :))
Learned about basic fundamentals and mission of @orbapp.lens project, and got a sick NFT 🔥 #orb #orbapp #orbsbt
Learned about basic fundamentals of Non-Fungible Token (NFT) on @orbapp.lens app, and also got a sick NFT 🤩 #orb #orbapp #orbsbt
Just getting started in web3 vs. when it all clicks. The deeper you go, the brighter it gets. @rabbithole.lens”