 Hi, my name is Jayanthi Kanani and I'm a founder and CEO at MATIC. Basically we are building a lead to scalability solutions for Ethereum and we use plasma-flavored to secure our valuable assets and we use proof-of-stake for our consensus mechanism to validate and keep the chain running. So basically today I'm here to talk about mostly how we at MATIC thought differently than other lead to solutions and created a way to create mass adoption for dApps and users. We are going to share this story with how we did our tech and the usability part of it with MATIC. So basically in general in the blockchain ecosystem what we all want, right? These are ultimate questions right now. Do we need scalability? Do we need more apps? No. Basically what do we need is users, more and more users and in any industry if you take a notice of outside decentralized systems, decentralized market you will see growth is very important for any industry, right? And what we are targeting is just users, right? Someone said like when you think about the problem you think about, you think a backward and work forward. So here also when we think about the problems we think about users and how we get more users and work backward like how we get more dApp developers to build on the blockchains and how they can actually get more and more users. So it works both ways, you need users and for that you need more and more dApps and for that you need scalability. So that's how we work like backward, think backward and work forward. So we just start with the scalability in how it actually affects the more dApps in general. So for that what we are doing is that we scale, we provide scalability as a layer two using plasma and predicates. We also use side chains, right? Side chains is a simple because there are multiple layer two solutions like search channels, other solutions. But the problem with the other solutions are they're like there is a trade-off between the amount you need to settle your transactions and make your transactions on the layer two. What we use is the simple side chains using plasmas and prop stake. And we hide all other complexities underneath and just provide dApp developers what they need. So here, so just for dApp developers, if you see what dApp developers need, we just provide easy onboarding for all the dApp developers. We provide their valuable assets using plasma and for them we need also provide easy migration. So once Joey Krug said, if someone comes to me and asks for, let's say, if I can scale your dApps in the next six months, we're not going to do it because it takes a huge amount of efforts and time and money to migrate from one solution to other solutions just to scale your dApps. Instead, people want to focus on their dApps instead of focusing on the scalability, right? So what we do is that we just provide simple and easy migrations and testing for dApp developers. Most of the times, dApp developers need different kind of fee models, fee models, right? In Ethereum, if you want to make a transaction, you need Ethereum or maybe you need to integrate meta-transjections. But here, we actually provide those kind of solutions in build on MATIC. So dApp developers just can use directly on the platform and just run their dApps easily. There is another problem in the whole ecosystem is the UX problem, right? So if we think about, if you are scaling in Ethereum and simple providing a platform for developers, you also need to make sure you provide the best UX in the industry so people can just move to the next platform, right? If you see the previous markets and before the decentralization movement, Web 1 and Web 2, each iteration makes your applications very user-friendly, right? Currently, if you are using Uber before, you are using Taxis, right? See the difference between the user experience throughout the Web 1 and Web 2 came, right? So when we talk about Web 3, we should think about how we are going to provide better user experience for our users, better experience for our developers. And for that, we also have multiple development tools as well, which people can directly integrate and provide the kind of seamless experience for the users. So now, if you think about what we as a Matic provide to web developers is that we use Plasma. So basically, in our Plasma model, we use more VP. There are multiple flavors of Plasma currently, but we use more VP. Plus, we actually use EVM with Plasma, right? So some of you know that it is not viable to create a Plasma, which is for general computations. But for now, we have solutions where you can use ERC-20 and ERC-721 directly on EVM. So basically, what we did is we changed ERC-20 standard a little bit and added extra receipts to make sure input-output-1, input-output-1, input-2, output-2, some kind of simple accounting on the receipts. And it actually helps us to create a fraud proofs when you exit from the Plasma framework. So those kind of little tricks and tweaks we made on our Plasma model to create a seamless EVM-compatible Plasma ERC-20 and 721 computations. And if you think about simple ERC-20 and ERC-721, it's just a simple computation, plus or minus. Let's say if I am sending a standard die to someone else, it just subtracts the amount from my account and adds to the other person's account. But if you think about a little bit complex state, you may want to write your predicates. So predicates basically just say, hey, let's say if you are using multi-sig wallet, when you move your state from the sidechain to Ethereum chain, you need to make sure only owners of the multi-sig wallet only can withdraw your tokens or exit your tokens from sidechain to Ethereum chain. So those kind of state computation you can write using predicates systems right now on MEDIC. But for ERC-20 and most of the standards, we actually provide directly in-built support for predicates. There is also some kind of problems in Plasma where you exit your tokens from the sidechain to Ethereum chain. It takes seven days or maybe no more, because you need to make sure you don't create a fraud on the sidechain and it exits instantly. So Plasma framework provides you a way to create, you know, have like a priority queue when you exit. So it takes kind of seven days for exit. But what we do is that we actually sell your exit directly to the buyer and you get the exit instantly, but you pay some fees for it and, you know, it's kind of security with kind of, you know, with a probability using, just other person can just prove, okay, hey, your exit is valid, you can exit, but you have to pay, let's say, a point zero nine die for one die if you don't want to wait for like seven days. So those kind of marketplace we are building for faster exits on our system. As we said, as we said, like we also provide multiple SDKs and development tools to just to onboard more and more DAP developers directly on the directly on our systems. The main thing is that we are not DAP specific sidechains. So we have like one public sidechains, which actually provides you a composability and the network effect if you if you are building on layer two. So basically, let's say if you have a DAP specific sidechain and you want to interact with multiple, multiple DAP and multiple contracts, like the DeFi systems, you need to make a transaction on a different shot or different different chain to make this work. But here we provide like composability out of the box and these systems actually works pretty well because it derives the security from the Ethereum if something goes wrong, right? So for security, Ethereum is there and we just provide a partial confirmation directly. And after after after five minutes or so, you get the simple finality after after plasma checkpoints goes in the Ethereum chain. So those kind of tweaks and ticks help us make the whole system smooth and for for, of course, our our users and developers. So in this whole whole system, what about end users, right? How end users actually interact with multiple chains? So as a layer two, we have a problem with interacting with multiple chains in one one one screen, right? So if you use kind of, you know, use metamask, you need to change your networks or your user has to change your networks very frequently. So let's say if I want to move my tokens from the Ethereum to layer two, I need to deposit. I make a deposit. I need to make a deposit transaction on the Ethereum. And then after that, I can make transaction on the layer two, right? But here, let's say if you are using metamask or something like that, you need to make sure you have to change your networks once you make a deposit. But for that, what we are doing is we are we are actually integrating wallet connect protocol, which help us to which help us our users to interact with multiple chains directly. So people users don't have to worry about multiple chains, multiple deposits or exit anything, right? Also, when we talk about simple public side chain or public one public chain, people can actually use and test multiple multiple contracts when they want. If you use a simple, simple, you know, that specific chains, you have to your user has to move one chain to second or the chain to test your test your applications. But here, your user can anytime trade or interact with multiple contracts. It also helps for stable coins on the chain to support users can and apps can use use stable coins in payments in these exchanges and, you know, multiple at multiple ways. So those those kinds of mechanism we are we are providing for our end users. So also, we are working on multiple widgets who developers can directly integrate for the users. So so again, they don't have to make a deposit and exit transactions on the on the layer to so mostly of a system like if such kind of system can make users and developers life easy. And for that, developers can actually build new markets and kind of let's say defy games and you kind of defy, which actually works multiple works with multiple contracts games. Who who can integrate, let's say Uniswap or multiple dexies or a simple other games as well other games contract as well. And so, yeah, those those kind of market and existing market we can actually target on when we have such kind of system. So so, yeah, yeah, and that's it. Thank you.