 Hi Rodrigo, bom dia, esperta tudo bem. It's great to see some of you. Welcome from Brazil and North Carolina. All right. Welcome everyone. Excellent. Thank you so much. Welcome everyone. We'll go ahead and get started. Good morning, good afternoon and good evening to those of you who are joining from around the world. My name is Daniela Barbosa, and I am the executive director of hyper ledger and the general manager at the Linux Foundation for blockchain health care and identity. I'm very pleased to be the host today of today's hyper ledger in depth webinar with our member consensus. This is part of a three part series educational series for the hyper ledger and the Ethereum community around paving the way for enterprises to take the best parts of the public main net. Today's speakers, we have ease G, who's the co founder of the head engineering of infer and did a live flock, who's the CTO of codify. So I'm very excited, excited and we'll let them introduce themselves in a little bit so welcome. If you are joining us for the first time in one of these webinars, all are welcomed in the hyper ledger community, we do, we are committed to creating a safe and welcoming community for all. So please review our hyper ledger code of conduct, and the basics is be nice to one another be respectful, and let's be helpful and collaborative. We have a couple housekeeping rules as standard with our hyper ledger meetings webinars meetups etc. We do operate under an antitrust policy. So we do have participation by industry competitors. And it is the intention of the Linux Foundation to conduct all these activities in accordance with the antitrust loss. If you have any questions, please visit our website to review. And if during the session you have any questions please message myself or one of the other hosts and we can assist you. Please note that the session is being recorded. So the session will be available afterwards and our webinar library as well as on YouTube. And these slides will be available for download as well with the videos so we look forward for you to view those. If you have any questions just let us know. This is an interactive session so we're going to have EG and DDA are going to do a presentation and talk to you a little bit about the work that they've been doing. But please stay active and get the most of it. Raise your hand if you have a question. We'll get to it during the Q&A part and we'll allow you to do a voice question if you so wish so just go ahead and raise your hand to do that. You can also use the question area and answer section in the zoom webinar just clicking on the button asking your question there and we'll get to those. Or go ahead and ask comments questions etc in the chat. So once again for those of you who just joined us, feel free to say hello and where you're dialing in or zooming in from today. And once again welcome everybody to the webinar. Just as a reminder, you know, Hyperledger is a collaborative and global open source software community we're hosted by the Linux Foundation, and we're really focused on advancing blockchain technologies for businesses, focused on our developer community so once again all are welcomed and we look forward to our discussion. Hyperledger is made up of multiple projects and here you see our 17 projects. Today's focus is going to be in on our Ethereum community, which we do have Hyperledger Bezu which is our Java based Ethereum client and EG and DDA are going to talk about some of the other consensus products that are available for enterprises as well. Just a quick history of Ethereum and Hyperledger. The series title of this, the series is called Who Put Peanut Butter in My Jelly. A lot of people are not aware of the partnership and the collaboration of the Hyperledger community and Ethereum since 2016. Consensus was one of the founding members of Hyperledger in December of 2016. And in 2018, when we started working very closely with the Ethereum Enterprise Alliance, as well as the Ethereum Foundation, where they are associate members of Hyperledger as we are of their organizations, and many participation opportunities since 2018 and beyond. In 2019, in August of 2019, we also had a project that was contributed an open source project at the time was called Pantheon and Pegasus and it was contributed to Hyperledger and renamed Hyperledger Bezu. So Hyperledger Bezu once again has been part of the Hyperledger community since August of 2019. And in 2020 Hyperledger Bezu became active status project. And once again, if you go on our website, you can find a lot of this history of Hyperledger and Ethereum. Just as a reminder, you know, as an enterprise Ethereum ecosystem and collaboration. We know that, you know, the Forbes blockchain 50 for example had 21 companies that were using Ethereum and enterprise applications. So adoption continues to rise. Hyperledger Bezu is one of the four main net compatible Ethereum clients that are supporting future hard works. And the Hyperledger Bezu community is very active. If you're interested, please do participate at the end. I'll tell you a little bit about how to go to do that. Hyperledger member companies continue supporting Bezu and other Ethereum technologies and code bases and they continue to grow. And just a quick sampling of some of the Hyperledger Bezu case studies that you can learn more about finality which is the utility settlement coin, lack chain, which is a Latin America consortium built on Bezu for various use cases. There's also post Italian in Italy, which is allowing customers to combine different programs using Hyperledger Bezu and we do have a full Hyperledger member case study about post Italian available on our website, as well as a recently posted one around RTI, which is a supply chain based built by Ledger Leopard, also using Hyperledger Bezu. So, and last but not least, Palm NFT studio a couple weeks ago, Daniel Heyman did a presentation around the palm chain and how they utilize Hyperledger Bezu and Palm NFT studio is behind the Damian Hearst the currency which is a very interesting project, as well as DC Comics and many more. So, lots of activities happening in the Hyperledger community. But for today, we want to focus on easy and DDS presentation. So I will go over and DDA and easy. You want to introduce yourselves and get started. And I'll stop my screen and go ahead. Sure. So DDA Floor, I joined Constancy three years ago. My background was in banking. The first and half year and a half I was focused on enterprise use cases in particular consortium projects and then over the past year and a half been leading technology and engineering of the FinTech product group of Constancy called Codify. Welcome. Yeah, thanks, Daniel. My, my name is Eiji Gulano. I'm one of the co-founders of the Infura project that's been part of consensus since 2016. I've been working solely on that project since I joined the Ethereum space at the same time. My background is in scalable web systems, distributed systems, cloud engineering. I spent most of my early career at a startup called Gaikai that's now part of the Sony PlayStation group. I wanted to focus on similar things, back end and reliability. And so when I entered the Ethereum space, working on the project that could quickly scale developer access to Ethereum was kind of what I was passionate about. And that's what I'm still working on today. Wonderful. Oh, welcome. Didier, over to you. Let me share the presentation. So today we're talking about enterprise adoption of Ethereum mainnet. And actually I want to broaden straight away and mention not just Ethereum mainnet but potentially other public Ethereum infrastructure that exists today. So as we know and is now notorious Ethereum as broad adoption, both in enterprise and in crypto. There are the largest community of developers and the largest user base, essentially in blockchain ecosystems. There's been a few years ago, most projects were running on most enterprise projects were running on private infrastructure or permission infrastructure. So networks deployed by enterprises, but more and more we see enterprises including large financial institutions using public infrastructure to run some of their use cases. Most famously, over the past two years, the likes of Santander, Subgen and others have issued bonds or other digital assets on Ethereum mainnet, for example. One major trend that has accelerated the adoption of public infrastructure is also the fact that beyond Ethereum mainnet. There are now many other venues that are public networks that can be used to issue assets. So some of them are public side chains like Polygon and Xdai. And others are layer two technologies that derive their security from from layer one, and are usually roll up roll ups, like optimism and arbitration. We'll talk about it a little bit in this presentation. So what are the key advantages for an enterprise to use public infrastructure? Let's say historically, we've noticed that the cost of ownership and the go through the speed to market are much reduced in the case of public infrastructure because you don't need to worry about deploying specific networks. You can use existing infrastructure that is immediately and readily available. Another huge aspect is immutability on JVT. So, you know, there's been many cases of enterprise starting with small networks of four nodes, and then wanting to scale. And sometimes they find themselves in a situation where they have to migrate from one particular private network to another, in order to achieve that no such problem if you use public infrastructure. And boom, obviously, a big advantage is the connection with ecosystem applications on public infrastructure, so in particular decentralized finance. It might seem far fetched as of today, but as we saw with Sogzhen collaborating with a DeFi protocol called MakerDAO, things are changing and we might see more and more collaboration between DeFi protocols and enterprise institutions. Some of the concerns that originally existed around energy efficiency, scalability, and privacy are gradually being solved, in particular with those layer two venues and public infrastructure that are emerging this year, mostly. And we'll talk about it a little bit as well. So, coming back to the advantages we mentioned above. So if you think of your typical private blockchain journey or DLT journey, it has quite a lot of steps. And in large part because they are roughly, you know, if you simplify two situations, either you're on your own, and you decide to launch a dedicated network for a particular use case. And you still have to deploy the infrastructure, but there are ways to do it relatively simply and the question, the challenge there is that it's your network. How do you ensure that you broaden the ecosystem and you manage to invite other people to that network if you want to scale. That creates some potentially some challenges. And the other scenario is a scenario where multiple enterprises come together, form a consortium. I want to launch a dedicated network for a particular use case. And experience shows that there are challenges around governance, around legal challenges, onboarding, and a lot of small frictions to adoption of those private networks. There's also the fact that the cost of the infrastructure is also has to be essentially borne by the members of the consortium or the owner of the network. In the case of public infrastructure, it's much more simple from the perspective that the ecosystem and the network is open. So there's much less frictions around onboarding, adoption, governance, because things operate in a public ecosystem. You still have obviously some of the challenges in particular around security and sharing that your smart contracts are properly audited. And you do have, and that's the main tradeoff is you replace a cost of infrastructure by a different cost of usage of the network via gas that needs to be paid in the native cryptocurrency of the network. But as we will see in this presentation, even this problem is gradually getting somewhat solved. It's a similar message here with a lot more steps in the case of, if you really want to scale a private network, there are many more scales, more responsibilities for in particular the parties hosting the network. They are obviously and we provide blockchain as a service, for example, for private network via current blockchain service, which simplifies greatly. Some of those challenges, but still you still have a cost of infrastructure, you still have the questions around adoption governance and onboarding. In the case of public infrastructure really the key, the key additional questions are coming back to gas, having to pay gas and if some of the volatility in the price obviously we're going to talk about it and compliance, but any of those challenges are gradually being addressed. So what are the key use cases that we've seen on on public blockchain. Many, like I mentioned large financial institutions have run issuance of bonds or notes or other securities on on mainnet. And, you know, they give, they obviously have, there's a lot of benefit from it because once the asset is deployed on, on, on mainnet there are other things you can do with it. And that's the particular what happened between Societe Generale recently and MakerDAO, with the essentially the funding of a bond that had been issued by Societe Generale some time ago on Ethereum mainnet. It increases the connection of the use case and assets that are created with the rest of the ecosystem. There are other pieces of infrastructure that you, that you need beyond the chain so potentially oracers, potentially in some cases, cross-chain, some form of cross-chain interoperability, particularly in use cases that involved both digital assets like a security and a stable core in our IDC that might be deployed on a different network. Like I said, composability is a very important benefit. I mean today there are very few, very few people who are experimenting with decentralized finance in enterprise or in financial institutions, but it's changing in particular with some announcements around, you know, in particular Ave or Maker again like I mentioned. And I think more and more we'll see more use cases and more collaboration between protocols in the ecosystem and enterprises. Some of the concern that existed before, I mean one of them certainly one of the most famous actually is energy efficiency. However, this is being solved in multiple ways. So first of all, Ethereum mainnet used to run on is still running on proof of work consensus algorithm which is fairly that consumes quite a lot of energy because it's predicated on solving cryptographic problems, which is and which is obviously necessitates a lot of electricity. Having said that next year, next year, Ethereum will transit from proof of work to proof of state this transition has actually already started. A year ago, proof of state chain was launched. And next year, those the existing Ethereum mainnet will merge with this proof of state chain and will create a much more energy efficient than your own mechanism for Ethereum to continue to run on mainnet. Beyond that, as I mentioned, they are side chains, roll ups, so layer two solutions that derive their security from from mainnet that are emerging and those technologies are very energy efficient and very scalable. This represents what's going to happen. What has already started and is going to continue to happen next year. Like I mentioned, the beacon chain was launched a year ago. It's a proof of state chain that is very energy efficient. We're still on proof of work in Ethereum one, the world's Q2 next year, the merge will happen, which will transit. Ethereum one essentially to a proof of state consensus. And then from there, more, more scalability solution will be layered on to further increase the scalability of Ethereum in an energy efficient way. So, adoption of the beacon chain has been significant. There's a lot of ether a state into the network to guarantee security. So this is all going very well. And the, the merges plan for Q2 so far. Beyond that, like I mentioned, a theorem to we provide additional scalability, but then there's already many solutions layer twos and side chains that have been deployed. Some of which are deriving their security from mainnet roll ups that have that have a large factor of improvements of scalability. And they are essentially two types, if you simplify, mostly. So they are optimistic roll ups that are based on fraud proofs. So essentially you have an opera. So the general principle of roll ups is that the execution layer is externalized execution of transaction and computation to an operator of the roll up. And this execution takes place off layer one. And then the transaction data and state transitions are reported back to main to layer one after execution. And there are two mechanisms, either it's based on fraud proof. So if nobody contest the validity of this transaction, then they get they are fully finalized. And the alternative is proof of validity proof using zero knowledge technology, where you can really verify via zero knowledge proof on mainnet, the validity of transactions. This is more on the same topic. So, and one interesting thing here is that you might have heard also of some initiatives that around enterprises making use of zero knowledge technology to you for enterprise to use mainnet so in particular the baseline initiatives that involved EY and Microsoft. And there are more initiatives in that regard. So how do you build on mainnet what are the differences what tooling do you need. We have a stack that enable a lot that enable makes it easy to build on mainnet, it also makes it easy to build on private network but we focus on mainnet for for today or public infrastructure. And codify so the feedback for a group of content sees provide a set of middlewares and modules that enable various use cases from business process automation with workflow to issuance of digital assets and managing their lifecycle using codify sets and issuing stable coins or CBDCs or E-money using codify payments. I also mentioned codify compliance, because it's a way to scan a theorem addresses to identify any financial crime compliance risk. And also codify orchestrate that is the middleware that abstract the complexity of blockchain transaction. So now I'll leave it to EG we can explain the role of in-fiora in that process and how in-fiora also provides solutions to solve other problems that we have mentioned earlier in this presentation. Thanks, Lydia. Yeah, if you look at the stack where in-fiora sits is what we labeled the blockchain network, we're much closer to the protocol and the lower level details of how your application will interact with the blockchain that you're building your app on. And the layers that codify builds sit on top of some of the services that we provide. So here's a list. If you're building on something like a private permission chain, you might choose to build on top of Quorum. And within consensus we have the Quorum blockchain service that provides managed blockchain nodes that support the Quorum protocol. And if you're already targeting a public mainnet deployment, we provide the Ethereum API and that's been our core API that we've offered since 2016. What this means is that instead of having to run that infrastructure yourselves internally, you'll be able to utilize our API as an always on, always available up to date API endpoint that's identical to what you would have if you ran your own infrastructure. And that was the core concept that we used when we started the in-fiora product was we wanted developers to be able to build on top of Ethereum as quickly as possible. Whether or not they had experience with like the DevOps skill set that is required to run blockchain infrastructure, a blockchain node or the node software is fairly complex. It has the consensus layers. It has an RPC API server. It has a storage system that needs to scale with the throughput of the transactions on the network and knowing how to provision that infrastructure so it's not something that requires a lot of maintenance was something that we wanted to save teams from. So by offering the Ethereum API as a service, that was kind of a new paradigm at the time when most people were saying you had to run your own blockchain node to participate. And the reason that we kept the API compatible rather than build a proprietary API which there were many that were starting to pop up at the time was because we really feel like the interoperability and openness of the protocol is one of the huge advantages of this that we have, we've built a decentralized network. And if we're providing a traditional centralized service, it's important that people aren't locked into just using our service and our infrastructure versus running their own. And so whether you choose to run a portion of your infrastructure and utilize in Fira for any overflow so that you don't have any issues with scaling or you want to go the other way around and using Fira and still have your own nodes running inside of your own infrastructure in various areas, you can switch seamlessly between the two and that was one of the things that we continue to use as a way to shape like how we present products to our users. And so now to the right, you'll see some of the other networks that we've started to support over the last few years. The polygon network which did I mentioned earlier, the palm network, optimism, the consensus rollups or the sumo project, the IPFS API and Filecoin. If you're not familiar with the two on on the far side can explain this a little bit. I'll start with polygon, though, where, like today was saying polygon offers a EVM compatible so Ethereum tooling compatible commit chain, which allows people to deploy applications with utilizing EVM tooling, utilizing tooling that they're familiar with like in Fira and truffle diligence, things like that, and having the benefit of already supporting proof of stake, which now provides a high transaction benefit, the energy efficiency that a lot of people desire with proof of stake, and also more stable fees that I'll explain more about on the next slides. POM is another offering that we started to support at the at the end of spring of this year, which is focused on providing an NFT platform that's now powering things like the DC Comics launch launch that just happened this week. And then we have the rollup solutions, we're actually missing one from from this I just know this which is the arbitram optimistic rollup solution so we support both the optimism and arbitram optimistic rollups, which are another Ethereum native scaling solution, or layer two. I believe one of the next webinars is going to cover all of our layer two using detail. And then lastly the IPFS and file coin ones are focused on storage, it gets expensive to store data on the public blockchain. And the ideal when people were talking about and designing Ethereum was that we would be able to tie into a decentralized storage network, and the protocol labs team which developed the IPFS protocol and the file coin project are offering a solution for that which is a decentralized storage network that can be tied into Ethereum. All right, next slide please today. All right, so I'm going to talk about the transaction fees and how that will impact your migration and deployment to mainnet and how did that would happen in the context of this product that we provide which is in fear of transactions or itx. So, the, the difference one of the big differences with dealing with a public blockchain is now you're going to have to deal with the gas fee market. Ethereum has been described as a crypto fuel. It's not just a straight digital currency it's a crypto fuel that powers interactions on this virtual machine that allows you to execute smart contracts. That is paying for compute on a distributed network. And to do that, the concept that that was put into Ethereum was this concept of a gas fee that you have to pay for every interaction with a contract. And the fee market is a way to prevent denial of service attacks on the network and every interaction that you might have on the network whether it's a simple value transfer transaction purchasing an NFT interacting with a smart contract powered game is going to have some cost associated with it when it comes to a transaction that gets sent to the network. And when you're deploying on private your fees are pretty stable you're operating costs of running an application on the private network can be pretty stable, or at least predictable based on the growth of that transaction volume. When you're dealing with a public blockchain, I've I've shared these three graphs from ether scan, which is great resource for taking a look at the current transaction activity and analytics of the blockchain from day to day. And on the left you'll see the transaction volume over roughly the last year and a half, and how steadily that grows. And then you look at in the middle, the average gas price. So what is the gas price that the user would have to set to get their transaction included in a block and that's denoted in the way or gig away. It's, I won't get into the details of how to calculate way pricing just roll with me here. The, it's associated with the daily price of ether as well, because that way is like a very small denomination of ether. And because that may vary day to day and the price of ether may vary day to day. From Monday through Friday, your application may have wildly different costs of operation because of because of how the these three variables can change over time. Next slide please. So, so this is the main thing to that you'll have to deal with when you start deploying your application to a public network is the fee market. It's up to you to entice the minor to include your transaction in the next block that there is no centralized entity that's controlling which transactions get included. And that's for both like privacy and security, but nobody can be censored. If you can entice a minor to include your transaction and the way that you entice your minor to include the transaction is by setting your fee appropriately based on the current fee market. There are some great resources. Ether scan that I already mentioned has it right on their front page of this is what the current gas price is that you should set. There's another one called each gas station that provides another API that can tell you this is the historical trend of gas prices and what you need to do to set your fee so that you're at the bottom of this funnel able to get your fee out and not stuck at the top of this funnel where your fee was set too low that you're constantly being priced out. Next slide please. That used to be our simple graphic to explain how fees worked on Ethereum. If you follow the Ethereum space and the developments in the Ethereum space. There was a hard fork called the London hard fork which introduced a fee market change called EIP 1559. And on the right, it roughly goes over what changed there. We don't need to go into too much detail. But the goal of the IP 1559 was to make it easier for people to understand how to incentivize a minor to include their transaction in the network where a tip can be sent specifically to a minor. And there's always a base fee for the transaction or the contract invocation. That way people can better estimate the costs of their transactions and if you look at the impact that that had over the gas markets over the last couple of months. It really did a great job of adding some predictability and stability to the to the fee market. Next slide please. So what happens when the funnel gets filled up when the transaction keys on this network fill up is that transactions get dropped. So you can see those three envelopes that we have showing you know these transactions are getting dropped from the queue. This isn't in furious queue. If you're running your own infrastructure that's not your queue. This key that we're talking about is the global transaction pool. And the way to that that works out like a technical level is every single node on the network dedicates a portion of its memory to storing a certain number of transactions and there's a limit to that. And regardless of you know how how many optimizations the core developers made to the throughput of the network that queue will remain limited by the amount of memory that's available to store these transactions. So if there's a large spike in transaction volume this queue is going to fill up and the lower price transactions are going to get priced out and they may get dropped. And what happens when a transaction gets dropped is it breaks the delivery chain. So if you look on the right, every transaction on on the network that comes from your account needs to have a sequential order. So I first send transaction one and then I'll send transactions to through 99 and I can't send transaction 99 without sending everything in between first. But what happens when that delivery chain gets broken because maybe I set the gas price to low on the transaction and it creates this gap. Next slide please. What happens is the that queue or specifically your queue could get stuck. So I sent transaction one on the left it was successful I sent the next transaction number two it was successful. And then I figured maybe I would try to optimize my fees and set a lower price on that third transaction, and then it gets dropped. And the reason it gets dropped is because maybe maybe I didn't even do anything maybe I kept my fee the same, but all of a sudden the transaction volume on this public transaction pool went up and my transaction got dropped from the network. And because of that, I need to be rebroadcasting these transactions so that and you know checking where my fee is in relation to other fees on the network to ensure that I can get that third transaction mind. Otherwise transactions for five and six there are going to get stuck. And there have been some pretty notable cases where that's happened and had a significant impact on teams and products that are already live in production on not just at the end but all public blockchains. Next slide please. This Black Thursday event was specifically one that affected the maker ecosystem, where there was an issue where on March 12 of 2020. There was a huge spike in transactions that ended up affecting the maker ecosystem because they had a component that was stuck behind and they had a gap in their, their transactions and couldn't get the interactions to happen on chain within the amount of time and it had a bunch of cascading effects down stream that took a while to recover. So we're continuing to try to get their transactions into. I don't want to get too much into the specifics of maker, but essentially to protect their investments that they had inside of the maker product, and that resulted in kind of like exacerbating the more transactions on the network made the problem worse, not better. And if, if systems are architected a little bit differently, it can help avoid this type of situation. Next slide. Solving these problems is not trivial with a lot of people end up having to build custom infrastructure specific to their use case to be able to solve this issue. Sometimes it's as simple as retrying a transaction and saying if my transaction didn't get mined within a minute, five minutes, 10 minutes, whatever is acceptable to your application, you can retry that transaction. And some people build much more intricate retry mechanisms that look at, you know, the current gas market actual pending transactions on the network and being much more competitive, if not adversarial with how you retry your transactions, especially if you're building a defi trading platform or something where every second matters to get your transaction included into a block as quickly as possible. And so it either requires dedicated infrastructure. There's a lot of issues with the guarantees that can be made. And of course potential loss of funds that CDP example let's know that is the issue that was impacting that maker black Thursday. Next slide please. So what our inferior transaction service provides is a way to, like we offer the way to outsource your Ethereum node infrastructure to outsource the transaction infrastructure, instead of building your own in house relay or to send your transaction. We offer a dedicated API that is able to guarantee transaction delivery and make sure that there are no step transactions in your transaction queue. Next slide please. But the way that our system works is that when instead of having to build that custom retry logic into your application you send us that transaction once, and then our ITX system is responsible for periodically republishing that transaction. So maybe it is getting priced out right now, but when you send us the transaction, you basically put it on a queue of when you need that transaction included whether it's within, you know, the next two or three blocks, the next 10 blocks and the next 100 blocks, like you're basically able to set the priority yourself and we'll do our best to republish it to ensure it gets included within that amount of time. And if there's a fee adjustment that needs to be made, then we're able to make that fee adjustment for you without any interaction on your, on your side or for your customer. Next slide please. Yep. Yeah, so I'll walk you through one example use case of how that could work and why that could be beneficial. Next slide. We have this concept called sponsored transaction infrastructure that we've helped a couple of teams implement on top of ITX. This is not something that you need ITX to build you can 100% build this in-house yourself. What we were trying to do was level the playing field because at these times when we were seeing that more sophisticated and better educated users on the mechanisms required with the gas fee market were able to out-compete newer entrants into the space when it came to like DeFi trading in particular that these specific groups were able to build this custom infrastructure to monitor the pending transaction pool and rebroadcast their transactions and get their transactions included because they had this custom relayer. By us having this custom relayer it allowed people to build similar systems without having to have all of that prior knowledge. And the sponsored transactions example is one of the things that came up is how can a user say swap tokens if they don't have ether. Meaning yes ether is a token but the tokens I'm referring to here specifically the ERC 20 tokens. Matic which is the polygon token is an ERC 20. So say you had 10 Matic in your Ethereum wallet and you wanted to transfer it to another service or sorry, another account. You would need to first transfer ether to that account that held the Matic tokens and then you would be able to use that ether as gas or transaction fuel to get your Matic out of that account and into another one. By having a relayer infrastructure, you're actually able to do what's called a meta transaction or a gas list transaction, something that allows you to transfer these ERC 20 tokens where somebody else pays for the transaction fee on your behalf. And that's like the core principle that's enabled through having a relayer is you can build a system that can pay for transaction fees on behalf of the user. Next slide please. And so once the system was built, you can set a different fee schedule where that intermediary that is sponsoring the transaction on behalf of the user can receive a payment in the ERC 20 token itself for the fee. And that fee is set based on how fast they want the transaction included, whether it's very quickly, meaning under 10 blocks or slowly like it says here, which is a couple of hundred blocks, that fee can vary and that person who's sponsoring the transaction can take a higher or lower fee. If I had 10 Matic tokens, and I wanted it involved, included quickly, I can try to send this transaction. The person that built this sponsored transaction application can take a cut of the actual transfer or swap. I never had to have ether in my account to make that happen. It just gets deducted from my Matic token balance to be able to pay for the actual transaction fee. I think that was it for this next slide. Yeah, so, so thank you very much. I hope that provides some clarity on what inferior transactions provides and the different things that we provide it in fear and consensus. And I think we are opening it up now for the Q&A. Great. Wonderful. And as a reminder everyone, you can ask your questions in three different ways. Number one, if you want to do a voice, if you want to ask your questions via voice please raise your hand use the raise hand feature in zoom. And we'll go ahead and permission you to speak and it'll be great to hear your voice and say hello. Number two is feel free to drop some questions into the question and answer tool. Just click on that ask your question and we'll get to those. And we will read the ones that are there already because there are some people on the live stream and then in the recording that won't see the Q&A section so we'll do those on voice. And last but not least if there's any questions you can also just drop them straight into the chat feature and we can get them going. So, there was a question that was answered in the Q&A, Marta Pekarska actually asked a question around, how does info choose the layer to that's going to be used or is that the responsibility of the user. Did you you did put some answers in there but perhaps you can elaborate on that as well. I think I mean whoever deploys the application and is the is the owner of the insurance account. Ultimately will configure the application to use particular insurance points that correspond to a particular venue. So, it's the responsibility of user use the user as in the intro user, not the end user of the application. Right. There's another question also from Marta, perhaps Didier you can read that one off if you would like to answer it. Yes, so maybe this one is for EG. Does ATX help with things like to low sleep age set in case of events like LBPs where a user sets a price to X but by the time the transaction shows up in the queue, the price changes by X plus 10% or when gas randomly jumps. So that's not something that we do currently, because it requires some introspection into the that specific trade to understand the slippage and be able to cancel the transaction. That being said it is something that a few other groups have started integrating ITX have currently built themselves, and have asked us if it's something that we can integrate into our systems, which would be a way to cancel the transaction if we see that it's no longer going to be successful. That if you are going to do it manually basically means you send a cancel transaction, a higher trend, a same nonce transaction with a higher gas fee that will then cancel out that trade that you already had in the transaction pool. So once you have a transaction in that transaction pool there's no guarantees that can be made though because a miner can always decide they're still going to include that transaction regardless of if there's one with a higher fee. But it is something that we can at least try to help users with but no not something we support. Wonderful. Martin that answer your question. Anybody else have any questions. Once again, just put them in the chat or raise your hand and we will get to you. One of the questions I have you know in particular EG you had on your slide specific to palm as one of the side chains that uses hyperledger basu and kind of to the to the question of how do you how do you choose specific to the hyperledger community and hyperledger basu do you have any any other examples or summary of why someone should be looking at hyperledger basu specifically. Yeah. So, historically we we had been running the go Ethereum client because that was the main one that was used at the time that we started and for legacy reasons that's our historical reasons that's just what we've maintained for a large amount of our infrastructure, but we've worked closely with the Basie team are early on the pantheon team sharing requirements of what we were seeing with, you know, the difficulties of running node infrastructure at scale, whether it's slow RPC performance, or issues, sinking clients relatively quickly where it takes, not just days but weeks to sink a new Ethereum client from scratch, and get the full blockchain downloaded. And so I think the Basie team has really been great with working with us to understand what the current issues are with the client, the primary client that we are running and how they could improve on those, especially when it comes to some of these other things that are deployments that have been supported with Basie that have a much faster state growth, whether that's because it's deployed on private or because they're using a POA system to be able to get a higher transaction throughput that it runs into some scaling issues sooner than what the current proof of work Ethereum network does. And so we wanted to work with the Basie team on deploying the POM network support, because we knew that this was going to be a network that would very quickly see, you know, rapid adoption, got some very exciting early projects already lined up and we wanted to make sure that any scaling issues that we would encounter, where things that we could surface and try to get prioritized as quickly as possible and we've had a great time working with with the Basie engineers. Yeah, it's great. Yeah, definitely seeing a lot of activity around the POM network and made me a very cool mom because of the DC Comics NFT drop so I was happy about that because my daughter's like that's this hyper ledger so great, great, great answer. Once again, if anybody has any other additional questions, go ahead and queue them up. I do have a question Didier and EG, you know, specific, you know, when we started this webinar I talked a little bit about the relationship and kind of the collaboration that we've done. And that's what we've had with the Ethereum ecosystem for since the beginning of our project. Maybe you can tell us a bit about where what you see is as different in today's enterprise blockchain conversations that you're having across the different industries, where, yeah, that that's the question like what's different. What kind of questions are you getting from these enterprise businesses that are interested in in the Ethereum ecosystem. Yes, I think, I mean, things change quite a bit in the sense that three, four years ago, people were very much focused on using private networks focused on use cases around mostly around, I would say, you know, cost reduction business process automation and things like that. And over time, digital assets became quite prominent use cases. And I think, as those use cases emerged, the opportunity of using public infrastructure became more evident to some of those enterprises. And also because, like I mentioned, although private networks are great to spin up initial use cases and or potentially highly regulated use cases, it could be another example, like we mentioned USC and finality for example earlier. But in the end, there are lots of frictions around adoption, broadening the ecosystem with with private networks that become much easier when you're on public infrastructure. It immediately exposes the use cases you deploy and the assets that you deploy to the entire ecosystem and potentially some of your counterparts. So it just makes things more smooth. And I think more and more people see their main net and also tools and sidechains as really good venues for settlement of securities and potentially in some cases securities versus E-money. And we see, I think, more and more experiments, pilots, so live pilots of particularly financial institutions, trying to continue to use main net and even possibly in the case, recent case of Société Générale interacting with some of the DeFi protocols as well. I think it will become more and more the case as regulation clarifies as well. For sure. But these are the main reasons why people explore public networks. We still see a lot of supply chain use cases or focused on provenance use cases, so satisfying provenance of assets in particular that are still deployed on private networks. So we still see a prominent number, a large number of private network use cases, making use of Corm, Hyperledger, Bezu, and ArcCorp blockchain service infrastructure. But I think the trend of using main net is growing. Yeah, well certainly it's a continuum of different hybrid requirements, et cetera, as we continue to see that. Well, thank you. I know there's another question, but we are at the hour. I want to thank EG and DDR for today's session. Once again, this is part of an educational series around, you know, and Ethereum and the public main net. We encourage you to come and view some of our other sessions that are coming in. Once again, you know, Hyperledger Bezu is one of our Hyperledger projects, one of our distributed ledgers. We welcome everyone to come join the Hyperledger Bezu community. If you go on our website, you can get involved to see the wikis, the chats, et cetera. We also have a free online self-paced MOOC that is available via the edX platform that is available for anyone it's free to use you could get a certificate at the end via the website for I believe it's $99 US dollars. But please do take a look at that course. It's off the hyperledger.org training website so as part of our educational series we're going to continue doing project specific and industry specific sessions. Upcoming in November we'll have some project workshops which will be multiple hour workshops specific to Hyperledger Aries and Hyperledger Indy focused on our identity solutions within the Hyperledger project. Also coming up we have an in-depth hour with Ledger Leopard on supply chain traceability. This one is also a Hyperledger Bezu project that Ledger Leopard has put out with RTI. Oliver Rickin will be speaking about their use case and the benefits that their customer RTI has already seen using Hyperledger. And there's a case study on our website that gives you the full details if you want to read in advance of that session. The next Ethereum based education series will be on November 3 at 8 am Pacific time. This one will be on DeFi and DAOs deep dive into unprecedented DeFi growth and Liz Matthew who's the head of strategic sales at Consensus in the US will be joining us for that session so please do register for that session as well. We have a lot of great content across all our projects Hyperledger Fabric, Sawtooth, Bezu, Indy and more via the Global Forum which happened in June and we'll be doing additional sessions as we go through. We are open community so please do get involved. There's many ways that you as an individual or as a company can join us. Please do take a look at some of the resources that we make available and provide any feedback that you have on more content that you'd like to see and more things that you would like to see from us. So once again thank you for watching. We really appreciate your time and your questions. If you have any questions, Didier and EG how do they get in touch with you. By email so EG shared his email and I can share mine as well. You'll put your email address into the chat room. So once again if you have any questions feel free to reach out to EG or Didier. And to myself as well anybody on our team if you send questions to membership at hyperledger.org will get back to you as soon as we can. So once again, thank you for watching and we will see you soon. Thank you.