Web3 Crash Course | Josh Snow | Skillshare

Playback Speed

  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x

Web3 Crash Course

teacher avatar Josh Snow, Web3 x no-code

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

11 Lessons (2h 14m)
    • 1. Course Introduction

    • 2. What's Web1?

    • 3. What's Web2?

    • 4. Web3's Promises

    • 5. Social Tokens, NFTs, DAOs and more!

    • 6. Projects that make sense with Web3

    • 7. Projects that DON'T make sense with Web3

    • 8. Web3 projects we ❤️

    • 9. How to build web3 apps with no-code

    • 10. Building Web3 apps with no-code using Bubble

    • 11. Bonus Content: Bubble x Pinata Integration Walkthrough

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

There’s a lot of buzz words flying around at the moment, but what does it all mean?

  • Blockchain
  • Bitcoin
  • Web 3.0
  • NFTs
  • DAOs

It takes time to break these down and understand how they work.

In this course we’ll talk in detail about these topics and how they can be applied to real life scenarios, and how we expect they’ll impact our lives.

By the end of this course you will be able to:

✅Understand the key web3 lingo and how you can apply it to a new/existing business
✅ Know where to find help for anything you don’t know. You’ll have access to a great and supportive community
✅ Command envious glances as you walk down the street (in the metaverse)

You'll benefit from this if...

✅ You're just looking for a quick crash course in web3 and how it can apply to real businesses
✅ You have an idea for a web3 app but don't know how to make it yourself
✅ You’ve got an existing web2 app and you’re wondering how you can inject some web3
✅ You want to solidify your web3 knowledge, learn some awesome tips and tricks, and see how you could use no-code tools available today to build your app in days.

Course overview

✅ Hours of video tutorials covering the key foundations of web3 you need to understand before you start building.
✅ Tips and tricks, recommendations of how to get started with no-code.
✅ Where it does and doesn’t make sense to use web3 technologies in your app
✅ Introduction to some web3 projects we absolutely love
✅ Guides and resources for continuing your learning journey and trouble shooting.

This course has been created in collaboration with Matteo Mosca, of Superbuild.io

Meet Your Teacher

Teacher Profile Image

Josh Snow

Web3 x no-code


I've been bubbling (building no-code apps with Bubble.io) for the past 12 months, after rolling off building my own startup for the two years prior with code. Naturally, I'm obsessed with Bubble and want to help other makers learn what’s possible with it. I've also been bitten by the web3 bug and in addition to learning all there is to learn, I've worked on a successful NFT collection drop for a client.

See full profile

Class Ratings

Expectations Met?
  • 0%
  • Yes
  • 0%
  • Somewhat
  • 0%
  • Not really
  • 0%
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.


