 Welcome. Thanks for coming. I'm really excited to be here because I left Red Hat six months ago, so I didn't expect me to see that many Red Haters that soon, but it's always a great experience. My name is Vasek Pavlín. I now work for a company called Blockchick, and I'm leaving that company. Never mind. So I want to talk about Vet Free, Blockchain, and these things, and I want to talk about how it's open and potentially open source, and how I think, I believe, I hope it actually inherits some of the open source mantras and approaches and promises. So I got the single only one response to me speaking about this on this conference was this. So I wanted to front on that by saying, please don't be mad at me, don't be angry, don't shout, don't scream, don't hit me. I understand that many people are concerned about environment. I'm too. I don't want our planet to end up like this by burning so much electricity through mining and all these things. But I don't want to talk about that because that's a philosophical question that I don't understand. I'm not an environmental expert, and I'm not developing proof of work blockchains or anything like that. I develop applications on top of blockchain, and I try to use less resource demanding blockchains as much as possible. So I wanted to show you something nice. So whenever you get mad at me, please think about this little kitten. Imagine how you rub its fur and how it calms you down and don't be mad, please. So what is that free? As this gentleman here can show you, nobody knows. It's a buzzword, really. But we are used to buzzwords at Red Hat. Containers where buzzword and web scale and all these things. There is some technology that changes the world sometimes. I think this may be one of those. It may be changing not all lives, but some lives, like containers that change lives of software architects probably, and how they design applications. So Web3 can change lives of some other people, which I don't know who those would be yet. But generally, Web3 is like an extension of what is called Web2, which is like Facebooks and Googles and YouTubes, and we want to make Web3 a better place where to be, where nobody tells you what you can do and you cannot do, and where nobody is stealing your data and whatever. I can't explain that very well, at least not without pictures. So I stole this picture from Anderson Horowitz presentation about the state of Web3 and basically explains that Web1, that's like, I don't know, 1990s, I guess, 80s, is read-only basically. You could create a website and put content there, but you would have to know how to do it. You would have to have your own server, maintain that, manage that. You couldn't just come to a website and start posting blog posts and videos and things like that. So it's kind of read-only for the general public. Then we have Web2, that's where we live now, and you can post a video on YouTube, post on Facebook. You can write and read. You can be content producer and content consumer. In Web3, the expectation or the goal is to be a content consumer, content producer, and then owner. So if you post something to Facebook, then Facebook owns that content. If you post something to YouTube, then YouTube owns that content and they can say, no, we don't like it. You can't post it here. Take it away. Well, not take it away. They will take it away or take down your channel or something. In Web3, the idea is that you own the content or you can own the platform that the content is displayed on, or you can own the protocol that runs that platform. That way, they want to basically give you the ability to own a piece of internet if I use their words. So what does it mean to me from more like a lower level perspective? I think Web3 can be built out of these three terms or technologies, and it can also be built without basically any of them, which sounds potentially weird. But I think hopefully, this is like the technology that we are trying to use now or approaches that make sense and the best Web3 version can be made out of these. So blockchain as an open permissionless interoperable database, where you can store information and you can store the transactions, whatever it is, like an economical transaction, financial transaction. But it can be also that I don't know, you followed someone or you liked someone post. Then there are tokens which is the financial part of the thing. So when it says own, there is often financial incentive in there because all those big companies, they make money of you posting that content and Web3 promises that you make money out of posting that content. So the tokens are there to keep the money flow and keep the financial system going through that whole ecosystem. Then there are Debs, which is basically the web applications or the applications developed on top of these, utilizing blockchain, utilizing some incentive for people to use the platform, hopefully being distributed as in nobody can shut them down, nobody can block you from accessing them. But this ideal world, that's not how it works usually, but that's the goal where we want to be ideal. I think that this is how open source works as well. You want something that is interoperable, you want your source code with a public API, a well-documented API that anyone can take and interact with your open source project. You want that to be transparent, everyone should understand what's going on there, why you are making decisions. So that's why you have your code on GitHub or GitLab and you basically want the community to come and look at how things are decided so that they can contribute and they connect with the rest of the community. You want it to be permissionless, you don't want to block people from contributing to your project. That's the same for Bit3. The goal is to be interoperable. That's like, obviously, we are talking about public blockchains, not private blockchains and private blockchain is a expensive database and that's it. There's nothing else there. Public blockchains. So if I put in a smart contract that represents some asset in a game, potentially someone can come and say, if you own an asset in this game, you can also get, I don't know, a t-shirt for free because I'm printing t-shirts and I want to do some marketing. That's, I think, part of the interoperability. The transparency, if I interact with Jakub here and I send him the money that he paid for my coffee, everyone can see that because it's transparent. That's the same for if someone does something bad. So I explained a couple of examples of where Bit blockchain actually makes sense during the day. So I'm going to say it here as well. One example is that Polygon, which is one of the big blockchain networks, they worked with an Indian government where there was an issue that if someone reported a crime, let's say some woman was raped or something, and they reported the crime and it's the issue with police was not that the crime didn't get solved but that the crime disappeared, like the report disappeared and never happened. So they went, government went to the Polygon project and said, implement something that solved this and they did a blockchain project where now if you report a crime, it goes on top of the blockchain and it's there forever. If someone removes it, which potentially is still possible, at least there is a record that someone put it in and someone removed it and then you have kind of the foe in the story who is doing that. So that's the transparency and then permissionless. As I said, if you have an open source community, you don't want all these code of conducts and be welcoming and then try to get diverse people, and part of that is permissionless. If you have group of people that you say, no, you can't contribute to my project because I don't like you, that doesn't work and that's what we want from that free and blockchain perspective. We want anyone to be able to interact with the applications without some authority saying, no, you can't. So as I want to focus on the open source part here, I picked some projects that are open source and that are heavily used as part of that free ecosystem. So I split it into front-end, back-end and the actual blockchain part. Just for you to have some reference of like, if I have no clue how to join this free movement and be successful in something new and exciting and hyped up because containers are boring now, and you can take one of these projects and look at that, contribute to the community. So from front-end perspective, very well-known framework for developing front-end is React, and it's heavily used to develop blockchain-based applications where you interact with blockchain directly from the front-end. So there is not much to talk about there. Then there's Eters.js, which is the library that reps the calls to blockchain to smart contracts and allows you to call it from the front-end easily and simply and manage wallets and things like that. So it's very useful to understand. Then there's TypeChain, which is based on TypeScript. So if you're not using pure JavaScript, but you're using TypeScript, which allows you to do typed JavaScript. The TypeChain allows you to generate typings for smart contract and then call that as a method on an object. So it makes it very easy to interact with smart contracts by just basically instantiating an object and call that. All of these obviously are open source otherwise I wouldn't be talking about them. From the back-end perspective, because often people think like, okay, so I have this blockchain thing and that's it, right? No, so you still need front-end for some user experience and you often need back-end for aggregation of the data because blockchain will not help you with that. So there is very interesting project, the graph, and even if you're not interested in blockchain, I think this is a really cool project. They do the aggregation. So every smart contract can emit events. An event can be like information about what happened. So transaction from to how much. You can build a mapping into the graph, which automatically ingests the events and then builds your GraphQL API on top of that. Then you can easily query that instead of calling the blockchain directly. So you can potentially take any blockchain-based project and build graph for it on your own, and then do an aggregation layer on top of that and make something useful for the project. IPFS, Interplanetary File System, I've heard about it at Red Hat before I left Red Hat, and before I actually did something with blockchain, because it's an interesting project which tries to solve permanent storage distributed permanent storage. So basically, you upload something to some IPFS nodes. Those objects have unique identifier like in S3, in Airbus S3 basically, unique hash, and then as you access it, it gets copied over in the network, and the network, anyone can join it. It's again permissionless, and you can basically get access. The more it's used, the more copies the quicker access to the data, and it's essentially, Pipe Piper, and essentially, it is basically, hopefully, it is permanent there, and never going to get deleted. And then Go Ethereum, that's basically the most popular client for Ethereum, and I think it's cool because it's going, and I really like Go Link, and I know a lot of people at Red Hat do too, that's why I put it in there. It's a very nice way to interact with blockchain on backend, if you need to build something on top of your smart contracts. And then for the blockchain development again, for the smart contracts, HardHat is a nice tool to rep your development with tests and deployment scripts and automation and things like that. It's a suite of utilities and extensions to make it easier. Not that many people use it, so that's why there is so many hacks because people don't test their smart contracts, and it sucks. I hate it that they don't. And then I have Solidity, which is a programming language for Ethereum-compatible chains, how you program the smart contracts, also open source. And then MetaMask, it's an extension for managing your wallets, so you can create the wallet or import your private key there, and then you can see how much tokens and NFTs you have in there and stuff like that, and it's also open source. Some interesting repositories or projects to look at if you are interested in the smart contracts or even the front-end development where I take my inspiration from when I'm implementing something. Uniswap, it's a decentralized exchange, and they are one of the biggest innovators in the space. Aave, that's lending protocol, and OpenZipLin, that's basically, they do security stuff, but they also provide a lot of implementation of standards. So if there is an Ethereum standard for tokens and NFTs, all these things, they will have a library for that that you can use and you don't have to implement the standard on your own. And the reason I have these here, it's often hard to start from scratch. So if you are familiar with front-end, maybe you can go and look at one of these projects and check their front-end implementation and get some understanding. If you are into back-end or into an actual smart contract development, the Aave smart contracts are crazy and I don't understand them because I like the financial understanding of how they work and what they do there. It's very complex. And basically, my last slide here is that VET3 is trying to push a new model. I have talked about it with a couple of people here already. So if you heard the story or heard the idea, I'm sorry, I'm gonna bore you potentially. But there is something that is described by the guy from Zora, it's one of the links there, and he calls it hyper structures. Up until now, anything we've built as a software, we have to maintain and we have to improve upon, right? We have to maintain it. We have to make sure it's running. We have to make sure there is infrastructure for it. We have to pay bills to AWS or some other provider. But the idea of hyper structure is that you build something that you deploy on blockchain and as long as the blockchain is available, which hopefully is forever, as long as people are incentivized to run the nodes, it's there and it's working and it's running on its own without any fees, without any company behind it. And I think it makes a lot of sense because I take blockchain as infrastructure. So if you're building something out of OpenShift, then OpenShift is your blockchain. Bad, but like on that level for me, I don't develop blockchains, I don't develop Ethereum, I develop applications on top of it. But the good thing about blockchain for me is that it's always there, it's always running. I don't have to do anything, I don't have to set up anything, I just can deploy my smart contracts and they will be running as long as I have users using them. And the idea of hyper structures is then that you develop something that you deploy and it's there and it's running and nobody has to take care of it. Nobody has to maintain it, nobody has to do monitoring of it. Obviously, bugs, issues appear, so we have to think about upgradability or migrations and things like that. But like, you don't have to have an SRE sitting in front of computer and watching blocks of some container on your OpenShift if it's hyper structure based on blockchain because the smart contracts will just be there and working. So that's how they approach Zora D3 and it's an open source NFT marketplace. Definitely, the smart contracts are pretty simple but the kind of hyper structure idea is there. And then Lens protocol is quite new, probably like two weeks old. It's by the, oops, it's by Ave. And it's a social graph. So if you imagine Twitter, Facebook, all these things where you can follow people and comment, they are building an open social protocol where you can come, you can create profile and you can follow people and all of that is recorded on chain. So they can't shut it down because the contracts will be there and they can't remove them and they can block you. It would have to be some kind of another layer on top of that that would basically give you the access to the contracts that does not show your profile. So if a company is built on top of that and you can't, and they want to block you, you can't, you can't, you potentially can't access that but then the protocol itself is still there and it's completely permissionless and their contracts are really interesting and I still need to read a bunch of them. So that's it. I hope that I delivered the message that there is a lot of openness and open source happening around blockchain and Bet Free and that it's not just us burning planet and us trying to steal your money and your wallet, private keys and things like that. So always first think about the kitten when you start thinking about blockchain and well if you can, if you can't then there's not much I can do. That's it. I don't have anything else to say so I can either leave or you can ask questions. Thank you very much for listening to this. Yes, they know my wallet address, they can check and your wallet address, they can check that there was no transaction where I paid for your coffee. So yes, you can find people that check this and then beat me up, yes. But I'll pay for your coffee. Any more questions? Okay, now I'll take even the angry questions. I'm not sure if I understand the structures. Uh-huh. There is always, there needs to be the cost. Yes. So in this case, the cost is the... The externality of increasing the blockchain itself. So like everyone using it from that moment, it starts existing, will we pay in some very fractional cost of it existing? No. Yeah, so the question is where is the cost in the hypostructures because there always is cost and whether the cost is kind of spread across the people that are using the blockchain, right? No, not really. You pay, in blockchain you pay for transactions, you pay gas fee. So every transaction has a cost to it. And the users that send the transaction pay that cost regardless of what kind of transaction that is. If it's a hyper-structure, then if nobody is using that, there is no cost for it being there. If people use that, they have to pay the gas fee. But the gas fee is not for the project, it's not for the hyper-structure. The gas fee is for interacting with blockchain and it's the reward to miners or validators who run the blockchain, if that makes sense. So you don't pay anything to people that build this and run this, you pay for the interactive infrastructure. Imagine you are calling an AWS API for something and you are not paying for actually running a virtual machine there but for calling that API and getting a result. So that's basically the same with blockchain. You are submitting something, you're storing some information there, you are changing the state and that's what you are paying for, regardless of what that is. So you don't pay for it to be there. You pay when you interact with it but you don't pay to that hyper-structure, you pay to the blockchain validators for running the blockchain. That's, yes, like in theory, yes. I guess it depends on the blockchain implementation. If we talk about Ethereum for example, then yes, as the state grows, so the more smart contracts there is deployed, more users using it, the state grows and the transactions get more expensive as the validators is to pay more and they need to be more incentivized to run the validations. So potentially yes, but it's not, I don't think it's like a straight line there, like with current model where you pay for a service. You pay for something. So yes, if every person on the planet decides to deploy some smart contracts on the blockchain, the state grows and the cost will be higher, depending on the blockchain because there are blockchains which basically shard things and like take the unused part, they just like throw it away and if someone wants it, they pull it from like a backend database if I may say that and that kind of like work around this issue a bit but that depends on like, there are different implementations so it really depends on the implementation. But the kind of the premise of this is that you are not specifically paying for that one thing. It just generally like grows and as it grows, yes, there is potentially higher cost but that also depends on other factors like the configuration of the blockchain, block time and like throughput and things like that. So it can be tweaked if like the state grows too much and there are tweaks that you can do to like lower the cost and that way basically eliminating this like everyone pays for your smart contracts being deployed although not used. Things like that or solve crimes. Yeah, I think we're out of time anyway. So thank you again.