 people. Okay. Great. All right. Thanks. Thank you, David. Thank you for the opportunity to talk about this important topic on Webster Technologies and how they are beginning to permeate into enterprise and government solutions. Great to see the audience here. I see folks from from Tampa to Barcelona, Nigeria, India, and very hot southern France here as well. Great. All right. So, just a brief introduction. I have been working on blockchain, enterprise blockchain predominantly at Oracle since around 2016 when we joined Hyperledger and began our work on delivering an enterprise blockchain platform. Been at it ever since. Obviously, saw a lot of changes and a lot of transformation in blockchain space. Webster Technologies over the last few years, of course, in public change initially, but later findings away into enterprise solutions as well. And, you know, I'm going to try to take you on this journey today to sort of give you a sense of how we're seeing it, how an enterprise customers and government customers are beginning to take advantage of some of these capabilities. We've had quite a bit of customer success in this space. Oracle has been picked for the last three years by Forbes Blockchain 50. And, you know, to a large extent, it's based on, you know, successful customer deployments and sort of growth of the momentum in our blockchain efforts. So, I'm going to cover today a few topics. We're going to start with sort of basic definition of what we see as Webster. It's a very loosely used terms these days, very broadly used terms that I think bear is defining and have some thoughts on how we can approach a definition. A little introduction of Oracle Blockchain platform, which is based on extended capabilities of this Hyperledger Fabric Foundation. And then we'll talk about two key distinguishing areas of Webster, portable digital assets or tokenization, how we approach it, how we're providing the capabilities and some customer examples. And then around the central identity as well, how we're looking at providing those capabilities for verified credentials and where they are, we're beginning to see them being used. And then just close with some, you know, Q&A and links to some additional materials. So, let's get going. We have a lot to cover. And as I mentioned, definition is always a challenge with, you know, Webster. People have widely different opinions. There was this question raised on Twitter a couple of years ago and you see some sample responses, you know, anything from self-sovereignty and community ownership, exit liquidity, grave delusion, transactional. People obviously, you know, view Webster as their own particular lens and depending on, you know, their focus and their experience and, you know, the capabilities that they are trying to bring to market, if they are part of a startup, you know, this is all varies quite a bit. So, what do we see as sort of key aspects of Webster? I think there are two trends, two sets of trends, right? From the top, we have sort of decentralization and disintermediation, right? You know, people are obviously concerned about the platforms that own your content and they want to make sure that content creators have ability to own their content, earn from their content, don't have to sign off your rights, etc. And that there is a sort of decentralization approach to providing variety of the services. On the other side, bottom up, there is a range of technologies that we have seen emerge, decanization of portable digital assets, right? And portable is really important because decanization tokens that live only on one chain are not that interesting. When they become portable, they become really exciting. The centralized identities and related to that verified credentials is another area that's quite important and it's opening up new capabilities for, you know, individual identity, but also some interesting ways of dealing with a variety of what you would call claims, documentary claims and so on. The centralized storage is another big focus area. It's providing ability to, you know, leverage platforms that resist any kind of censoring and then the centralized governance, right? Of course, DAOs and, you know, there are some, you know, other forms that are emerging in this area. And I think we're going to see a convergence between sort of the stop-down desire for decentralization and the set of technologies coming down from the bottom up that will help us arrive at sort of this next generation of interactions of various sorts, person-to-person interactions, you know, business-to-consumer, business-to-business government to person-government of business and so on. And those interactions are going to be characterized by a few things. They're going to be obviously powered by blockchain and increasingly artificial intelligence, particularly generative AI tools. They're going to be amplified by the immersive capability, virtual augmented and extended reality. And they're going to enable a set of services and capabilities such as digital identities, wallet smart contracts, off-chain edge computing, etc., and perhaps many others we haven't even sort of. But they're all going to benefit from sort of the core set of technologies and the demand, if you will, and the desire to provide greater and greater disintermediation and decentralization capabilities. So to drill down into this a little bit more, right, there are the pigs of four specific areas which is portable digital assets, decentralized data storage, decentralized identity, and decentralized governance. You know, what are some of the specific standards that are emerging in those areas? So in tokenization, of course, we see ERC standards, ERC-20 for fungible tokens, 721, 1155 and a number of others for non-fungible tokens, token taxonomy framework as well, which is kind of trying to bring together a unifying framework across a number of different token standards. In centralized data storage, you know, IPFS, many of you know about Zero Chain, which is an oracle partner from a while back, providing similar technologies. For the centralized identity, we see, of course, DADs, the centralized identifiers, and W3C has been doing a lot of work in verified credentials of ECs, and there is a number of standards that have been emerging from that area. For the centralized governance, we have a range of different consensus mechanisms, which I would argue are part of the centralized governance, particularly from an enterprise perspective, you know, consortium models and others, and DAOs, of course, which are more programmable, smart contract-driven governance models. They all have specific, you know, benefits, which is why things that begin to matter not only from a consumer perspective, but from enterprise and government perspective, right? So tokens obviously provide capabilities to do financial transactions without requiring, you know, banks or intermediaries, you can use them to protect IP ownership because they can represent variety of intellectual property, they can provide traceable history of, you know, life cycle transactions associated with non-fungible tokens that can be used to represent, you know, digital art, music, product, increasingly we're beginning to see use of NFT to represent product components, ingredients, and, you know, product assembly kind of things like that. The centralized storage obviously, as I mentioned, has a straight benefit in terms of no censorship, but also privacy compliance and transparent sharing of data, which is even more important. The centralized identity enables user control and greater privacy for many users, more granular claims, right? Many of you have heard, you know, the example where you are, you know, if you're going to, let's say, a bar with 21 years of age cut-off requirement, you can prove that you're over 21 without having to disclose all those information in your driver license. That's sort of a classic example of the centralized identity and verified credentials, but there's many others, right? It enables trusted interactions in the sense that your identity claims, whatever they might be, whether it's, you know, about organization, you belong to certifications that you have, whether it's your age range or other things, can be proven with cryptographic means in a way that the verify organization that needs it to be proved can really trust in the result, right? And you have to wonder if what somebody told them is true, if the piece of document and signature is showing a valid, et cetera, there is, you know, a different quality to cryptographic proofs, because they're much harder to, you know, much harder to manipulate. And you can also, you know, use this in terms of reducing any kind of credential and document front, and I think this is really important. So this is, you know, a lot of different benefits that we're beginning to see being leveraged both from an enterprise perspective and from government, and I'll talk about that later. And then when we talk about the centralized governance, right, the benefits of this collaboration was they were stakeholders, stakeholders, whether you are doing it in a, you know, Dao were just, you know, a group of organizations that people came together or maybe supporting a particular sports team, we're beginning to see some interest in sports leagues, giving Dao governed teams, automation in decision making and speed, of course, transparency and such, and I think we're beginning to increasingly see governance questions being raised in consortium networks, whether we're talking about supply chain provenance or other kind of things, where some degree of governance automation is important, and the different programmable capabilities and structures are coming to play as well. So let's talk a little bit about tokenization and portable digital license, because it's always a big part of app three, right? Tokens obviously help to transfer ownership or potentially rights to the asset, maybe not ownership completely, but you can define certain rights. You can verify ownership history, probably again, cryptographically without requiring intermediaries. You can support fractional ownership, which is kind of important to increase liquidity of certain assets and enable participation. You can track digital assets or digital twin of a physical asset represented as a token as well. In variety of transactions, whether it's bit to see engagements or bit to bit transactions, there is actually a great paper that was published by UECD in 2020 that talks about different categories of tokens, tokens that are native to blockchain, that exist only on chain and tokens that exist both on chain and off chain, representing a pre-existing real asset. So this is becoming quite important in variety of areas. You know, of course, traditionally started with Bitcoin, and of course, there's many cryptocurrency chains out there these days, you know, some are more legitimate. So now this obviously, but we have seen an explosion of that with Ethereum programmable tokens, right? So we all know about here is it 20s for fungible tokens, 721 for non fungible, but then there is emerging things like 1155 spec that combines fungible and non fungible tokens in a single contract. ERC 1400, which provides a little bit more capabilities around standardized tokenization for securities. There is emerging networks, you know, things like flow, for example, furniture, marketplaces, many others. And there is a lot of emerging enterprises cases, right? So on a fungible side, we're increasing the beginning to see tokens used in rewards programs and loyalty points in particular, particularly multi-brand loyalty points, royalty tracking for intellectual property, payments and particularly micro payments, cross-border funds transfers, of course, and, you know, bank back digital currency and CBDCs as well. But what you might have seen recently is that Central Bank of Philippines announced a wholesale CBDC project for which they've selected Hyperlegia Fabric Technology as a baseline. So we're beginning to see a lot more, you know, CBDC projects beginning to leverage Hyperlegia technology. For NFTs, we see also rewards programs, particularly providing kind of VAP awards of various sorts. And I'll talk about one example that we're working with right now, product riskability component riskability, particularly in those regulated production supply chains that are, you know, very strict about provenance of the components and products and how those products come together into sub-assemblies and things like that. There is a big movement around electric vehicle batteries. And batteries in general, particularly in the circular economy, battery passports, a big thing Germany has passed. I'll give you some recent regulations and has an initiative called battery pass to track all of the batteries, ensure that they get recycled, etc., in logistics, electronic bill of lading, which is a document that conveys both custody and ownership rights and goes and gets passed from, you know, the shippers to the different carriers and to the receiver ultimately. Also in supply chain, we're seeing certifications, qualifications and other things being expressed, leveraging NFTs and so on. So quite a bit of effort in these areas that really tell us that the organization has arrived into enterprise space. Now, in Oracle's approach, as I mentioned, our platform started with and continues to this day to run on Hyperledger Fabric, which doesn't have native token support. But many of our customers and partners have built application chain codes that emulate fungible tokens or non-fungible tokens. And in order to try to make it easier for everybody, we decided at some point a few years ago that we would provide more standardized application chain code available as building blocks so that, you know, every customer application doesn't have to build its own. We have a development loco tool called blockchain upbuilder that's able to generate chain codes from a specification. So we started by essentially creating a specification, leveraging a standard like token taxonomy framework, which is essentially a meta model that allows us to define different token types, behaviors, custom properties and so on. And then we can use those specification templates. And we have automated life cycle, automated chain code generation capabilities. So we can generate chain code, managing all of the life cycle, all of the, you know, behaviors, mintable, transferable, vulnerable, all of the standard behaviors that you would need for a token based on a particular token-based token type, properties, etc. We've also done some work to optimize Hyperledger Fabric peer logic so that we can avoid the missing conflicts when you are updating, you know, multiple token transactions the same block for the same account and so on. And we have since extended that with non-fungible token support including ERC 721, which provides a whole non-fungible token and then ERC 1155 that allows us to combine both non-fungible and fungible tokens and support whole and fractional variations of those. So I'll show you how we do that. So it's just a little bit of an introduction if you're willing to keep building blocks and we'll talk a little bit more about the centralized identity as well as we get there. But let me give you a little bit of an overview of Oracle Blockchain Platform built on Hyperledger Fabric as I mentioned. So you'll see standard peer nodes ordering service, which is a set of nodes that create and, you know, mint blocks from the transaction, sends them back to peer nodes to append to the ledger once transaction has been verified. Peer nodes also were smart contracts executed. Membership service, which is Fabric CA, that's because this is a permission network, allows us to create identities for organizations, create identities for the different, you know, affiliated members, if you will, client organizations, as well as for the nodes themselves ordering nodes, peer nodes, and so on for interaction because all of the interactions here are done through signed messaging. So in order to verify that the signature is valid and any message that any node receives, you have to be able to apply PKCS standards to, you know, and that's based on the private public keys. We have enriched this environment with a set of additional capabilities, operations management tooling, that makes it easier to run in an enterprise environment, integration gateways that provides REST APIs and events with callbacks capability to expose smart contract APIs and core peer APIs, order APIs, et cetera, through REST protocol. We make it easier to integrate a development tool called low code blockchain upbuilder, which among other things, he has a built-in tokenization engine that allows us to deploy tokenization chain codes, integration with an indexing database using Oracle database, no surprises there to provide for access to metadata and transaction payload data and so on in a way that supports high volume queries, live analytics, machine learning integration, and the like. This is an environment that can be deployed in Oracle Cloud as a managed service, a blockchain as a service option, as well as we have this enterprise addition that can be deployed outside of Oracle Cloud on premises or into third-party cloud environments. We're also, of course, very compatible with third-party Hyperledge Fabric nodes and in fact, we have production customers that are running Hyperledge Fabric networks, spending our nodes and third-party cloud nodes as well. All of it's preassembled, so you can quickly provision it in a matter of 10, 15 minutes with all of the built-in resources, everything you see here, and start working on integrating applications, which is where the value comes in, right, blockchain by itself without a transaction flow, without sharing data is not going to be particularly useful, but you start integrating applications, you can do that through the Hyperledge client SDKs, through our SAPIs and a variety of integration adapters that we provide with Oracle and third-party applications as well. There's been a lot of innovation that we've done, we started in 2016, we've released our first version in 2018, a lot of infrastructure for high availability, dynamic scaling, identity management integration, and on and on security, block integrity verification, fine-grained ACLs on chain for enterprises that need more granular security, management tooling around operations management, monitoring dashboards, etc., versus WebUI and a set of DevOps APIs, development portal and so on. The API gateways that are touched on, which manages and automates a lot of interactions from a client application side, discover a transaction orchestration, provides REST APIs for asynchronous transactions, event subscription with reliable callback. We've added recently a two-phase commit-based atomic transaction coordination, which allows us to coordinate not only transactions across multiple fabric channels, but also XOpen, XA standard resource manager, for external transaction managers, which allows us to do two-phase commit or atomic transaction updates across both off-chain resources and blockchain resources on chain, and extending that recently to support Ethereum interoperability so that you can now do atomic transaction update across both hypolygia fabric and Ethereum or any EVM-based networks out there with the same kind of capability, with optimization called LRC, because obviously EVM networks in Ethereum don't provide a two-phase commit, but in a two-phase commit orchestration, you're allowed to have one resource where you can do a transaction and you can determine finality as it has been committed and then do it in two phases on the other components, like hypolygia fabric with Oracle extensions. Our local development tool, blockchain upbuilder, which integrates development, build, deploy, test tooling, and provides auto generation of both chain codes scaffolding and the chain codes themselves with local remote deployment options, tailorable templates, and a lot of built-in security as well, so there is role-based and functional based security generated into the chain code. And based on top of that tokenization digital lots, as I mentioned earlier, for fungible tokens, TTF extension of year 220 for non-fungible year 721, and then combination of fungible and non-fungible in the RC-1155. We've also added an exchange pool mechanism, so if you're doing fungible tokens for multi-currency, let's say multi-currency, CBDC, or multi-brand loyalty points where you need to exchange them to have different weights, so the built-in liquidity pool mechanism, and then CBDC sandbox infrastructure that allows us to take this technology into CBDC engagements and have not only the tokenization engine, but all of the necessary interbank kind of a CBDC capabilities, analytics, auditing, and many other things that central banks are quite interested in if they're going to experiment in CBDC technology. Very easy to find if actually in Oracle Cloud you have an account or you can provision a free trial one. There is this menu here on the top left that allows you to drop down to developer services and then select blockchain platform. Very quickly provision a few different parameters you would specify, click create. It basically orchestrates and marshals all of the resources necessary both infrastructure, fabric nodes, and all of that on components. And 15 minutes later you have notifications that this is ready for you to run, deploy chain codes, and so on. And you can go and bring up a console, download from developer portals, blockchain outbuilders, start experimenting with that. The console's got a lot of interesting capabilities for administration, configuration, management out of the box. These are easy to use web UI without requiring a PhD in blockchain, life cycle management for smart contracts, monitoring, troubleshooting, etc. Ledger browser, channel browser, and so on. Many tools out there. I mentioned the mixing database. This is something that we found quite important because there is a lot of things that you'd want to do. This is data with a ledger data off chain, right? You cannot run effective live analytics at the rate at the speed of smart contracts responding to queries, right? So if you're going to be looking at aggregated data over large time, or large number of users, etc., it's really expensive to do that on chain, but by asynchronously updating a schema in Oracle Database, what we call Rich History Database, we can now provide all kinds of live analytics on that and other kind of indexing operations. Some section of the message I wanted to highlight that. So in our REST API, we essentially have these two phase implementations. You can specify a transaction array with multiple chain codes and multiple channels, right? So let's say we have traditional fabric marbles chain code example representing some goods that you're transferring on channel goods. And then you have a channel wallet where you've deployed the payment chain code. So you want to make sure that payment and the transfer of the marbles is done atomically. And so everything guys that commits or it rolls back, you can do that by specifying essentially atomic transaction API code with this kind of a payload, right? And we actually now extended that as I said to work not only across fabric, but fabric and Ethereum or EVM networks. And this allows us to essentially use this two phase commit mechanism, but we put a transaction in the prepare for us phase first across the different channels and networks. And then we check that events have been published on commit through section commit, fabric and section commit. And then we do a commit rollback. So this is actually going to get a commit rather, this is going to get updated in the state DB. And there's a bunch of others. We've done a lot of work in different use cases. I'll invite you to take a look at the eBooks that we have. There is a link here. You can scan also the QR code to get access to it. And there is a lot of interesting stuff on our use cases and for the blockchain enhancements and so on. We're also picked by Juniper Research on top of the leaderboard when they did assessment of the different blockchain platforms. But I wanted to talk a bit more about tokenization and how we can provide that on fabric, right? Because fabric does not have this native capabilities of its built-in tokens. So in addition to all of the infrastructure stuff to make it easy to run, easy to secure, easy to extend and so on, we felt the need to really simplify the adoption by creating applications ecosystem and have a lot of partners that provide capabilities across many different industries, as well as financial services, logistics, manufacturing, et cetera. Got cut off a little at the top. Sorry about that. And then custom applications through the slow code development tooling that supports automated chain code generation with built-in tokenization support as well. So this is a tool that's built on essentially Visual Studio Code extension for the GUI part, but also has a command line interface for CI, CD kind of things. It allows you to manage entire development tests, deployment lifecycle for chain codes, just built-in Fabric 2.5 for testing and supports all of the chain code lifecycle operations and the packaging and storing and so on. So when you generate here the chain codes from templates, you can then automatically deploy them, not only on Oracle blockchain, but any Hyperledger Fabric node. You can package them and we have specific deployment accelerators, if you will, for Oracle Networks for our SDPIs, but you can package and deploy and it will run its standard Fabric chain codes. It's generated either in TypeScript for Node.js or Go. And when you generate, you can pick the target language that you want to generate in and will essentially generate all of the CRUD methods. So if you want to define some kind of a document or product object or anything else that you want to track on chain, we can generate all of the create, query, update, delete methods out of the box. And if you're specifying a token chain code, so if you're selecting a particular token spec, we'll generate the lifecycle methods appropriate to that particular token spec. Right. So you can use spec files that are either in YAML or JSON format. I'll show you examples of what they look like, a little bit big examples in the next couple slides. And automatically, as I said, scaffold and generate smart contract project and code directly from specification. You can then deploy it as is, if you want to, or you can add custom methods if you need additional business logic that's a little bit more comprehensive. You can deploy it locally on 2.4 Fabric, 2.5. You have local built-in fabric here. And then you can test and debug using standard visual code debugging tools. We're also providing, by the way, in our latest release, ability to generate in a recipe as automatically so you can test against deployed environment. And then you can package and deploy to Oracle blockchain platform on premises or in the cloud and start basically running through the rest APIs for those chain codes that have been deployed because they're automatically exposed. Or you can go through a menu here with all those generated token methods. So that's how to speed up the development and deployment and testing and so on. So how we apply this for tokenization. So we have essentially created models, metamodals, that are helping us to generate either based on TTF or ERC-721, ERC-1155, the necessary token lifecycle chain codes from those templates. And this has integrated identity management in the SAPI because this is an account-based token engine. It also supports liquidity pools mechanisms that I mentioned earlier as a liquidity or exchange pools that allow you to exchange fungible tokens based on whatever exchange rates that you might want to set using APIs. So on the left-hand side, this is what the template might look like. We provide standard templates. This is for fungible chain code with different behaviors, custom properties and extensions, etc. And we will go ahead and generate the setup methods and then the actual token operations like issuing, transferring, as-grow methods as well as born tokens. And this is out of the box, literally. And this allows enterprises to begin to use those tokens in a variety of applications. And like I said, we've seen them in current applications with digital currency like CBDC. We've seen them in loyalty systems and others. This is based essentially on generating a core SDK methods for different frameworks that I mentioned. It has custodial wallets built in with an account by system, and we're working on support for non-custodial wallets down the road as well. And then we create a set of wrapper functions that is 30 plus wrapper functions that allow you to much easier interact with those methods. All of them allow you to pass organization ID and use ID as function parameters. So you can tie them to this particular account. You can customize them, of course, extend them. There is function level security as well. So if you want to restrict that using fine-grained access control, as I mentioned, you can do that. And there is a role by security. So we can generate automatically specific role management methods for mint, burner, and notary roles. And of course, based on the account and the role assigned, and there are methods to assign the roles, we can also identify the call of the function and then ensure that the security is applied appropriately. So you could use these methods directly through the REST APIs that we expose, or you can add additional custom chain code methods on top, because everything you get is in source. So you can do more complex business logic. Or you can also use cross-chain code and vocation to invoke them from additional, from existing smart contracts or other smart content that you might have that deal with maybe other objects, but need the, you know, core tokenization support. And so the previous slide I showed you was for fungible token. Here's the examples of the templates that we support for non-fungible. This is the RC721. And the plus means that we have taken the liberty to extend it a little bit to make it a little bit more useful from an enterprise perspective, like adding vulnerable properties. So you could burn it, adding ability to have custom properties and custom metadata. Custom metadata is assigned, of course, when you mint the token, custom properties are changeable, updatable by current owner of the token. So this token gets transferred, the current owner gets to update, and you can specify whatever properties you want here. Then we have RC1155, similarly extended, but in the RC1155 spec, you can combine non-fungible tokens and fungible tokens as well, right? So this allows you to create an environment where you could, for example, exchange fungible tokens as a payment for non-fungible tokens or vice versa, and there are applications that take advantage of that. And most recently, we've released fractional non-fungible token support as well. So there is an example template we provide for real estate, for example, this is a great example of a non-fungible NFT they use. But you can think about intellectual property, where you have different kind of licensing rights, and a number of other use cases where fractional NFTs come in handy. And again, you can have custom properties, and it's dynamic NFT in that sense, right? So there's some examples of the templates for the tokens. Exchange pool, just to illustrate that, you can create them, you can initialize them by initializing the exchange pool user, and that user will have multiple subaccounts for different currencies that you define. You can set exchange rates or update them, you can fund the exchange pool by either as a percentage of minting, so you can call a mint function and provide a percentage of the minting amount that goes to the exchange pool, or regular transfers, right? So there could be participants which are regular liquidity providers, and they can do a transfer into those pools. And ultimately, you can call a convert method, token conversion, specify a token going in one currency token ID, essentially, and to be transferred to a different account in a different currency. So you can say, for now, I want to do token ID, XYZ USD, 100 units, and they want to transfer that in XYZ euro to an different account. And this is essentially a liquidity pool mechanism, what will happen is internal swap. And again, this is done atomically in a way that ensures that, you know, that transaction completes successfully across to the target account, or it's rolled back across everywhere and everybody keeps their own money. Ethereum interoperability is something that also I think is important as a first step towards portability and portable digital assets. So we have taken essentially our infrastructure with API gateway and tokenization system, we have enriched it by providing and built an Ethereum client that's part of the two phase commit orchestration. And what we can do then is we can do two phase commit with extended LRC optimization transfer. So you could do a prepare, for example, operation on the chain code methods on the fabric side, you can then do a commit and verify and you can specify finality parameters, how many blocks to wait, and, you know, whether you want to, you know, wait for a certain amount of time. And then when this reaches the finality conditions you specified, then we'll go and do commit on the side, right? So this guy was to commit. So a quick response here, somebody was asking in the chat if the blockchain outbuilder is good to use for use cases other than tokenization. Yes, in fact, it was built before we had tokenization support for generic use cases. So you can spec whatever data assets you want to track and generates a chain code, which will give you all of the crowd methods and operations and APIs and so on. And we've added tokenization on top of that in addition to the core generic stuff. By the way, you can mix non-token assets into the tokenization template. So tokenization templates basically extend the particular tokenization standard as a generic template mechanism, but you could have other kind of assets in there all in the same chain code. And this is what happens when you actually invoke this Ethereum integration. So here's a chain code on fabric that we're specifying with an argument and a channel. And then we have the seller C extension that allows us to specify Ethereum request. This could be signed or unsigned. In this case, it's unsigned. So we're specifying all the parameters. And then you're specifying finality parameters as well. An isolation level and timeouts. So this will go ahead and run the chain code on fabric. It will run chain code, solidity chain code here on Ethereum that you're invoking. We specify the URL. In this case, it's in a Goryl test net, but whatever network you want to use. And then as a response, you basically get the transaction IDs in a committed state. This is on a fabric side, commit transaction ID. It was forced to prepare and then it was commit. And then the Ethereum response as well. And the transaction checks from the Ethereum side. And you can look it up in Easter scan as well and see that it has taken. Now, if this finality parameters do not result in the block being added within this time or number of blocks, et cetera, then we will do a rollback and you will see on the fabric side, the rollback as well. And this works with Ethereum. This works with EVMs like Polygon and so on. There's many interesting use cases that we have seen people explore. For example, you can do an NFT here on the fabric and use the ERC-20 to pay for it as a ERC-20 transfer or ETH transfer. Or most recently, for example, you can maintain an NFT here maybe for confidentiality reasons or other kind of IP protection. You want to do it here. But then somebody buys it and you want to provide greater liquidity on Ethereum side, EVM side. And so you could do essentially a burn operation here or lock operation. And then a try mint operation here, atomically, right? This ensures that the token either arrives because it's minted here. And by the way, you can transfer all of the token history from fabric side onto the EVM side or Ethereum side. But if for some reason this fails, then the rollback will ensure the token remains active and available on the fabric side as well. So, you can use tokens on Oracle blockchain to track public chain token balances as well. So you can have essentially a bookkeeping token account here for variety of cryptocurrencies that some banks have tried to do as well. You could have a public hash for confidential transaction that's down on the right-hand side. You can publish a public hash or some kind of a data that does not disclose the details of the transaction but allows the party to prove the validity of the transaction as well. You could use it with standard tools like remix IDE on Ethereum side. You can import existing smart contracts or deploy, create new ones, invoke them. Essentially, the ways that we operate, this is something a little bit different, right? So we actually allow you on Oracle blockchain, which is topology of fabric, to run EVMCC, which is EVM chain codes that emulates Ethereum mutual machine and allows you to run solidity chain codes inside, expose them through the fab3 providers. This is something that some customers beginning to use. Fab3 is actually a provider that talks about the fabric in one side to the EVM chain code and here exposes JSON RPCs that allow you to interact with standard web3 tooling like remix IDE and so on. We also expanded this to support the rest APIs to invoke solidity chain codes on EVM. So this combination, essentially, of the availability of the EVM and I'll mention authentically that I'm really glad to see the reappearance of EVM in fabric environments supported through the new hyperledge lab project, rather, because this thing is going to be in an important technology to allow folks who build stuff on solidity to leverage other blockchains underneath. And then, like that exposed through the fab3 provider, JSON RPC APIs for wallets and other dapps. So a little bit on the use cases, right? I mentioned that we've done a lot over the last number of years in financial services and retail, manufacturing and supply chain logistics and global trade and increasingly web3 and NFTs. And we're beginning to see a number of those actually start leveraging tokenization chain codes, which is coming back into web3 world, right? Whether it's digital currency, renewable energy certificates, which is a project we're currently doing, rewards programs, micro payments in freight services, automation platform, data assets for utilization for trading, et cetera. And I'll show some examples. This is a ticketing example, a partner of ours built in Italy, Ticketcoin, where they basically create tickets by using our platform, combining fungible, non-fungible tokens. And then those tickets can be verified and so on. This is our CBDC sandbox. So it basically contains the blockchain nodes, right, which is this hyperledge fabric nodes, as well as some tooling for the application side of it, integration tooling, database analytics for monitoring and so on. And then we've generated our tokenization layer. We have APIs and then we have this application that provides CBDC capabilities for wholesale, CBDC and also APIs for retail CBDC use cases. And we're beginning to see interest in commercial banks as well for leveraging this, not just relying on central banks, but tokenized deposits or if you will, bank-based stable coins, things like that. I wanted to mention NFT use case as well. We've worked with oneoff.com recently to help launch rewards by Warner Music Group, WMJ rewards. This is essentially a one-off based enterprise-grade software suite that supports NFT marketplace across multiple chains. So this is deployed across our blockchain platform, which is fabric together with Polygon and Tezos in a hybrid environment using another hyperledge project, Firefly, to orchestrate. And then they provide the NFT marketplace that allows basically music lovers that have membership with WMJ rewards to earn tokens, digital budgets, participate in challenges, and then redeem those rewards for specific gift cards, VIP tickets to show concerts and shows and so on. So this is one of the stronger examples in music NFTs. Another partner called LifePlex that's also doing hybrid blockchain support with hyperledge fabric, Solana, Polygon, and they provide the Web3 generation capabilities. That's interesting because it not only does basic NFT support, but it's in reach with gamification and immersion capabilities. So they can actually generate in a metaverse like virtual worlds for use cases ranging from rewards programs, HR onboarding, training, and so on. So this is a very powerful combination. This is an NFT marketplace that's being built by a partner called Tweedox that supports essentially non-traditional investments where there is a network of companies that use a blockchain network to share their KPIs, production KPIs, and then essentially this data goes in on the net and the ledger used by NFT generators to create specific NFTs based on the company results. And then we have a trading platform associated with that that allows for those NFTs to be traded. So this is an interesting kind of alternate investment use case. A quick question here that I see using blockchain to empower serverless videoconferencing. It's an interesting idea. I don't think I've come across one specifically, but we could certainly follow up and discuss Marshall. There are some capabilities there that we could help us. Product tokenization. I think that's another important area. We're beginning to see a strong interest in leveraging tokens in tracking product components, ingredients, inventory, things like that. And we have some customer examples. This is in textile industry where they have a number of companies that make things from the chemical ingredients they provide, fibers, yarns, fabrics, garments, et cetera, and the traceability is done using our blockchain platforms that allows them to drill down in very granular fashion to see for particular garment what all of the sub-ingredients it's made from and then track, you know, the entire inventory and then there is royalties because it's a certified materials as well to being tracked and dependencies across companies and ingredients from this data. In government cases, we've done a pilot implementation for grants program. So this is basically granting of funds to multiple levels, right? So sometimes you have grant letters to a particular institution, maybe, you know, universities often, and then they also do sub-grants from that. And so tracking, particularly sub-grants, is very complex and a lot of it, I mean, takes a lot of time. I think there was an IBM study that said that in sort of a government granting situations to academia, researchers can spend up to 40% of their time on paperwork, tracking, you know, the expenses and where the money went and all of that stuff. So we combined an NFT token for the grant letter with fungible tokens to actually manage the financial, you know, the actual currency amounts and allow this to be, you know, sub-granted, right? So you have a grant and then you can have a sub-grant and you can track all of the expenses reported against the grant amounts based on categories and so on. And, you know, we think this is going to be quite, you know, quite important because there is, you know, so much of, at least in U.S. government, funding is spent through grants. And a few minutes on the centralized identities. This is a more recent trend in terms of kind of use that we've seen in, you know, enterprises and government and so on. So the centralized identity also often referred to as a self sovereign identity. It's a standard framework based on the concept of digital identifiers and verifiable credentials, right? So it allows users to take control back, users get to decide what information they're going to disclose. They have verified credentials which consist of multiple claims potentially and they can pick and choose which claims they're going to present. Because that user information sits in a wallet, it doesn't sit in some centralized IT system, there's nothing to hack, right? Companies are spending enormous amount of effort and funds to secure their internal systems, particularly identity management system, because, you know, you go everywhere, you have to create an account and a bank account, insurance company, you know, healthcare system account, all of those are maintained, managed by their own internal systems. And that means that those can be, you know, great attractions, you know, great targets for people who want to hack those identity systems. And a lot of effort and money goes into securing them. When the information is not in those systems, but in the wallets, very decentralized, there's nothing to hack. So that, you know, I think great benefit. This transparency, because the users in control of who they're sharing with, they can see the track of, you know, who they shared the data with, there is interoperability as well, because there are standard kind of a schemas defined on a blockchain registry, typically, and data formats that can be used. There's also benefits to actual enterprises that are using them, right? Fast verification process, they don't have to spend as much time and energy, verifying the credentials that helps to reduce the fraud, improve security of data and identity using PKI, and reduces the risk of being targeted for cyber breach, right? And a lot less compliance efforts as well, right? Because increasingly, there's a lot of compliance requirements around identity management, you know, California rules, GDPR, et cetera. So this is from verified credentials, WS3 orgs, there is a lot of examples of where verifiable credentials can be used. It's based on what's called a trust triangle, where you have essentially a holder that acquires and stores credentials for the register with the register using DID, then they can request credentials. There is an issue which is second leg of a triangle that issues those credentials. They can verify the identifier of the holder before they do that. Of course, they only identify it on the registry. Then the holder has those verified credentials in their wallet, and they can send a presentation of those credentials, one or more claims from one or more credentials to a verifier, sometimes known as a relying party. And they can then use the signatures because those presentations are signed by the holder saying, yes, this is my credential. And inside, of course, the signature of the issuer saying, yes, I issued it. And all of those verifiable with the register, right? Because boschemas and DIDs are maintained on the registry. So this is kind of the triangle. We have actually implemented on Hyperledger Fabric the mechanism to support this, right? So we've created essentially DID management chain codes as application chain codes to create and update DIDs and check the holder's DID. And then we have a mechanism which has custom issue holder verifier functions. And this allows for verified credentials to be requested. For example, from holder to the issuer, the issuer can check the holder's ID, prepare verified credentials. They will obviously check with the internal systems to ensure that they can issue that credentials that the person has passed whatever qualifications are required or presented as a document and so on. That's kind of off-chain process. But once credentials are issued, then they return to the holder's wallet. And then the holder can prepare a presentation, send it to the verifier. Verifier can then validate that issue and hold the DIDs that I mentioned earlier by retrieving public keys and signatures. And then return the acceptance status and the credentials can then be used whether it's in person, mobile QR codes scan or some kind of application where you gain access to something. Hey, Mark, I'm sorry to interrupt. This is David. I just want to flag that we have the room for just an hour. And with the hour coming up, we have about five more minutes. So just wanted to give people heads up. I think maybe if people have questions that there's not time for, maybe I can drop your LinkedIn profile link in the chat and then encourage people to reach out to you there and then to flag. If people are dialing in for the next call starting in just four minutes, just hang tight. We're going to be wrapping this up in about four minutes. So I'll drop your LinkedIn profile. Yeah, I'll just drop in two minutes and maybe take a few questions if there's any. If you can, it's the last five minutes here. So I just want to flag a couple examples here of verified credentials. This is in government. Utah recently issued an RFP for a pilot program. Rhode Island had a pilot program earlier this year. There is a new RFI from Customs and Water Protection CBP. That's been actually quite interesting. It's talking about automated commercial environment, which is a system that manages trillions of dollars of goods coming and going out of US and into US through customs. And they have specific DAD verified credentials focus in there, looking to identify legitimate taxes through DAD framework, verify trade document claims. In W3C standards on verified credentials, there is actually a set of documents that have been provided based on the CBP standard forms for trading and for custom forms and so on. And there is a request from CBP on whether this can be in RFI. It handles through the verified credential implementation. So this is quite an interesting data. And we think there's going to be some future work around this ASIC system to leverage DAD and VCs potentially. So just to summarize, I think Webster Technologies certainly have significant value. They are going to be appearing on many chains and not limited to particular chains where they have originated. But their adoption depends on having an enterprise-focused blockchain infrastructure. I think that's important. And having enterprise blockchain provide access to those Webster Technologies for cross-ledged interoperability, asset portability, governance mechanisms, and centralized identity mechanisms I think are going to be important for this kind of a hybrid world to emerge where Webster Technologies are permeating across all sorts of chains. There's a number of other hyperlogy projects. I talked about Fabric a lot, but there are others I wanted you to know about to explore. And you can go visit Oracle Block for additional materials here. Oracle Solution Playbook and also your architecture center about NFT marketplaces. We have a bunch of really interesting stuff there. And you can subscribe for a trial as well. Visit our blogs, visit our online pages, oracle.com.blogchain is your entry point. So all of that's available. And happy to follow up if you want to reach out on LinkedIn or take a couple of questions here. Any questions from folks here? Yes. Hi, Michael. Yeah, hi. So this is Michael from Chicago. Hey, how are you? I'm good. Good. So you have a fantastic talk. And then you have a share with some great use cases in a later part. And then I'm very interested in the building blocks. That's key for the framework of Web3. And then would you talk a little bit more about how those use cases resonate with the key building blocks you introduce in the first section? Thank you. So that's going to help to showcase the value of the building blocks you introduced. Thank you. Yeah, absolutely. Thanks. So as I mentioned, for tokenization, I mentioned a few examples. One of.com for music NFTs is using our building blocks. We have examples where there are customers that are using wallets for micropayments. We're doing work in CBDC space as well. Some of those are confidential. We cannot, you know, customers sometimes don't want to disclose which vendors are using. So we have to keep some things confidential. But we also have, you know, examples in loyalty programs that are confidential. But we are trying to share at least anonymously without naming the customer. You know, some of those use cases. So, you know, this presentation has a few. But if you want to reach out to me on LinkedIn, I can probably provide a few more. And we actually have, there's going to be some recording from an Oracle conference next week, Oracle Cloud World, where we'll be able to share additional ones as well. Great. Well, thanks for that, Mark. And thanks for the question. Sorry that we don't have more time for other questions. But as Mark said, he's happy to have you reach out to him on LinkedIn. I just dropped a link, his LinkedIn profile link in the chat. So please do that. And Mark, thanks for your time. I can send the recording and the slides around to everybody who signed up. So you'll have the resources and thanks for joining us today. Thank you, everybody. Thanks David. And then Brett, you are set as a co-host so you can run the rest of your call. Thank you very much, David.