1. Course Introduction: Hey everyone, my name is Matteo. I'm the founder of super bills and I'm so excited for this course and even more for the Web three industry food of controversies, but also big opportunities. In this course, we're going to talk about Web three, its impact on the creative economy, pros, cons, controversial topics and great products being built by exception on makers. And of course, how to make them with no code. I mean, I'm excited. You can tell it. And with me talking about Web three, Mr. Josh from Australia, we'll provide some links at the end so you can learn a little bit more about our caries if that interests you. But to give you a high-level intro into my experience though, because I'm sure a lot of you are not familiar with me. I've worked at in various corporate strategy and finance roles in the corporate space for about 15 years before throwing in the towel a few years ago now. And that was to focus on doing things that really interests me. Over the last few years, I've been consulting on projects related to my past life a little bit because I've got to pay the bills somehow, but also getting heavily involved with product strategy and development and spending a lot of time in the setup space. I'd say I've been a hobby coder for many years. I know a little about a lot, but with no code tools like bubble, I've been able to not only develop the strategy, I've also been able to go and build it too. And it's just been an amazing journey over the last 12 months or so, playing around with bubble last year, a client, I reached out and wanted some help with a new project that we're working on and that was specifically working with LFTs. Now I hadn't had much exposure to the Web three space before then. So I spent a lot of time brushing up and understanding how it all worked and that sparked my interest in the Web three space ever since then, I've invested a lot of time on understanding it, as well as working on a few projects in that space. Since as well, I really believe that there are some cool things happening in the space, but I do also believe that there is so much hot air and hype as well. I think it's pretty difficult to understand a lot of what's going on most of the time because a lot of people in the space at the moment, our developers. And there's nothing wrong with that. But I think it means that there is unnecessarily complex and discussions and there's a lot of buzzwords that are used and it's just really hard to get up to speed. Mateo, and I wanted to bring you this very balanced view of the Web three landscape. Yeah, Look, there's some hype that's worth getting excited about, but we also want to help you understand the current limitations as well because that's really important. First off, we'll start by going through the fundamentals in plain English and with as many examples as we can before looking at the product lens and what works and what doesn't work, at least with the technologies today. Then we'll move into a little bit more detail about how you can get started with Web three using no code tools like bubble. And we'll also go through a couple of examples as well. Finally, we've put together some really great resources for you to leverage after the course, and that'll help you continue your learning as well. Okay, so let's get into it over to you, Mateo. 2. What's Web1?: The best way to explain what three is two staff at the beginning of the World Wide Web, full deep diving into web three features, pros and cons, and even how to build what they apps with no code. We need to talk about when one, web two, and the evolution of the creator economy over the past 30 years. And I'd like to tell you the stories of three content creators. These people here in the pictures from left to the right. Lena's Stovall, Middle Ariana Grande there, and rock on the right. Don't worry if you don't know anything about them, I will tell you who they are and why we need them to explain. Went three. In the nineties, the Internet was a pretty small, decentralized network of computers. 1 million computers connected to the Internet, which is nothing compared to full billion devices connected to the Internet nowadays, including laptops and smartphones, IoT devices. The first version of the World Wide Web was a democratized way of sharing information with people worldwide. If you add the IP address of a specific computer or the URL of a specific website, you could establish a connection and start transferring or receiving information. That was tricky. I will say there was no Google, no Facebook, no social networks at all. So for a web one Creator, the overarching goal and the challenge at the same time was to get views for the content. I mean, actually finding people interested in what they were created. They internet wasn't just a bunch of studying websites with read-only information reachable if you knew the exact addresses. Again, no aggregators, no social networks. This is why people refer to web one as read. Only. Creating content was extremely hard and doable only for an elite group of developers who could deal with complex protocols. To explain this, let's talk about our first creator. For those unfamiliar with them, Linneaus tall vaults is a Finnish Americans software engineer who is the domain developer of the Linux kernel use by Linux and other operating systems like Android. Developer a bill software. And of course, since he is pretty active in the community of developers, it wants to share and talk about the best practices to write code with our engineers back in the nineties. How would you do that? Remember, no Facebook, no Google know WhatsApp. So first thing, it would create a webpage using HTML, which is a markup language to build web pages that we still use today. Second, it would add in the page some static text to explain the cool things it was doing. Would upload the page and his personal server using FTP, which means File Transfer Protocol. Then he'd send the page URL to the people in you and between quotes, followers, because at that time he didn't make sense to call them followers. Actually, to do that, it use emails or live messages with a protocol called IRC. You needed to have all these addresses and contexts saved in a private list. Perhaps a dot TXT file. Pretty tricky. Was not index theat. There was no way to find discounting online. And even worse, there was no way for him to find people interested in the continent was creating, apart from word of mouth and direct in real life, connections, simply put, web one was about the centralized and direct relationships between creators and their followers. And these connections were possible thanks to open source protocols, the acronyms that I mentioned before and that are here in desired as well. That weren't decentralized, built and maintained by university and research centers all for free. 3. What's Web2?: Here he comes web to. Entrepreneurs started noticing web one gaps. The need for users to easily create content and distribute it to the audience. And on the other side, they need to find compelling information and content online. There was no way to do that. What T2 is all about content discovery and social networking that actually solved problems that creates a slightly No Stovall had creating content, sharing the content with the followers, finding people interested in the content. This was made possible thanks to social networks. Today, how easy it is to write an article and share it on LinkedIn or record a video and share it on YouTube. But these solutions come with a compromise. What today we call the Big Tech. And talking about the PUE, centralized companies that run the most popular social networks. Think about Facebook, Twitter, linkedin, Tiktok, Instagram, you name it. These aren't centralized online spaces where you find the counter you're interested in. You socialize with friends and new interesting people. And in this process, the beak tack, search on natural gas companies make millions of dollars leveraging the passion and work of creators that basically feed the platforms with new, fresh content every day in web to create those animals by the ambition of becoming famous and achieving their personal success. But how about money? Same doesn't pay the bills. Well, if they are good enough at creating content itself, some naturals we reward them. But how a lunch. Let's talk about our next creator. Ariana Grande day, extremely popular American singer. Content on Instagram. And her goal, I was, I would generally say the web to creators goal is to get likes, comments, followers, and create such an engagement. We said that web one was read-only because it was extremely hard to create and share content. But how about web two? Wow, Web T2 is read and write. You can easily find content and you can easily create content. This is why we are talking about user-generated content as well. Influencers choose the format, text, picture, video, and social natural they want to use to find the followers and create content. That's the game. Let's get back to oriented. Granted, she knows that ether post got a lot of impressions. Instagram algorithm, we reward her by putting her posts in the front row at the top of the Earth followers feeds. By why do such a message reward users that create engaging content? Because their revenue model is based on selling ads. And when it comes to selling ads, you make more money by showing as many ads as possible. In other words, by keeping the user active on the platform. We'll notice we've paid this price every time we use our February social networks. In this game, social networks are the backbones of the Internet traffic. And the problem is that they capture most of the value that creators generate, leaving them with likes, comments, glory, and the hope of selling something to the audience they developed. It's now possible for them to monetize the social capital and social currency they created in ears. Social networks indeed provide benefits like a custom tailored experience. I click the feed is different from yours. I don't have to remember your IP address to send you a message like it was in Web one. And social networks analyze the website we browse to provide us with day-to-day experiences and more effective ads. But wait a minute, is this a benefit? What about privacy? We're being tried by ad tech algorithms that know everything about us and make models to predict what we're going to buy next. Again, what about creators monetization? They spend hours creating content on it to get likes, comments, followers. And in the process, they don't extract the economic value they deserve. Let's analyze what's going on here. Because these points are crucial to understand the revolution, which web three claims to bring. I just wanted to make a point here. I personally think that Web T2 is fantastic. Don't get me wrong. You are viewing this video because you found me on Twitter or LinkedIn. And the probability of few discovery me on our Web one IRC chat is exactly 0%. But we're here to understand why people think that Web three My be so revolutionary. And I hope to give you a fair representation. State of the art with pros and cons. This, Let's go on. The problem with web to search on networks is that they are designed to reach a certain amount of users that allows the network effect to kick in so that they can switch from attract to extract. Look at this graph, shear. The beginning social networks attract users once they know that users are locked in, one, easily leave and continue to attract more users. They start charging. And they do that because it's the easiest way to grow the revenue. As private companies. Think about Newberg, achieve was at the beginning or Facebook, they started charging businesses and developers to reach customers by selling ads, services. Based on the data we're giving them for free. Plus, since we're talking about private company censorship is also an issue because these companies get to the sidewalk content is displayed or which account needs to be banned or disabled? Yes. I mean, I can leave to return if I feel that I am getting skewed. And indeed, many people deleted Facebook after the Cambridge Analytica scandal. But what I'm referring to saying here is that as a social network user, you need to follow rules that are defined by few private companies that take huge decisions on how privacy, chancellorship, content ownership, and generally speaking, the decide how our online lives should look like. 4. Web3's Promises: This scenario in mind, we can start talking about Web three, that is splitting the web into two sections. Some people think it's a massive Ponzi scheme. Some others think it will be the next big iteration of the World Wide Web. Let's jump in. Web three claims to combine the decentralized ethos of Web one with the advanced modern functionality of web two, it is the internet on by the builders, creators, and users orchestrated with Dawkins. What does that even mean? Finally, we get to talk about Web three and in particular, its promises. Before starting as a small disclaimer here. In my opinion, some of these points are true and revolutionary. Some others are good intentions. That is attracting a lot of people, but that are not under percent sure it's going to happen. With that sad, Let's break the premises down. No chancellorship. It means that no centralized entity will have the power to limit or suppress users voices. Think about Twitter, that Kanban your account, if they think you're doing something wrong. This internalization award Wide Web data and content are registered on blockchains, tokenized, and accessed on Peer-to-Peer distributed networks. Creators monetization. We will talk about LFTs, social tokens, Dow's that can help creators achieves a dream of making a living online, following the passions. Content, ownership in Web three, you are the owner of the content you create online. It's written in a blockchain. Privacy claims to suppress the ad tech truckers that know everything about us. Last but not least, crypto payments that are inherently embedded in the web. We've been talking about crypto wallets, like mathematics, how to make transactions and handle our Web three identities. We all have that feeling of justice when we think about distributing the Internet wealth across multiple individuals rather than being retained by a few tech companies. That's probably the most significant ethos, but it's a tricky and sometimes misleading topic. First of all, the centralization can happen at different levels. You can build a decentralized social network. Data saves posts on decentralized blockchain. But the access point of view and consume that content is a centralized node. In other words, a website with one URL. Someone could argue, yeah, but makers can build other websites and poor from the same public blockchain. The point is that relevant to the attention economy. And people spend most of their time on 235 websites. It's a human limitation we just can't handle to spread our antigen and across a 100 of information, entertainment and socialization sources and platforms when creating and sharing content, creators want to rely and doubled down on a specific structure mantle that works for talent. Actually focused on one platform for building an Odeon is a well-known best-practice. If by decentralization we mean getting rid of centralized social networks or content aggregator as well. I think this is unrealistic. In fact, open see the one NFT marketplace is a centralized aggregator. What artists submit their NFT. The main difference is in that case, is that they own, they aren't with DACA about this in a while. There is no way to remove content from the blockchain. Once a block is created, it will be there forever. If you want to change for hide something, see a post, I use a maid. You'll need to create another block to declare your changes. The front-end app called node, which pulls data from the blockchain, is in charge of displaying the final data or not. Let's make an example here. You run a decentralized social network where every post gets saved on a public blockchain. Makers can create nodes, actually all the websites with different URLs that pulled data from the same blockchain. On the major node. I mean, the one that gets more traffic and has more users. The owner decides to hide a specific post. They say, because it's against some local rules they defined. Remember, they can't delete the post. It's written forever in a blockchain. Nobody, if the blockchain provides the API, they can create a new block that declares that a specific post needs to be hidden. Some nodes can ignore that last block. M showed the past. Anyway, I avoiding any chance or ship, but the owner of the main node, again, the one that gets more traffic, can decide to apply the hiding rule. And nutshell, the past. What I wanted to say here is that Web three doesn't guarantee free speech and no chancellorship. It provides the tools for it better than web to dust. But ultimately it's the owner of the front-end node that decide what content is displayed. It's true that people could find it through with the blockchain. But technically speaking, I'll accessible areas to analyze the role blockchain. How many people know about ether scan.io, a tool that lets you explore block-by-block, the Ethereum blockchain. I went to leave you with even more controversy. And this slide, think about the Twitter man of the President of the United States. Was it correct, wrong? Was it abuse of power by Twitter as a private company? This can quickly turn into a political debate which I'm not starting here. But still while creating this slide, some questions came to mind about censorship. And I couldn't give just one theorem answer. Definitely controversial. Let's talk about creators monetization for the creative economy. In my opinion, this is the major advantage that Web three rings on a table. The overarching goal for our creator in 2022 is to make a living online and it's all of their passions, them in the process. What three can help create the same disregard. Web three. It's not about taking money out of the system. It's about moving the money around to the people who create, consume, and to the people who maintain and improve the network itself. Look at these graphs in his side. It shows how create those connect with consumers, their followers, fence to intermediaries called platforms. These platforms are such networks. I mean Instagram, LinkedIn, Facebook, TikTok, you name it. Think about our integrand that Instagram allows her to find and grow Herodian. But he worked to, as we said before, these middleman capture all the value generated by creators and followers. Remember, creators invest time creating compelling content for the audience. The more great content is created, the more users will spend time on the platform and talk about it with their friends. The more ads are solved by Instagram. Think about what happens when you see a great picture on Instagram. You think that the creator is grades and you might follow him or her. But also that Instagram is the place to find great content. And you talk about that with the friends. You spend more time on Instagram because it's cool. Instagram popularity grows and they make more money selling gods. Who created the value here? Well, they creators. Web three allows two things that can potentially break the rules and bypass these aggregators when transferring value between creators and funds. First, it allows an invites Web three founders to build their nodes pouring from the public blockchain. It's not just a technology feature. The open source and decentralized Ito's belongs to the Web three culture. Vaso is a great example here. It means the centralized social. And we have talked about it soon in the next slides. But he has a vibrant discourse community that works together to build nodes on top of the blockchain. But how does this help creators? Well, the more platforms connect creators to consumers on the same blockchain, the lower the price they can charge. It's a basic market rule. Basically, more competitors lower the price. These of course, is in theory because the prices they can charge depends on the traffic and popularity they gain. But still, the blockchain provides these capabilities. Second, Web three provides a set of tools that help create those monetize their social capital and social currency created already years. In fact, Web three followers are direct stakeholders and investors and establish a direct and financial relationship with a favorite creators. Explain this, let's talk about the third creator, Brock. 5. Social Tokens, NFTs, DAOs and more!: Iraq is a musician. It produces music. Spotify as a Web T2 platform doesn't reward him as he wishes. This is why Iraq created a social token called rock with a dollar sign at the beginning of the word. Social tokens are cryptocurrencies, DAP, brand communities are influencers, can use to monetize themselves. Special cryptocurrency associated with the Creator, something like a stock for accompany the value. This token depends on the Creator. Online performances, like quality of content they share high likes, comments, generally speaking, the engagement and impressions they get. In fact, the more creative is families, the more followers with by actually invest into his token. Social tokens automatically to followers into investors that can buy and sell creators tokens based on their shorts or performance is exactly what stockholders do with companies if you think about it. But how does Rock actually make money? We such as tokens in a person days, every time there is science by is token. It can sell tokens. Ia owns its followers, wanted to spread the word when he released his new hobbles. But why? Because followers are stakeholders of its kind, it's in their interest to spread the word. Basically they want him to succeed so that rock Tolkien's value increases as well. But on the other hand, what are the benefits for the followers? As old as of the Tolkien? Fans can access premium content, such as early access to music, live concerts, or private connection with them. For example, like live calls, private jobs and things like that. Some artists provide regarding dividends depending on the percentage of their tokens, their funds own. As investors, they can trade tokens who believed in rock at the beginning of his career. And push-based is token when the price was low and I'll sell it at a higher price. You can think about this also as a way to back artists and creators with talent, but not famous yet. In this scenario, social tokens help creators make money, not because they have millions of followers, but because they are talented and people believe they are going to do great things. Let's talk about Tao's. A DAU stands for Decentralized Autonomous Organization. Bit of a mouthful. So I'm just going to refer to them here after his doubts. And it's an entity with no central leadership. I know what you're thinking. It's not exactly an online version of the wild west. In fact, it's governed by its members community that's organized around a specific set of rules enforced on the blockchain. So how does it all work? Well, it typically starts with the creation of a smart contract. You can think of this smart contract as a little like a charter. It outlines the purpose of the Tao and the rules by which it operates. We'll talk a little bit more about smart contracts later on because it is an important topic to cover in the Web three space. Being on the blockchain means that the rules are set in stone unless they're amended through the governance system. And he guessed that that's outlined in the smart contract. After the smart contracts have been created, the down needs to determine a way to receive funding. And this usually involves crypto tokens being sold. They raise some funds. And then those people that hold those tokens have then got some voting rights in terms of what actually happens with the down. It's a little bit like owning shares in a company. Once everything is set up and the Dao is deployed on the blockchain. From this point onwards, stakeholders decide on the future of the organization. And this is a very critical point. It's not the organization's creators. Those people who first wrote that smart contract that hold all of the influence and power. They don't have any more influence and power on the project in anymore overlay then the other stakeholders, of course, it is all tied to the voting rights, which would be tied to the issues of tokens. So similar to shares, if somebody owns 80% of the shares, they probably got 80% of the power, that sort of thing. Decisions are made via proposals, the group votes on during a specified period, and the money gets controlled by, via built-in Treasury. And that is only accessible with the approval of its members. So things like fraud are pretty hard to achieve. What are some of the key issues that get solved with a Dell versus a traditional entity? Well, a traditional organization requires a lot of trust in the people behind it. This is especially true on behalf of investors and they're removed from the day-to-day running of the organization. They need to have a lot of trust in the people that are running it. With a dao. You only really need to trust the code itself. The code that sits on the smart contract. Because every action that allow takes after being launched has to be approved by the community and it's completely transparent and verifiable. Lack of hierarchy means any stakeholder can put forward an innovative idea and the entire group will consider it, improve upon it, voted in, reject it. And internal disputes are often easily solved through a voting system. And this is in line with pre-written rules in the smart contract. So it's a critical thing that if you are going to set up a dao, that you pay a lot of attention to the smart contract because that will either set you up for success or failure down the line. Members of a dao have their interests aligned to the DAO as the nature of the doubt incentivizes them not to be malicious, but rather turn into advocates of the organization. And for me, this is one of the critical benefits of a Dao. Let's look at the example of a community. If it's governed by a dao, the members of the community would be incentivized to be active. There'll be incentivized to promote the community, to mute new members, and to help. Not only do they get the benefits of this thriving communities that they're a part of. But there are also rewarded since they'll have a financial stake in the success of the community becomes their success. And they're rewarded with things like the token that they purchased growing in value over time. Now, I know what you're thinking. This sounds brilliant. It's brilliant in practice, but do members want to vote on every single issue? Do we want this to sort of very pure democracy here? Well, look probably not once an organization grows to a decent size, there's just too many decisions that need to be made and voting on every single decision that would become this massive bottleneck. What a dao can do is delegate authority in a similar way to shareholders, delegating authority to a board or CEO in a traditional organization. Although there is one key difference and that's that you've got the full transparency of the decisions that are made and all of those checks and balances in place because everything is sitting on the blockchain so you're able to follow the money and not just rely on this carefully crafted report. As we often see with traditional organizations. There are some hurdles to widespread adoption, though Dow's can be distributed across multiple countries and jurisdictions. They kind of, you know, the internet native. They don't fall within any particular geography, so there's no legal framework for them. And legal issues that may arise will be probably pretty complicated to solve. There are countries that are starting to look into how they can support the adoption of doubters and new governance system. Because as we've just seen, there's a number of upsides, but I expect that this would take some time to become commonplace. One of the massive issues that we see with doubts though, is that third-party transactions outside of the web three space it pretty difficult to achieve because there's no legal entity to enter into contracts, like hiring staff in a traditional way or opening a bank account. You would need to employ an agent to act on your behalf. Then that kind of a road, some of the value proposition as you start to reintroduce these activities that happen off the blockchain. And then you've got points of failure like transparency, fraud and so forth. In the US. It's a it's a completely different stories. So the SEC issued a report in 2017 determining that Dow's that have sold security in the form of tokens. Kind of how it works, violated portions of the securities laws. So you just need to be very careful that if you're in the US are a citizen of the US. But I do encourage you if you are looking to start a doubt to check how that may sit in your country. Dow's do have the potential to change the way corporate governance works completely. There's a massive future for them. But I think it's going to take some time for the concept to mature. This legal gray area where they operate today to be cleared, more and more organizations will probably adopt the downloadable to help govern some of their activities as time goes on and expand this over time versus just going headfirst into the deep end from day one. So LFTs, you've probably got some questions about this emerging platform. Look, you've no doubt seen headlines about people paying house money for a clip art of a rock or doodles that you'd be proud of your four-year-old for creating. You're probably thinking what the **** is going on. This makes absolutely no sense. Well, there's more to it than that. But first let's go through and understand exactly what an NFT is. An NFT is a non-fungible token at which probably still makes no sense to you. But the easiest way to explain it is if you imagine an NFT being one of a kind trading card, it's unique and if you were to trade it for another trading card, you get something different in return. Whereas bitcoin, for example, is fungible. If you have one Bitcoin and I have one Bitcoin and we swap our Bitcoins. We still both have the exact same thing that we started with. If T sit on the blockchain, which most likely today would be on the Ethereum blockchain. But that's changing and we're seeing NFPA pop up on other blockchains to in an effort to reduce transaction costs. And we're getting to that a little bit later on. The main difference between say, an NFT and a cryptocurrency like Bitcoin or Dogecoin or, or any of these main coins is that there's a little bit extra information stored on the blockchain metadata that can link to digital assets. It could be an image, a video game. Whatever. Christie is the famous auction house auction off a 10 second video by people and it's sold for $6.6 million. Yes. I just had to check. I was reading that right. That's 6.6 million US dollars. And here it is. The awkward thing is that you can download the exact same file that the owner received, mind-blowing. But LFTs are designed to give you something that can't be copied and that's ownership of the work. The artists can still retain copyright and reproduction rights, just like they would with a physical artwork. But let's put this in terms of physical art collecting. Anyone can buy a Monet print, but only one person can flex that they own the original. Is there any more to it than that? Well, look, it can be argued that one of the earliest NFT projects, crypto punks, they've also got a bit of a community around them. And there's various other animal theme projects like board aid Yacht Club. They've also got a bit of a community around them as well. Or the activities of these communities do vary from one to the next. But if we take Board app owners, for example, it seems to involve vibing and sharing memes on Discord, complementing each other on their Twitter avatars, that sort of thing. You might be thinking, What's the point to all of this? I think it really depends on whether you're an artist or a buyer. Let's say you're an artist, you might be interested in LFTs because it gives you a novel way to sell work that they're otherwise wouldn't be much of a market fall. You may come up with a really cool digital sticker idea. But how are you going to sell it? You could sell it on the iMessage App Store, but you might struggle to get much in return. People are doing these sorts of things and doing very well out of it today. But I think it's worth noting that a lot of the success may be short-lived. If you're an unknown artist and you're putting these sorts of things in NFPA marketplaces, you might be able to make some cash today, but you may not survive the hype when marketplaces become oversaturated and it's coming. One of the key features for artists though, is that you can enable a royalty so you get a percentage every time your NMT is sold. And this makes sure that if your work it's super popular and the value skyrockets, you'll see some of that benefit as well. This is unlike traditional art where you could be an unknown artist and sell a painting for a $100 today and then become widely successful in the decades to come for that artwork to later sell for a million dollars. But you, the artist would still have only made $100. In this case every time it trades hands, it's built-in to this NFT that you're going to get whatever royalty you said, 5%, 10, 80% percent. Typically royalties for art seems to be somewhere between 5, 10%. Every NFT is unique, right? Well, technically yes, every NFT is unique. There is a unique token on the blockchain, but it's also possible for collections to be released. So you could release 50 or a 100 of numbered copies of the exact same artwork or derivatives of the same artwork. And this is what we're seeing quite a lot of the number of copies though is transparent and then that of course, influences the value. From a buyer's perspective, one of the obvious benefits of buying art just in general is that it lets you financially support the artists that you like. So this is true with these LFTs as well. Buying an NFT also usually gets you some basic usage rights like being able to post the image online or set it as your profile picture. Plus of course, you've also got those bragging rights that you're the one that owns the art and you've got a blockchain and treat it back it up. But if teaser, like any other speculative assets, like a painting, you can resell them for a profit as well if the demand is there and there's already marketplaces popping up, such as open C dot IO, where people are trading LFTs today. What do I think of NFT out? Well, look, I'm probably not going to go and start plotting with my hard-earned money to fill my crypto while it would clip art of rocks. But what I am excited for is how people use NFT is in new and novel ways in the months and years to come. For example, we're already starting to see NFT is being used in games. And this is for the game creators to be able to sell unique items. Like it could be a particular gun or a special helmet, or some clothes or something like that. You can purchase this NFT, which gives you the US to use it. And then you can also trade this as well. So you've got something to flex and this is something that people in that space do appreciate. We have also seen in the universe where companies are selling virtual plots of land that could then be developed by the owner in the future or traded or wherever they might, may like to do with that virtual plot. There's also been some attempts at connecting NFT to real-world objects. And I think this is where things start to get really interesting. And we're starting to move away from some popular but perhaps short-lived uses of LFTs today. If we look at Nike, they've painted and a method to verify sneakers authenticity using FFTs, and they call it Crypto cakes. And we're also starting to see some other luxury goods providers do similar sorts of things as well. There's also people using NFV TAs for all sorts of other sorts of things today. So think of event tickets and could be physical or virtual. You can also sell media like music, TV shows, movies. And what we're also starting to see actually growing quite a lot in the last few months as people selling and FTEs to access a paid community or to access a particular sass tool. The opportunities really are endless and I genuinely think that will start to see some really cool uses of LFTs in the near future. And it's definitely not gonna be constrained just to $1 million cat doodles. I told you I was gonna talk about spot contracts. So bear with me for a moment as we get a little bit more technical. There is some method to my madness, and I promise it's important background knowledge for some of the later sections. The architecture of Web three applications, or more commonly, ups or D apps, are completely different from web to applications. And if we look at a popular web to site like medium, it's a simple blogging site that lets users published their own content and also interact with content from others. There's a few things that need to go on behind the scenes for a website like medium to work first, there must be a place to store all of the data. So that's all of the user's information, the content of those posts, comments, likes, and all that sort of stuff. This requires a constantly updated database. Second, we've got back-end code that's written in a language like NodeJS. And this defines all of the business logic. For example, what happens when a new user signs up? What happens when they publish a new blog, they comment on someone else's blog, that sort of thing. Then third, we've got front-end code, and this is typically written in a combination of JavaScript, HTML and CSS, but there's a bunch of other different languages as well. But you get the idea. This defines what the site looks like and what happens when a user interacts with the site, when they click on a button, what the color of the button is, all that sort of stuff. We put all of this together and when you write a blog post on Medium, you interact with the frontend, which then talks to its back-end, and then the back-end talks to the database. And all of this code is typically hosted on a centralized server to be something like AWS or Google Cloud. And you as the user interact with it through the, through the web browser, Chrome Safari, Internet Explorer, if you're game enough. And that's kind of how it works. And this is a pretty good high-level example of how most web two applications work today. What's the difference with Web three? How does it, how does it work in the Web three world, unlike web two applications such as the medium example, web three eliminates the middleman. There's no centralized database storing all of the data. There is no centralized Web server where all of that back-end logic resides. And I can look probably give you a far more lengthy and comprehensive explanation, but at a high level in Web three, you can write smart contracts and that defines all of the logic of your applications. And then you deploy those onto the blockchain, the traditional web servers and databases that are no longer needed because everything either happens on or around the Blockchain. Smart contracts are written in code and popular language to write a smart contract in is Solidity, which has a lot of similarities with JavaScript, but it's not JavaScript. And then sitting over the top of that is the front-end. Now the front-end doesn't really change a great deal from what it is today. Those two things together become your dApp. Alright? Now that covers the most basic implementation of Web three. But there is one thing that we haven't mentioned yet and that's storage. Storing everything on the blockchain gets really expensive, really, really quickly. Once you kind of move beyond simple text, which you can quite happily store on the blockchain, you will want to store much larger files. So if you've got images and videos and things like that, you typically would store those files on a P2P network called IPFS, and then save the location of that file to the blockchain. The future of the web is Web 2.53. So three purists, I probably going to try and find me in a dark alley after watching this video and break my kneecaps for saying it. But look, I really believe that the future of the web is most likely going to be somewhere in-between what we have today and this pure version of Web three based on what we know and where technology is at. But it could all change. It's a little bit like this image that you can see there. We've got this multi-generational effort to get the task done. I'll take you through a detailed example a little bit later on exactly why Web three isn't suitable for all projects. Please don't hurt me fanboys, It's true. But in the meantime, let's just look at it. Very simple and stupid debate, at least in my opinion, that's happened not that long ago. Bit Cloud. And for those of you that are not familiar with big cloud, it styles itself as the crypto social network. It's built on a blockchain called Desso. And Matteo will talk about day So a little bit later on because they're doing some really cool stuff and we want you to know about it. Anyway, a big cloud, it's not fully decentralized, but it's clearly playing in this Web three space. And there's this expectation from people that it's pure Web three and its upset a few people for no good reason, in my opinion, if you look into bit Cloud's documentation, it states that there's parts of bit clout that are centralized or semi-centralized. There are parts that are completely decentralized. So things like storing of images and videos are centralized today and stored in a similar way as you would in the web to space. They say they'll look to decentralize everything in time and move away from these centralized servers. And they've come up with these fancy term to describe this, which I think a lot of people are probably going to use in the next few years called progressive decentralization. But you've got to ask what's the point of going down that path other than being able to claim that you fully decentralized, what benefit does it give you? Should you even bother at all? Well, I don't think that there's anything wrong with that from a technical perspective, as in, there is nothing wrong with taking this hybrid approach. In fact, it's a good idea to use centralized servers where it makes sense since they're far more efficient and cheaper. My advice is always gonna be to use the best solution for the problem at hand and not attempt these one size fits all pure approaches because it's just not needed. There will be plenty of good reasons to use Web three of the web to plenty of them. But if you're storing something like a photo for someone's profile, does anyone really care if that sits on an AWS server? Even if that AWS server blows up, very unlikely, probably also backed up and that photo is lost in this hypothetical situation. Or if someone was to hack in and make it change to it, change your photo to a picture of a cat. It's not nice, but it's probably not gonna happen. And it probably doesn't warrant this extra effort. And mind you cost of putting it on the blockchain. The only thing storing something like that on an AWS server does is undercut all of these high-minded talk about width three, decentralization. On the flip side, if you're running an app, let's say that it stores entry and exit data for a high security government building. There's clearly a strong case to leverage blockchain for that. So be smart about it and use the right thing. Don't attempt these One-size-fits-all approaches. Alright, so by now you might be wondering, how can I access the Web three is a regular user of the Internet. Well, the first step in your journey is to acquire a Web three wallet. Went through wallets are an essential part of interacting with Web three, and you really won't get far without one Web three wallets or digital wallets. So they had the ability to store and interact with digital assets. And this includes everything from cryptocurrencies to NFT. But they also manage your identity online as well, allowing you to interact with those. The apps we just mentioned, there's different types of web, three wallets. They fall into two quite common categories though, you've either got software or hardware. We're gonna focus on the software. Wallet says they're the most common. The most common digital wallet is MetaMask, which is available as a browser extension and as a mobile app. It allows you to purchase, store, swap, and manage all of your digital assets. It also allows you to connect with DFS, as we've mentioned. And it works a little bit like logging into a site with a social login, like a Google or a Facebook, just a couple of clicks and you're in, without getting into a detailed explanation as to how it works behind the scenes, your crypto wallet essentially holds the private keys needed to access and authorize things on the blockchain. People may be able to see that your wallet owns an NFT, for example, but it's the private keys that would be stored in the wallet that would be needed to actually transfer it to a different bullet. Now, what I'm gonna do is I'm going to play a short two-minute explainer video from metta mosques that should hopefully explain things far quicker, simpler and elegant than I could enjoy. This is saying CM uses the Internet, just like the rest of us. Lots of apps for you uses seemed to be free, but they actually come at a cost. She knows the Internet isn't very secure and strangers own her data, credit cards or stolen identities get hacked. She has to navigate a maze of ads just to surf the web. And she knows someone is always watching, but she's heard there's a better way. And then sam sees it. The promise of a new Internet powered by the Ethereum blockchain, an amazing combination of technologies the world is building together that are reinventing how we connect to one another. And it's just within her reach. But to access this new world, she needs the right tools. Meet MetaMask, your connection, the new way, MetaMask is the tool SAM needs to access this new world. It's a key that connects her to new types of applications. It's a wallets that keeps her data and valuables safe and sound. And it's a shield that protects her from hackers and data collectors. With MetaMask, Sam is ready to explore this new internet safely and securely. The possibilities are in place. Sam can use next-generation applications that give control back to the users and the community. One her data and move seamlessly between sites and send money across the world at a fraction of the cost. Create new organizations with new currencies that binds her communities together. Crowdsource projects in art, or invest in other people's creations. Sound too good to be true? Well, with great freedom comes great responsibility. Sam controls her own identity on this new internet. No more new passwords for every site she visits. Just a secret phrase that controls her accounts. This phrase is her login, her password, and her proof of ownership all wrapped up in one, so Sam has to keep it as safe as she possibly can. Now that she's installed MetaMask, Sam's ready to explore the best version of the Internet, vote crowdfund buy stuff published, writing, make art, hire freelancers. What we'll see him do first, whatever she wants. The Internet is hers to explore. Welcome to a new kind of Internet. Welcome to MetaMask. Despite the large sums of money made by people who own Bitcoin or Ethereum. I've always viewed the movement as anti-capitalist. That couldn't be further from the truth. The movement is really about doing one of the most capitalist things ever made. I'm talking about cutting out the middleman. Basically in week three, we are talking about a more direct connection between suppliers and consumers. In this relationship, fans, followers become investors and stakeholder. That creators can actually monetize the social capital and currency. In NFV is, we can now prove that we have created an own specific digit that acted unprecedented on the Internet. And FTEs create a supply scarcity and triggered new digital economy dynamics. Though the present and the future is 2.5. Whether it doesn't mean Web T2 goes away just like web to did they mean Web one went away? Finally, if you remember, we said the web one was read-only because people could only read the content than Web T2, we said, is read and write because user-generated and consume content on social networks. But how about Web three? Well, three is read, write, and home, as you can see in this table here, because user can easily create, consume, and own content online. The colon ethos of what three is the intermediation. Taking away the middleman by enabling through peer-to-peer social and transactional relationships. The way mass value is being created on the web is through communities of people coming together, collaborating, being part of something. With 19 ownership and payment layers built in Web three has the potential to fundamentally rewire the core social and economic structure and deliver on peoples and consumers. Steve desire to be part of a creator, brand, passion community. In refreshing new ways. Web three is foraging stronger and more direct connections between creators and fans. Tuning passive audiences into active members and stakeholders, creators are looking to engage their fan base in more meaningful and value and enhancing ways involving them. Enough co-creating process and sharing the upsides, that is allowing a different kind of patronage with fans turned into equity stake holders in a combined cultural value and upside, the questions that Web three people ask themselves are something like, why subscribe when I can invest? Why just participate if I can partake in the value being created while just play, when I can have a say as well. In Web three communities, crypto tokens can be used to reward status or contributions, and specific utility and privileges can be attached to these tokens to provide additional benefits to talk in holders. As with equity shares, this could wholesome be linked to certain voting rights or governance permissions. And the attached utility isn't just restricted to the digital word, but can provide access to other benefits in the physical award as well. Community TdT tokens combined access to online to offline products and experiences with financial and tradable value. Tokenize community with bridged existing created economies to become through ownership economies with members, consumers, and fans, and joining a direct connection to the creators they love while having a stake in the collective value upside. Ultimately vibrant and engage communities are perpetual promoters that drives network effects and positive feedback loops for growing community engagement and acquiring new members. This is why one of the main Web three promise is that communities we'd replace ads, marketing, and social media as we know it. 6. Projects that make sense with Web3: Okay, So we've gone through a lot of the Web three fundamentals and told you all about the great things that it can do. But it might still be a little bit fuzzy and disconnected at this point. Yes, you could create a DAO or you could release an NFT. But what, for what purpose, in what contexts? How did these building blocks end up in an actual product? We'll spend a few minutes leveraging what we've learned so far in the context of actual products that make sense today with Web three. Now this is by no means an exhaustive list, but it's just to give you an idea about how those building blocks are applied to solve real problems. The first step is communities. Now, this is probably one of those much more mature projects to take on today with width three technology. And by doing so, you unlock a bunch of benefits. Now I'm not talking about building a website revision of slack or Discord or whatever. That's not what I mean. I'm talking about specifically about the community that might sit on those platforms. I think a lot of you are probably like Mateo and I, in that when you open up Slack or Discord, you'll see dozens of communities that you've joined at some point in time. Some of them you might still be active in, but most of you are probably just be a passive lurker popping in from time to time when you need something from it or there's probably some that you haven't stepped foot in, in months or even years. A Web three community, on the other hand, may still sit on Slack or Discord, but the dynamics will be a little bit different. So perhaps you had to purchase an NFT to join that community. While either you hold that NFT, you maintain your access. But if you're no longer interested in the community, you can sell that NFT and you can have your access revoked. Why is that important? Well, you and the other community members will probably be more engaged as you'd be looking to get a return on that investment in the first place. You'll probably also be happier to buy that NFT knowing that if or when you outgrow that community, that you can ideally recoup that investment, maybe even for a profit after all, if you help create this desirable community culture and grow this community, the value of that NFT will increase. There are also a bunch of other things that community managers on the other side could do with width three tools such as easily rewarding engagement with tokens, or another width tool that can be used as a dao. In fact, what we'll probably see in time, his community management move away from this centralized structure, which we've become so familiar with to those governed by a dao. And those members will change in time and it will live on and have a life of its own. This community will govern itself. We've already gone through that in a bit of detail, so I'll move on. There's a couple of other major types of for-profit crowdfunding platforms are models that exist today, excluding things like Go Fund Me. And that's a Kickstarter type model where people pre-sell an idea for a product and then use the proceeds to build the initial run. One of the more recent adaptations will be where people raise small amounts of money from a lot of different people to fund an early stage startup. In this ladder example, the Web three tool that you could use here is a dao. And people have already started doing this. Again, I hope you are clear on the, at least the high-level mechanics of this by now. So I'll go back to these first example, the Kickstarter example. In a typical campaign, what you get is a person or it could be a few people, they started that campaign, right? Then people contribute to it. I don't think with money, so they'll contribute their hard-earned savings if they liked the goal of the campaign and what they'll get back as a reward could be that invisible air umbrella before everyone else. And before you ask yes, that's a real product that raised a $100 thousand on Kickstarter and not surprisingly, was never shipped. Web three allows you to turn that equation a little bit on its side, maybe on its head depending on the implementation. For instance, community members can contribute to a project in other ways if they cannot afford to contribute financially. Budding writers to creative designers and social media influences anyone from any walk of life really could join that campaign. They could be rewarded with social tokens and that could be put towards a discount on the product or in exchange for cash. Or maybe they just get bragging rights forever stored on the blockchain that they contributed to that product. By rewarding and incentivizing their communities, the makers of a product can build a highly engaged community that advocates for that product, making it more successful, but maybe also allowing them to focus on building the product unless on the marketing. If we move on to marketplaces, I'm really excited to see what people would do with Web three or what they will do with marketplaces using web technologies. So thinking back to that section earlier where Matteo explain the issues with web two social networks. Well, a lot of this stuff also applies to marketplaces, and it's the perfect example. And I know it's a little bit of a cliche, but it's Uber. I'm sure we've all used Uber by this point. We've no doubt noticed that it's not as cheap as it once was, rises significantly more expensive. And the promotions that you used to get all the time, a few and far between the cost to get this lukewarm pasta delivered for Dina makes you vow to start cooking again tomorrow. You're probably not going to though. This big shift that Web three allows in this space is to limit the control of any one platform. Uber has spent billions of dollars attracting its uses and now it's in this phase of extracting value. Sure, while you can use an alternate ride-sharing service to get home from a night out, there might be half the price. There's no cars available or if the pickup time is 20 minutes, you're probably still going to order an Uber when you're ordering a late night snack on the drive home and you really want to pizza from that one place that makes it exactly as you like it. You'll use Uber Eats to order it as they aren't on the other platform that you've got a $20 coupon for. In a Web three marketplace, that pizza place could have its menu on the blockchain and platforms like Uber Eats, DoorDash or whatever could pick up that listing and facilitate the sale. But because those listings will be available to them and any of their competitors just the same. You may have this similar equation on the other side with the riders that they work for a number of different platforms all at once. They won't be able to charge the high fees and take advantage of their market dominance as they can today. They become a little bit like electricity companies. You get the same product regardless of the retailer. Those retailers have limited levers to pull and it's a heavily competitive market with low commissions and fees. Moving on to the creator economy and we'll go through some actual real-life examples of these a little bit later. But for the creative economy, you can do all sorts of things with NFT is Dow's and so forth. But I think what we'll see for the most part starting to emerge is create a rare coins. And we're already starting to see these today. So just think back to that example that Mateo disgust with RAC. Alright. Metaphase. I know we haven't really touched on the reversed yet. And to be honest, this kind of deserves a course on its own. It's a really loaded topic, but the many verse at its core is like a community. You might be part of a virtual world that's governed by a DAO, or you might buy an NFT to attend a virtual event in an otherwise public virtual world. Or you might even by some virtual Nike sneakers for your avatar. You look extra cool at that next virtual work meeting. I know it all sounds a little bit far-fetched today, but people are doing these things. It's definitely a thing. Verification services, okay, So this is by far one of the least sexy but also important implementations of width three technologies. One of the superpowers of the blockchain is that it's immutable. It means that a block can't be modified after it's created. This is in contrast to mutable objects which you guessed it can be modified after they created like a traditional database. If you then add in this ownership, it's pretty difficult to spoof. Like it would make it hard to fake someone's credentials, such as a degree or a license or lie about working at a particular company. If it was commonplace for these things to live on the blockchain. And there wasn't entries for this person when they say they should be like if they said they went to this particular school and they got this degree and the entry is not there, probably lying. Another application is KYC or know your customer. And this is one of the very early non cryptocurrency uses of the blockchain and a number of companies offer this service today. Why this works so well is that you can verify customers sensitive documents. Save that a verify verification flag on the blockchain by way of a smart contract, and then securely purged the sensitive documents to remove the risk of that actors tampering with the verification or gaining access to the sensitive documents. For example, my employer would only need to cite my working right, say by viewing my passport, then save that result on the blockchain, and then not need to keep a copy of my passport to take this step. One step further. Imagine I worked for labour hire company are lots of short-term projects. It could be typical for your sensitive documents to be shared with each of those employees that you might work with, meaning that by the end of the year, maybe dozens of employees have a copy of your passport by the end of ten years when their passport expired, it could be in a hundreds of different companies hands. There's a decent chance that some of these companies may not store this in the most secure way. They may have a data lake and that would expose your personal information. In a Web three world, each employee would only need to be provided with the address of the smart contract that verifies that you have working rights as cited by XYZ and labour hire company, which people know and trust and would clearly be on the hook should it later turn out that you didn't have those work rights to begin with because that smart contract that's on the blockchain and they can't edit it and it clearly says that they checked it and that you had those working rights. 7. Projects that DON'T make sense with Web3: Okay, so you've started to learn a lot of super awesome stuff that you can do with Web three and it is very easy, super easy to get carried away, believe me. Yes, the underlying technologies will start to weave their way into our lives in the coming years more and more. And they'll hopefully unlock a lot of benefits along the way. So either be by doing existing things in a different way or perhaps opening the door to new products and services, or even experiences that just haven't been possible yet. Let's look at an example of the universe and there's experiences happening in there that are completely new and delivered in a way that's just not exactly possible with existing technologies. But as technology stands today, it can't and won't completely wipe out everything that we know and love today. In fact, this was the same experience with the transition from web one to web two. Web tooting come along and completely wipe out all these web WAN technologies and render them useless. I did render some things irrelevant and new technology was created along the way. But in many cases, web to simply built on top of web one to provide a better user experience. And the same will be true for Web three, hence the notion of Web 2.5. So some parts of the web today will remain relatively unchanged. Some will be massively disrupted, and others might just have a few parts upgraded along the way. Let us illustrate this a little better. Let's look at an, at an example email for example, there's been web two platforms that have come along and they've modernized this e-mail experience a little bit. And we can take Gmail as an example. But the underlying technologies, the protocols that are used to send and receive email, these are still very much web one. For example, the protocol is SMTP. It's still used today when you send an e-mail from your Gmail account. The main difference being that today you don't run your own email server and your email isn't stored locally on your computer. It's stored in the Cloud. It's accessible across all of your devices. So it's become a bit of an established joke that blockchain are a little bit more broadly Web three technologies are in a bit of a search of a problem to solve. And this is obviously deliberately provocative. And it's designed to ruffle the feathers of Web three die-hard enthusiasts and fans, but there is a bit of a measure of truth to it. People are using it like this in a bit of a way. There's a risk of trying to fix a lot of things that aren't broken and rebuild them with Web three technologies for no real benefit. Or you rebuild them with Web three technologies and you actually take away a bunch of things and you end up with a worse, more inefficient product. Let's continue on with the example of e-mail. Is there a likely scenario where in a few years time all of our emails will be sitting on the blockchain. Emails, this web one technology with a few web two things bolted on. So surely Web three is going to come along and completely change it bold. It's highly unlikely. In fact, it's already been built. Ledger male. This is a product that exists today and it's builders. The world's first decentralized email solution promises to liberate its users from invasions of privacy, insecure message transfer protocols, SMTP, and abuses of centralized power, gmail. However, ledger male also makes way with a number of aspects of traditional email that people might actually want to keep. In fact, so fundamental as some of these differences, it might be considered misleading to characterize ledger male has an email service at all. Let's start with some of the benefits. And the classic one, which is probably the number one on every list of creating something new with Web three will be decentralization. But there's no single entity that's responsible for green lighting, verifying, and processing the emails such as Gmail. Immutability can be a big one depending on what you're using this email service for. Once a transaction has been verified by this consensus vote, these things that happen on the blockchain and it gets recorded, Well, it can't be altered, deleted, or otherwise tampered with. And you've also got auditability. So while people can remain anonymous, all the transactions that are open to public scrutiny. Although ledger male users can still feasibly send malicious content through ledger mail from one person to another. Things like identity spoofing, phishing attacks. These things are made much more difficult with a waitlist style mechanism in conjunction with the natural transparency of a blockchain based system. Ledger male also encrypts all messages and content, such as attachments, which means only the sender and recipient can possibly gain access to the material. This is different to standard web to e-mail services. You might be thinking this all sounds pretty good. You're going to pause the video. You're gonna go sign up for ledger male. Now relishing the fact that when you do get that email from a Nigerian prince and they promised to send you. That $100 million, you'll know that it's genuine and you absolutely should transfer his lawyer $500 to sort out the transfer. Well, hold on a second. Ledger male sits atop a little known blockchain called shin fin. And this draws some, some things from both private and public blockchains. It's a proof-of-stake network and courtesy of a number of clever design features, shin fin BOS at pretty decent throughput, which is little higher than Bitcoin or Ethereum, achieving upwards of 2 thousand transactions per second. That means it'll be capable of sending 2 thousand emails each second or a 173 million in a day. It sounds like a big number. But that only works out to be about 0.06% of the roughly 320 billion e-mails that currently pass back and forth each day. So yeah, it's a splash in the ocean, but also don't forget that ledger male wouldn't be the only service on shin fin. It's just one of many. So in reality, the capacity would likely be far lower depending on what else is happening. Scalability would probably be the number one limitation, preventing blockchain based email. And then closely following in behind this becomes cost. So yeah, costs to send an e-mail like all public blockchain networks. Every transaction costs. After all, someone needs to pay the miners for their efforts. You can't expect all of these different nodes on the network to verify that princes real and do it for free. You might be asking how much does all this cost? Well look, it's probably not going to take food off the table. It's roughly 108 hundredths of a dollar to send a legend mail email today, a bit of a tongue twister. However, the value of the transaction phase is tied directly with the amount of traffic on a network. So in this hypothetical scenario where ledger male becomes immensely popular and uses flood to the shin fin network, e-mails, it becomes significantly more expensive. Given only a tiny fraction of people currently pay for the privilege of sending email in the first place, like businesses sending mass mail outs and so forth. It's difficult to imagine the concept going down well at all, where individual users are going to be paying for every email that they send when they can currently do it for free. The single largest problem with Leger male, however, will, depending on which view you look from is that it's a bit of a closed loop system like WhatsApp. You can send messages to other uses of WhatsApp, but you can't send on WhatsApp to someone that's only using iMessage. So this means that users can only deliver messages to other people that have a legend Mel account and even then, only if they feature on the recipients approved list of contacts. It also only works with certain web browsers and doesn't work on mobile. So you can forget checking the email and your phone. Okay. I don't know. I've been quite rough on ledger male, but I'm really not convinced, practically speaking, there's probably a niche market for it as it does offer some benefits over traditional email things like the encryption, things like the immutability and the auditability. But I don't think it's something that most people are gonna want to use. Why did I talk so long about ledger male? Well, it's to highlight some of these limitations of Web three right now. That mean that look at simply isn't practical to just go and use it for every product that you might want to go and build. The best way of illustrating what it's like to build a blockchain based email client in 2022. It's like these ladies fashion choice to go to the supermarket and I'll leave it there. Let's recap this because it's been quite a loaded section. What are these key limitations of Web three today? Well, scalability, these transactions are slower on Web three because they're decentralized changes to state like payment, they need to be processed by a minor and then propagated through the network. It's not simply updating a database as you do with a traditional web to stack user experience. Interacting with Web three applications can require extra steps. Software and education are so this can really hurt adoption and things that are simple today just become a little bit more difficult. Accessibility. So the lack of integration in modern web browsers makes web three less accessible to most users. For example, it's very difficult to use. Web three wallets on Safari. Minimise doesn't work on Safari. Cost most successful d apps and put very small portions of their code on the blockchain, as it can get really expensive. And we call these transaction fees here to mean something on the blockchain gas phase. I just think transferring all of these transaction costs to the end-user, even if they're really, really tiny. But you've got to ask people all along the way to authorize these payments. I just think it's gonna be a bit of a turnoff. If everything I want to do, every link I want to click, I'm having to pay these tiny amounts of gas phase to do it. I just can't see it working in all cases. Sometimes centralization is a good thing. So let's not rule out Web two and go all in on Web three, at least for those things where it just really doesn't make sense. 8. Web3 projects we ❤️: In this slide, you can find a list of our favorite website projects. Now I'll give you my review of each one of them. Let's start with dazzle is probably my favorite Web three projects. It's the first decentralized, such a natural. I joined back in March last year, 2021. The most remarkable feature that these are blockchain provides is that as soon as you create an account, the system as size you are crypto wallet and means a special token associated with your profile. In my case, my profile angle is matter Moscow. The cryptocurrency automatically created would be called Martel Moscow. Users can then trade, buy, or sell my material most car token or other user's token to earn the upside or lose money if they bet on the wrong creator. Another exciting feature is that you can get a post. If you like content that I create story sharing, you can send them a small crypto tip, same as you would do with likes. But in that case, a crypto transaction attends behind the scene from your wallet to the creators were outlet. It says math way to demonstrate respect and reward talented creators. Beat file.com is the first node on top of the days of blockchain that they released back in February last year, 2021. But now promising nodes are coming up every day and you can find them on beat hunt.com. Basically the equivalent of product talent. But with bezel projects only. Ultimately Desso has a solid and active community of Web three makers and early adopters. So if you want to start your own decentralized social network, I strongly recommend to join the Discord server. Next one is super fluid. These projects can potentially change the way users get charged on the Internet. Basically, instead of a single or potentially recurring payment made monthly or yearly, superfluid charges users based on the time they spend using a specific service or consuming content. Think about reading a blog post or listening to a podcast. Superfluid would provide the creator of the content with a constant crypto cashflow proportional to the time you spend consuming that content. Open. See, I don't think there is much to say about this project. It's a marketplace where you can submit or discover and FTEs. By of course, if these in the assembled one, it processed more than 3.3 billion worth of sales, generating about 82.5 million in revenue for itself. Today, the company employs more than 70 people, and I think it's impressive. Next one is unlock. This one is a smaller project, but still interesting. With unlock, you create locks that you can place anywhere to lock your content on your website. For example, using Kempe would chase memberships as NST keys that grant access to content tickets and anything else you'd like to monetize. Milan is a social network where you can share content like videos that get automatically minted as an FT before getting shared, then you can buy and own your favorite creators moments. Think about TikTok, but with trading capabilities, I mean, buy and sell a viral video to earn money. Brave is D Privacy Browser is noun because it blocks attack truckers and it protects you from being tracked online. What picked my interest here is their token called BAT, BAT, basic attention token. So basically they blocked every ad on the Internet while you're browsing. But they provide a reward system that makes you earn money by watching ads. Basically, advertisers budgets go directly into your pocket. And instead of unknowing you while you're watching YouTube videos or with those banners everywhere on websites. They asked CHI you to actually go and take a look at their ads. So they reward for the time you spend looking at their ads. Check out the website for more info. Rally is where you go to create your own such as token or by cell other creators tokens. This is a promising project that in 2022, I think is going to gain popularity. I even portrayed some of their token dollar sign r, l, y. But this is not a financial advice and actually just a small disclaimer, if you're investing in crypto is risky and you should be careful. Rabbit hole is where you learn how to use the centralized apps, but it is also a matter blazed that connects web three enthusiasts will want to learn more about BAPS with Web three founders looking for early adopters. In fact, you earn money while discovering new projects. These money, it comes from what the founders were willing to allocate some budget to find early adopters. It's a match between adopters and Web three founders, but also a learning platform to learn and understand more about Web three projects. The last one is called Islands. Remember we talked about the direct connection between creators and farms. These tool is a community platform that enables creators to use Web three tools and dynamics in their community. It includes two main features. First one is an NFT marketplace and that did in the platform so that creators can sell NST, right where their audience is hanging out online. Second, app token gated threads feature basically an automatic way to hide show premium content depending on how much community token you own. 9. How to build web3 apps with no-code: Let's talk about no-code tools now. We start some bubbles on the platform that I teach on super build. I can tell you a lot about this. I tried to summarize everything with a list of features that I think the bubble provide. And that differentiates these platform from the others out there, lets you build apps without writing any code using a visual programming approach, basically, you can drag and drop UI elements like text fields, inputs, checkboxes, images it directly into your project. And in a matter of minutes, you have a fully functional front-end app. You can then connect that front-end that you created by dragging and dropping elements with a backend by defining what bumble calls workflows. Basically, workflows are sequences of actions that get triggered when your users do something like authenticating, for example, Sign-up, login, logout. All these actions, by the way, are available by default in bubble. However, if I had to choose my favorite bubble features, this will be the plugins marketplace. Thousands of developers on building plugins you can easily install in your app to extend its capabilities in his eye and you can find a link to my favorite it once, it's in the upper post, I've written with my best plugins. For the pros. If no code is not enough with bubble, you can easily run custom code in JavaScript and HTML so that you can build any custom features you want for your web app. All right, So Matteo is taken you through all these awesome projects that we love and your brains. Were we going a mile a minute with a bunch of things that you want to go and build. If you didn't already have a few great ideas already. And he's no doubt convinced you that bubbles a great tool to use and you want to get started on building. Okay, so when we were originally planning this course, we were gonna make it a lot more technical with lots of time sitting there in the bubble editor building things and had the course centered around a project that we were going to build from start to finish. But that was obviously going to take a lot of time for us to create and therefore was gonna get delivered much later. It was also gonna be a lot more narrow because we would've had to have picked one product which may or may not have been useful to you. We also wanted to make sure that we spend enough time on providing you with a clear understanding of all of the Fundamentals of Web three. And actually that part of the course blew out in size once we got to creating the content. But we're glad that we did. And I hope you guys have enjoyed the course so far because it is just so difficult to go and start building with Web three if you really don't understand all of that stuff, to keep costs under control and to be as useful as possible for you knowing that there are already so many great plugins and documentation and even some good walkthroughs out there. We instead wanted to focus on the technical building blocks and pointing you in the right direction depending on what you wanted to go and build first, knowing that you could leverage a lot of these great resources that already existed versus paying us to create our own versions for you. Now, if you've been bubbling for some time, you may have heard of the plugin and template developer easy code. They've been putting out with three plugins at a breakneck speed over the last year, but even more so just over the last few months. And honestly, they've made it so easy to get started. And look, we're not affiliated with them in any way. We don't know them at all. All we did was give them a heads up that we'd be mentioning some of their work in the course. We did try to squeeze some discounts out of them for you as some of their plug-ins are paid, which they were happy to give actually. But unfortunately, bubble doesn't support coupon codes and that sort of thing in the marketplace. So unfortunately we tried, we definitely try it, but you can blame bubble for that one. What I'm gonna do now is I'm going to walk you through about seven or eight different plugins and talk about what they do and why you might want to use them. And then there's a couple of templates that I'll introduce it, the end that kind of pull all of this together, pull a few of these building blocks together in the form of an NFT marketplace. And there's two options, one from easy code, but then also one from a competitor as well. So if that NFT marketplace is something that interests, you, then hold on for that piece, otherwise, you can skip ahead. Then I do want to jump into the editor briefly, the bubble editor to show you through one of the plugins. And this is really just to show you that it is actually not that hard to get started into use these plugins. And I'll take you through authenticating someone with MetaMask and then have them send you some Ethereum or Bitcoin or whatever in a shopping cart style situation. Because I would assume that would be useful to all, if not most of you, if you're going to get started with your own web three project. All right, let's get into it. Alright, so as you know by now, it all starts with the wallet in Web three, these managers your identity, but it also holds the keys to your tokens like cryptocurrencies, your NMT is your Dow's and so on. You won't get very far without it. As we've mentioned, there are a bunch of different wallets that you can use, but the one that's most popular is MetaMask. Most people in the Web three space will have a MetaMask wallet, even if they do have other ones as well. So when you're looking at getting started, you should at least have the ability for users to connect with a MetaMask wallet, at least in my opinion, even if you do want to offer connections with other wallets for different reasons. Otherwise it would be a little bit like offering social signing with Pinterest, but not with Google. You're just going to exclude a bunch of users unnecessarily. Now, this particular plugin here, it comes off the basics really nicely, but it does also have some more advanced features as well. What can you achieve? Look, I'm not gonna go through everything in detail because honestly it does a lot and it really depends on what you're building. But let's go through some of the key things that might be of interest to most people. So you can obviously sign up new users without an e-mail or password. So you think of this as something similar to a social login provider, like Google or like the Google plug-in that you can get from bubble. From the bubble side, it works in a similar manner to be honest, but rather than connecting with a third-party server, such as Google servers to authenticate you. It'll connect with the MetaMask Chrome plug-in. Or if you're on mobile, it will connect into the MetaMask app. There's a checkout function. So super simple, this is even useful for those people that have an existing app with a stripe plug-in PayPal, whatever. And perhaps you want to add crypto payments to your checkout. Well, this would be the function that you would use. You can also read but deploy smart contracts onto the blockchain. You can transfer NFT to another wallet. Yeah, like I said, there's a bunch of other things, but these are probably the key things that would be interesting to most people. There's also some utilities as well, things that you may want to utilize for back-end processes, or even things like a checking on the current gas prices. This one is super-useful and maybe relevant for you depending on what your app does. And the reason that it's super useful is that the gas price, which is the cost of executing a transaction on the blockchain that bounces around a lot because it's a supply and demand situation. If there's a lot of activity happening, then the prices do shoot up. So you do have these kind of peak and off-peak times depending on what you're doing. If it's just accepting crypto payments, then look, it's probably not gonna be that much. But if you're meeting NFT, I see you're deploying smart contracts onto the blockchain. This can cost a pretty penny. Sometimes it might cost 70 to 80 US dollars. As an equivalent cost if you're maintaining an NFT on the Ethereum blockchain during off-peak times, but that same NFT to mint it during the peak time might cost $300 or even more if things are super busy. If you're facilitating a transaction that's gonna be gas heavy, you might want to say, display this live cost on your front-end. So it's not a surprise to people because nobody likes to see something for sale for a $100 and then you go to pay for it and suddenly it costs $200. So this is just an example. I digress. Next up, we've got a free plugin, and this is very similar to the previous one, but all it does is just handling the sign-up and login, so it removes all of those other features. And that's why easy coded is giving that away for free. Again, it's not a huge different from having a Google login on your app. Alright, now, moving along. Okay, coin Gekko, this one is super useful for anything wallet related and cryptocurrency related. If you're wanting to build a wallet management app or if you want to have some of those features available to you or you users, then coin Gekko allows you to pull in live, but also historical information. I'm pretty much most cryptocurrencies, if they don't have a particular crypto in their API, then you probably should steer away from it. It's that extensive. Now as to whether you need this plug-in or not, it does really depend on your bubble skills. If you're familiar with the bubble API Connector, then just go to the API documentation on the coin Gekko website and integrate that API for yourself. It is really straightforward and it doesn't take long at all. If the API Connector scares you, then this is the plug-in for you. Now the API itself, the coin Gekko API is free. There is a rate limit, however, a 50 calls a minute, and that's with attribution also on your app as well. If you wanted to make it completely white labeled and avoid that attribution, but also increase your limit as well. Well then for a little over a 100 US dollars a month, you can do up to 500 calls a minute with a monthly cap of 500 thousand coals. So that's a lot. And if you didn't need more than that, well, they do have much larger tiers available as well. Next up we've got file storage. And if you remember back to when I was talking about the apps and smart contracts and how the architecture for Web three is quite different to web two. Well, I mentioned that you can store data directly to the blockchain, which is totally fine for small amounts of texts and things like that. But once you started needing to store much larger files and you're looking at images and videos and that sort of thing. Well, if you don't want to store those things on a traditional Cloud server, like bubbles built-in storage which sits on AWS. Mind you well, you could use things like the pin yada plugin to store your files to IPFS. For anyone that's wondering what IPFS stands for. Well, it's the interplanetary file system and it's basically a peer-to-peer network for storing and sharing data in a distributed or decentralized way. So let's say you're creating an NFT collection that you wanted to then go and sell. Well, you probably wouldn't want to store those things on bubbles storage or on some other sort of centralized storage. Because if you did ever decide to shut down your bubble app or close that centralized storage service, then those files would obviously be purged at some point. And then whoever bought your NMT is probably gonna be a bit upset when the image or video or wherever it is disappears. So this is why you would want to use this plug-in. But as we went through with the example of bit Cloud, well look, it's up to you for things like profile photos or other lower value assets. You may just want to continue to use bubbles storage as you normally would for those sorts of things. But again, that's a cool for you to make depending on what you're trying to achieve. And also I think it's worthwhile pointing out that as with coin Gekko, this plugin is mostly just accessing the pin yada API. There isn't a lot of additional logic or anything like that built on top of it in the plug-in. So you could also just go over to their website. You could create an account, get your API keys and integrate the API or using the bubble API Connector, whatever works best for you. In terms of deep Kenyatta service, they do give you one gigabyte of storage for free. And then it's something like $0.15 USD per gig after that. So it is all pretty reasonable. I, myself have used opinion data a little bit for my own projects and I can tell you that it works perfectly, absolutely no complaints. It's one of the most popular services. And so you really should consider it for anything that you want to deploy to IPFS. Web three back-end. Now this is where the rubber hits the road a little bit more. This plugin will help you with some of the more complex tasks that you might be wanting to achieve. So while on the surface you might look at some of these are functions off to the left and go, oh, that sounds a little bit like the first plugin that we went through. Well, the main difference is that the first plugin is focused more so on the front end. So this is actions that your users might want to trigger, whereas this plugin is going to help you with the backend functions that you might want to trigger or manage programmatically based on your own logic. So an example of this might be a rewarding your users with a little bit of crypto automatically when they complete certain tasks in your app. As an alternative to say, a reward system where you're giving people points. Or perhaps you want to build an exchange for your users, or maybe just as a tool for yourself to be able to trade one cryptocurrency to another or another truly Web three products that you could build with this is a force at app. So if you're not already started playing around with the blockchain test neck. Like green kirby, you use these tests nets a little bit like you would've development server to test whatever it is that you're looking to deploy before you actually go and do it because of course there's gas costs when you go live and you also should never test on a live platform. It's kind of rule number one that you don't break. And it's even more so true in the Web three spaces, you can't just easily overwrite stuff as you can in the web to space. Anyway, you'll use force at apt to get a little bit of tested theory or wherever so that you can then go and use it for your test transactions. Unfortunately though, you can't trade it for the real stuff, but it is super useful for testing. So what you could, if you wanted to, you could create your enforce it app, which are generally free to the end-users. But perhaps you provide this as a way to give exposure to whatever your main product is. Or perhaps you just want to stick a bunch of advertising on there and monetize it that way. Or I don't know, maybe you're just a nice person and you want to help out the community, that would be a great thing to do as well. So you can create your own art, force it using the functions of this plugin. I just want to mention as well that easy code has really awesome documentation, which is why we've spent so much time going through their plug-ins because we think they are well-made and they're also well-documented as well. They documentation sits on git book, so it's the same look and feel to the bubble documentation. You should be able to go through things fairly easily. Spend some time to go through that documentation for any of the plug-ins that interests you and align with your use case. And no doubt they'll answer most of the things and most of your questions along the way, but of course, heat up our community as well if you do need some help. And we'd also love for you to share your success that you have along the way as well. We'd really love to see what you build. Okay, So perhaps you want to build an NFT marketplace of your own. Well, there's a couple of different plugins that you can use for that. Again, both of these are largely just API plugin. So you can decide whether you want to integrate with the API yourself or whether you want to use the plugin. It's worth noting that by using these plug-ins, you're not creating an NFT marketplace from scratch though, but rather you're creating your own marketplace kind of on top of these other marketplaces. It's also worth noting that you can list new LFTs on the Ethereum network with a lazy maintain function and had them both listed on referable and open sea. But once they've been minted, they've been sold to somebody, then they'll only be available to be traded on that particular marketplace. Open seas, definitely the largest and most popular NFT marketplace and referable comes in at number two. So it's definitely one to consider about who you align yourself with. And the reason you might want to create an NFT marketplace is to be a little bit more tailored to a specific niche. Or perhaps you just want a place to be able to show and have your users interact with collections that you've made. Or perhaps you want to make a tool for people to manage their own NFT as well. This would come in useful for that. Lastly, we have a couple of templates and I will just preface this with, I haven't spent a lot of time looking through these templates and kicking the tires on them, but I just wanted to highlight them to say that they do exist and they are an option if they were of interest to you. So the first one is from easy code and there's another one from one tool. The easy code template at the time of publishing is 249 US dollars. And it's the combination of a lot of functionality that you'll find in those individual plugins that we've just gone through. So I won't rehash it all. But of course, it's all wrapped into one fee and with some nice UI elements to get you started, It's pretty good value for anyone that's looking to create an NFT marketplace if you're already going to be purchasing those easy code plugins. Anyway, one tool doesn't provide their pricing on their website and you'll need to reach out to them directly if you're interested in I've put it here as an alternative, but personally I haven't used the template as I mentioned. They do appear though to be using a lot of the easy code plugins. So it appears just to be a bit of a different skin with some hand-holding to get your marketplace launch. So probably not that useful to this audience began, it's an alternative and I just wanted to mention it. Yeah, kind of positioned to people with little to no bubbles skills versus the easy code template. We're a lot he's done for you. You'll still need to get in and set it all up yourself. 10. Building Web3 apps with no-code using Bubble: Now for the part I'm sure some of you have just been dying to see how does this all come together in the bubble editor. I've got my own test up here, but by the way, easy code does have demos and links into the editor with common use cases already mapped out. I would encourage you to check those out as it will give you a good idea of the complexity with working with a lot of this stuff, which I do promise is way more intimidating than it is difficult. It's also worthwhile pointing out that if you haven't already got a MetaMask wallet setup, then head over to the minimized site and sort one out. And there it is there. And this is what your minimise wallet will look like once it's installed. Look, it is a really straightforward process to, to set it up, so I'm not gonna go through it here. There's also so many YouTube videos that will give you a far better introduction than I could. In fact, easy code does link out to a 20-minute also video where someone will walk you through in detail all about MetaMask and how to use it. So if this is new to you, then perhaps that is a good place to start. Before you get too far along. You will need to use Chrome, firefox, or the Brave browser, which is quite popular in the Web three space. Or if you're truly game, it does also work with Edge as well. For any Mac users that prefers Safari, sorry, there isn't a Safari extension at least available at the time of publication. So you've got your MetaMask wallet set up and you've got the plug-in installed. So the first thing you'll notice there is a section for an API key. Now if you're not looking to do anything with smart contracts, then you can simply ignore this. If you are, then you'll need to head over to ether scan. It's ether scan.io. And you can sign up for a free API key. And this plugin will then access that API to retrieve those smart contracts and so forth and pull that information into the bubble app. So moving along, the first thing that you'll need to do to create any Web three app is being able to connect into the wallet, will be able to connect into MetaMask. So moving along, the first thing that we'll need to do is to connect into MetaMask. So you'll need to drag and drop in the plugins element onto the page and you'll want to access that from here. So it will be Web three and MetaMask, and you can just drop that into the page. I've already dropped one in. We can click on that. And there really isn't much to configure it all. So there's two things that you need to know here. We've got the expected network ID and then we've got this Enabled checkbox here. Auto trigger change network requests on MetaMask aligns with this here. And what this means essentially is that you will have an expected blockchain that you'll be looking to work on. So it could be Ethereum, it could be one of the tests networks. It could be something else, finance or whatever. You will want to make sure that whatever you are expecting the user to be using, everything stays in sync. For example, in this particular case, we've got the expected network ID which has four. And this is for the wrinkled B test network. If I change this to one, then this would be the Ethereum main network. And we'll provide a link in the resources. There is a page, I thought I had it open, but I can't find it too many tabs which actually outlines the numbers. So what does one stand for, two, Stanford three stand for, and so forth. But there's a little bit of information there though in the documentation. But you can change the network in the wallet by coming and clicking up here, I've got it set to the wrinkled B test network, which in this case would be four. If I, if I change that to one more, change that to the Ethereum network, sorry, then these two things would be out of sync. So by having this enabled, it is just going to make sure that it's, it triggers the user to change. In this case, it would be triggering me and asking me to change to the wrinkled B test network. So that's all that really means. Now the next thing that we will want to do is we will want to be able to connect the two together. Okay, so clicking over into the workflows and how does this all actually work? We can see that I've got four separate workflow setup here. Now the first one, ignore it, it's irrelevant for you and irrelevant in a normal use case. All I'm doing here just for the purpose of this demo is making sure that when the page loads that there is no user logged in. In practice, you would never want to do this, so ignore that one. But let's just outline the other steps that we've got here. So what we'll probably want to do first is we would want to create a state on the page. And this would be to just manage whether we know someone is signing in because there were a few steps that could be confused with maybe some actions that we would want to do with the Wallet later on. So we just want to be if we can use a state. Yes. We're expecting that this person is going through the sign-in process and then we can switch that state to know once we then go in and we're starting to use our app, then what we'll need to do is we will need to trigger the connection to MetaMask. And basically that is just forcing this to open up. Then there's a couple of parts from there. We can put in a little bit of logic to test whether someone actually has MetaMask installed. So they click the button and we go, Oh, do you have it installed? Yes. Let's open up. Let's open it up. No, you don't have it installed. We need to send you over to the MetaMask. Page so you can install it. Once it's popped up. We would ask them to connect. And then once they've connect, we would then want to send them a little message, were able to send them this little message and then have them sign that with their wallet. And this is really powerful because signing data can prove ownership of the user's account and it can act as a form of authentication, user consent messaging. For example, it could be used to approve that the user has read terms and conditions of using your app a little bit like a Web three version of DocuSign or whatever. We'll send them this little message. They'll agree to our terms and conditions and then they'll connect their wallet. Okay. Now that they've signed, will need to sign them up and then save some information about them into the bubble database. Will sign the user up if they don't already exist. But if they do already exist, then we'll just let them login and then we can change our state to complete, and then we can move on to some other things. Let's click through this all now. This one here, so this is being triggered. So I'm saying Connect wallet. Let's start that workflow. I'm putting in a flag here that says is it installed? So there is a state from this particular element that's on the page. And these are all of the different states that it has. And I'm just checking, is MetaMask installed? Yes, it is. Therefore, this workflow can proceed. I'm first now setting the element which is the page I've just put an a state on the page, this custom State and I've called it Web three signing up. And the value is yes. The way that you would do this, if I come back in here, I can click on anywhere on the page. I can click on this information box and I can add my state in here so I can add it in and I've just put it as yes or no. Okay? The next thing is, I can just come in here into element actions and I can say connect to MetaMask and that's that one there. What that's gonna do is that's going to ask the user to connect. Then the next step would be as a follow-up, would be to then send that request to sign. But we can't have this as all one long workflow they need to finish, which is why we manage that state at the page level. What we're doing here is we're saying let's test to see when the current user is logged out. And MetaMask sign-up Web three, signing up is yes. So this is basically saying if they logged out and this here is set to yes, this customs dataset two years, which we did in this last step, then we're saying we're going to send them this little message that we want them to sign. Again, you can access this in here. We want to say sine, we can click that. And we can put in a little message. And I'm just putting in a little message that says sign away your life to us. And that's it. That's the end of that step. And then the next step. What we're doing here is we're just testing to see if the user is logged out and they still in the sign-up process and then we can then sign them in. Okay, so we're gonna come in here and we're going to first sign the user up if they don't exist. Otherwise, we're going to log them in. And then we're going to set the states to say, Actually thank you very much, they've completed the process. Okay, so in the sign-up process, what we're doing here is we're actually getting the wallet address for bubble though, we do need to have something that resembles an email for every particular user. So what we've done here is just as a little hack, He's with use the append function. So we've gone to bullet, then we've gone append, and then we've put in at email.com. You could put in something random. You can put in your domain if you want, whatever, just as long as there is an at something.com that will pass bubbles validation, then what we can do is we can get the signature, the electronic signature from MetaMask as well. So we can put that in our password. We can say this sign signature. Click on that. Okay, So what this is going to do is this is going to sign up the user. It's gonna set this as the e-mail and it is going to set the signature as the password. And what we're doing down here is we're just gonna do a quick search for users. We're going to make sure it's the same as what's in this box here. We're just gonna make sure that this email combination doesn't already exist. And then we'll assign the user up. If it does, then this will fail. And then we can just go and do the login. And the formatting is basically the same when we're just doing the search here for the users were just going actually, yes, no, it's not empty. This person does actually exist. Then we're setting the states to know, how does this all work. Alright, so now what we've got here on our page that we can see we've got the button to connect to the wallet. And then I've just got a little text box here that when the user is logged out, it says they logged out. When they logged in, it says they logged in and that's it. And sitting behind this button is just those workflows that we've been looking at to connect our wallet. We're just gonna click this. It's going to force open the MetaMask extension. And then it's going to ask us if we wanted to connect with MetaMask. In this case, we don't have a favicon for this test page, but if you had a favicon, it would pop up here. This is my account. And click Next. And I'm going to connect it. Then the next thing it's gonna do is it's gonna pop up. And it's going to ask for signature, which is this message here, sign away your life to us. I'm going to click Sign announced connected. And that's it. That's all you need to do to have somebody now connecting their MetaMask wallet and then signed into your app. Now the thing that we can do is we can go and verify this. If we go back into the editor, we click into data. We looked at the app data, the user table. We can see here that we've got this one user created and their e-mail address is the wallet. At email.com. This person would then be able to sign in and access the same account each time as long as they're using this same address. So now what we can do is we can go over into another page and we can simulate what it might look like if we had somebody who wanted to pay for a transaction with crypto versus a credit card or PayPal or whatever. And this, I promise you is even easier. Okay, so we're on our checkout page now you can see what we've got here is not very much at all. We've got our element again because if we want to access this plugin on this particular page, we've then got a little input box where we can put in an amount. So it needs to be in a number or integer format here, number format. And we'll pass this through to the wallet to make the payment. And then we've got a button which is pay. And then when the person clicks the play button, what we're gonna do is we're gonna trigger dysfunction, which is send token with MetaMask plugin. And that is if I just type that in, you can see that here send token. That's how element on the page we can pull in the amount that sits within that input field. So whatever number is there a will get passed through. And in this wallet to receive, this would be your wallet. So you can wherever wallet you've created to be able to receive that, those funds from your users. Now, the next thing that we want to do is we will want to track once that payment is actually come through, we would actually want some sort of confirmation to come back. So what we're doing here is just looking to see whether that transaction was sent successfully. And then we're just making a change to our order to say yes, this has been paid. So given that we're dealing with the blockchain and it's a decentralized network and we have, this transaction gets recorded in many places. We may want to wait for that to be recorded in a number of places to make sure that transaction is genuine. It's gone through and it's been verified by a bunch of people. It's real and it's not gonna get reversed or anything like that. This here, the way we've set this up, once it's recorded, once we're gonna make a change and we're gonna say that it's paid. What we may want to do is actually put in a condition here and say Only when the transaction conformations is greater than six or something like that to make sure that we're not going to record a successful transaction before it's successful. If you're looking at much larger amounts, then you may not uncommon for some of the exchanges to wait until there's 20 or 30 different points of verification. But look, I think it seems to be standard practice to wait until it's about six. It so yeah, the other thing to mention here as well is that this does all take time, right? So they do say that you could expect 15 to 30 seconds or maybe a couple of minutes for transactions to be verified. But it can, if there's a lot of activity on the network, take longer than that. And while I've never seen it take hours, at least not recently, it's possible that it can take up two hours to confirm a transaction. You just want to take that into consideration when you're considering accepting crypto payments in your app. Because if you've got something where you need to give an immediate result to somebody. Let's say you're selling stock photography or something like that and somebody wants to download that immediately. If you accept a crypto payment, then asking the user to come and check over the next hour to see when the transaction has gone through so they can download the photo. The user experience is probably not gonna be great and people are gonna get a little bit upset about that. Versus if you're shipping out an e-commerce order or you're giving them something that isn't going to either potentially damage your business and you're gonna see fraud, or you're not going to end up in this situation where your users are just sitting around and waiting. So that's just something to consider. There. I'm on my page here. I'm gonna send myself 0.1 Ethereum, and it's going from my wallet to my wallet. So it's not the most exciting transaction costs a little bit of gas in the way, but will at least be able to simulate that payment going through and getting recorded on blockchain and then that result coming back and get recorded in our database. So if I click Pay Now, it's going to open up and we've already, we're already connected, we're already logged in. And I can see that I'm sending from my account back to my account. It's on the ring can be test network and there's nothing here because the result is actually 0 at the end. But typically you would see if I was sending to another account, you would see that outlined there. And you can see here how much gas that I would be paying as well. I'm not sending anything in this case in practice as I mentioned, but yes, there will be this very tiny amount of gas fee and that will need to be paid. And it's telling me that look very likely in less than 15 seconds, there isn't a lot of activity on the ring TB test net work at the moment. And if I'm not keen, I can just reject that and come back to the app. There is the ability to look out for that and then manage the user experience on your page. I haven't obviously built any of that in, but that's very easy to do as well. So I'm going to confirm that. That's it, That's done now. So now what we wanna do is we come back into the editor. We can come into our data and we can click on our orders. And we can just white here to see this order is marked as paid. This should now get updated to yes. There we go. So now we can see that has been recorded and that transaction has all gone through. If we want to take another little bit of a look into this, we can see that the transaction, and I can click on that click on that transaction. I can see the gas price. I can see everything there. If I do want to actually look and see how many times that has been confirmed by now, because this was just a couple of seconds ago, we can click on the Block Explorer. We can see that three block conformations of already happened. That was 46 seconds ago. If I refresh that, it all still need a little bit of time. So I guess this is what I'm just trying to make you aware of that if this was a stripe transaction, we would've had this conformation, everything would've been fine. All right. I think this is the end of this section, and I'll hand back to Matteo. Thank you. 11. Bonus Content: Bubble x Pinata Integration Walkthrough: Hello. In this video, we're gonna go through connecting bubble with IPFS via the Kenyatta service. So this will be uploading files to the decentralized storage and then being able to retrieve them and show them within our bubble app. Alright, so the first thing that you'll need to do to get started is to sign up for a pinata account. Now they do have a free plan. I'll just come over here to the pricing or the free plan gives you one gigabyte of storage. It gives you API access, access to the file manager, all the sorts of key things that you would need if you want to go beyond that. If you want to go beyond the one gigabyte, then you do need to pay $0.15 per gigabyte. So this is expensive storage. If you were to store files on AWS or Google Cloud or a zoo, or you're gonna pay a fraction of this and be mindful in terms of what files you are putting on IPFS and is there a reason for you to put them on IPFS? Is this files that are related to an NFT or something that really needs to be on decentralized storage and live on for forever. Because otherwise, if not, then you may want to consider just uploading those files to a standard Cloud storage, but I'll leave that to you to decide based on your own individual project. And then of course, there is a $20 per month plan. It gives you a few more features. One of the key ones here is Kenyatta submarine, which is a relatively new feature. This will allow you to make files private, so there'll be encrypted and then there'll be private, even though they are on decentralized storage versus anything that you do put on the free plan or anything that you put on the Pro plan that's not submarine and will be available for anybody to view at anytime. So you just do need to be mindful of what data you also want to put in decentralized storage, whether it's suitable or not, client's financial documents and identity information in these sorts of things. I probably wouldn't want to store these things in IPFS for obvious reasons. So be mindful of that. Then once you've logged in, once you're logged in, It's a fairly basic interface to be able to upload and retrieve files and all these sorts of things. We're not going to use this though. We're gonna be uploading files programmatically from bubble and then retrieving them. So we won't use this, but just to give you an idea, this is what it looks like. The one thing that you will need to do though, when you do first login is you will need to get your API keys. You'll need to generate those to come into here. And if you click on API keys, I've already generated some, but let's just generate a new set. So there are two separate keys that you will need to create. One which has say, admin access, or at least one that has fairly broad access to Kenyatta. And then one which is a little bit more controlled because depending on the way that you're sending files and retrieving them and all these sorts of things. Those API keys can be exposed publicly so you don't want to be putting full admin access to your Kenyatta account in public view and somebody can get in and do naughty things to your account. I'll leave that again for you to decide. You might want to read through the documentation to understand exactly what you may want to enable on the public version or the shared headers version versus the admin. So I would probably create one admin version and then you can come through and decide what access you want to give to that more restricted view and be mindful of that there is documentation available if you want to read through that for this demo though, I will see you in the plugin. There's a spot for the normal API keys. And then there's also those shade headers. What my more public versions I've just copied into both because I'm gonna, I'm gonna kill this key and revoke its access as soon as this is recorded. But in your case, you will need to have to set up. Let's come back over into our test app. Now there are two windows that I'm going to show you. One of them is uploading files to IPFS and then retrieving that file from IPFS. And then there's a small Alternate Version to this. And I'll explain a little bit more in a moment. If we look at this particular plugin, come over here, we've got our plugin installed at the time of recording. It's $3 US per month as a subscription or I believe $22 for a lifetime access. As I mentioned here, we've got our API key, we've got the secret API key, and these will be provided when you create them. And then we've got these, as I mentioned, would be ideally different, more reduced access API keys. So you would copy those into there. And then obviously if you have development environments set up, you can put those in. So in terms of what this plugin actually does, there is the pinata SDK, which I'll explain that this is what we're actually going to be looking at largely for this example, you can also do some data calls. There's some events which we will use these and then there were also some actions as well. So if you want to just do things programmatically in the background, you can use these. We won't be using these though. All right, let's come into the Design tab. What we've got here, alright, so our title, this is just a group that we're going to use as a bit of a drop zone for us to be able to drop a file in. So you can use the standard. Bubble file upload. So you could drop that in there and you could use that. If you do that, then all of the files will be uploaded to bubbles storage. So they'll live in AWS and then you'd be able to push them across into IPFS. Whereas if you use the SDK, you can push them directly to IPFS and then just save the path of where they're stored, all saved the identifier of those files so they can be retrieved and then you're not consuming or you're not uploading those files to bubble storage at all. So that's something to keep in mind. So we're going to go through the example which is a little bit more true to the purpose of a decentralized storage. All right, we've got our drop zone there. This is just another title. And then we can retrieve our image from IPFS and show at once it's uploaded. Alright, so let's go into the details here. So we've dragged and dropped this pin yada SDK element into our page. Then what we can do, we've got two options, and this is where I mentioned. I'll show you two different versions. We can either upload into a directory, which means you can have multiple files clustered to get up, or you can just upload the file outside of directory. In this particular case, We're just uploading outside of a directory. And then I'll show you the alternate version where we will upload into a directory. You're able to set a maximum file size. So if this is something that you're allowing your users to do, It's probably a good idea to put some sort of size restriction so people are not uploading gigs and gigs of data if you don't want them to. And you can also limit what files will be going through to IPFS. You can put anything in IPFS within reason, but in this case we're just restricting to images if we can enable drag and drop. And so that means that we can drag files into this drop zone or we can click on it and then we can open up the standard upload Window. And then we've got our target ID. So this is just our group. We've just created a standard group and we've put in the ID attribute of drop zone. Then we come back to our SDK. We've just put this group target ID in here. This is the one that's been able with all of the features and that's all we need to do. This just lives on in the background and we can go from there. I do have a very little text box in here that basically says when the files uploading and when the file is uploaded, it just gives a bit of feedback to the user. It's not really mandatory, but I've just put it there to demonstrate. And then in here we've just got a standard image and it's a dynamic image. So for IPFS, if we're pulling down from the pinata node, then the beginning of the URL will always look like this. And then when we upload the file will get a hash returned from the plugin, which has come through the API. And that'll just link to our particular or the path to our particular file. So we will return that and use that to generate out image. Okay, so how does this all work if we come over into our workflow, the first one, when the follower is dropped into that group, what do we want to happen? So we want to select and upload that file, and then we also want to pin that file as well. So you can upload files to IPFS. But if the process of pinning them will mean that they will stay there permanently, if you don't pin them, they will just get a temporary file that will just get purged at some point. So you do need to upload and pin the file. That's all we need to do the workflow, it is incredibly simple. And then what we want to do in this particular case, and this is not a mandatory step, but what we want to obviously do is we want to save our file to the database. So we've just got another event here. Once the file is uploaded, then we want to make changes to a table which is called course. We've only got one course in there, so I've just doing a search for the course and selecting the first item. But you would probably have something a little bit more elaborate. And then we're just saving the hash. That's the name of the field in the table, and we're saving that hash. So what gets returned is the file type, the file format, JPEG, PNG, the uploaded IPFS hash. This is the thing that we will use to be able to retrieve our image. This one's important. And then a few other things here, filename and so forth. If it's uploading in progress, we're using this to provide that feedback to the users. So if we come over into our demo, we could drag a file into here or we can simply click it. So let's upload this beautiful promo image here. We can see that it's uploading, so that's getting returned from that state. Then we can see that it's been uploaded. And then we're getting our image here returned to prove to you that this is not sitting in bubble servers and this is sitting in IPFS. I'll just open this up in a new tab. We can come up here and we can see here that we have this particular URL format, and then this is our hash here. Okay, so now if we wanted to retrieve the directory, which would be a hash, and then actually just refer to a filename, which is probably a little bit more meaningful to us. We can look at the alternate version. Let's come back into our test app. And I've got another page here. The only difference that I have in this other page is that when we come into our workflow and when I say that the file is uploaded, when I changed the course, I'm putting in the hash and then I'm also returning the filename. So that was the other thing that would return from that element as well. Sorry just to show to you as well, if I come into my database, we can see here that we have saved that hash from that last example. So now when we come into this new example, we'll say that this will change accordingly. And of course, when I'm looking at my the dynamic image URL, we can see that I've got the hash, but then I'm also pulling in the filename as well, which pulls in the full filename, the name, as well as the extension. So that's really the only difference between the two. But this is, you can see if I open up the SDK, the thing that I have here enabled is upload in a directory. I've got that enabled. Everything else is the same, and that's why that format changes slightly. Let's come back over to our demo. And I can click here. I can upload this same beautiful image again, it's in the process of uploading. It's uploaded. Now I'll open this one in a new tab and we'll be able to see that there is a slight difference. So you can see that we now have the filename at the end here. Because we've got the hashes, the directory, and then we've got our filename here. So that is the only difference between the two. And of course, if we come back in and we look at our database and we refresh our data. We can see that we've saved this new file location here. So this should hopefully give you a good understanding of how you can take your files and upload them to IPFS and then retrieve them back and also saving those locations within the bubble database. Of course, anything that does get uploaded, if we come into the management section here, takes a few seconds to show. Alright, and we can see these two particular files so that wherever I uploaded here. Alright, and the last thing that I wanted to mention was the easy Code plugin. There is a few different examples on their demo app as well. I haven't looked at it in detail, but I believe they've got an example very similar to the one that I've just taken you through, but also just to show you how you could use a little bit more sort of traditional ways of getting those files into IPFS by first putting those files into bubbles storage and then pushing them across to IPFS. I'm not sure why you would want to do that, but you could do that. In this example here you're using the standard bubble file uploader. You can upload your image, so on and so forth, but it does go via bubble storage. Alright, that's all for today on this particular plugin, as I've mentioned, if you've gone through how Web three Crash Course, this particular plugin is largely just looking at the pin Jada API. So you could avoid the plugin altogether and you could just integrate directly with the API. But I thought most people, given the cost of this plugin is fairly low, would probably just use the plugin or at least start with the plug-in. But there is all of the information here of different things that you can do, for example, and this is one thing that we didn't go through if you're uploading an NFT or if you're uploading some other files and you want to attach some metadata, you can also use the easy Code plugin for that. And this kind of the documents here will take you through in terms of exactly how that can work as well. Alright, thank you so much.