 minding. Yeah. Yeah. Go ahead. All right. Yeah. Thanks. Kamlesh and thanks everyone for joining this session. So I'm Ashok Govindan as Kamlesh already introduced. I'm the co-founder of SpyDRA. And before SpyDRA, a quick introduction about myself. So before SpyDRA, I used to work for almost 16 years with Microsoft, mostly focused on the cloud technologies and security identity and eventually blockchain. And I helped a lot of customers around the globe adopt various cloud-skilled technologies and build solutions on top of it for a long time. So as we all know, right, there is a lot of use cases in any business or traditional enterprise space where blockchain can help, right? There are multiple parties or organizations in this context that are involved in a business process and blockchain is one of the way where, you know, some of those business processes can be streamlined and data can be shared transparently with all the goodness of blockchain, right, that we all understand. But in today's world, right, it's a bit, if you look at any organization that wants to adopt blockchain and do something with it, there's a lot of friction as such, right? And organizations find it difficult to move from traditional Web 2 technologies that they understand very well to something like blockchain, right? And that's where most of, that's where we are focused on as a company. So our mission fundamentally is to make the adoption of blockchain technologies very easy for enterprise and, you know, customers with organizations so that they can basically use and integrate with blockchain just like you would do with a regular database, for example, right? And not worry too much about how the technology works, don't have to, you know, fully understand the internals of how blockchain works and what it does and, you know, things like order or peer in a hyperledger fabric environment, for example, right? So that's where we have been working with a lot of customers to implement a lot of the blockchain use cases for various industries, right? And then what we found was that we are doing a lot of repetitive work, right? Right from deploying infrastructure. So because we are talking about the private or enterprise blockchain space, so there's always some infrastructure that you have to deploy that to its scale, right? And when multiple organizations are involved and when you have to actually scale your use case and onboard multiple participants, there's a lot of infrastructure definitely involved. So right from that to actually developing the solution on blockchain to integrating it with existing applications, there's a lot of things which which are not available out of the box, but at the same time, you know, those are repetitive kind of tasks that you have to do for every customer. So that's where, you know, based on our learnings, we came up with the asset tokenization platform, which is basically a platform that we provide to easily tokenize any online or offline physical assets on a blockchain and make it very easy for customers to do so. So our platform is currently fully built on Hyperledge of Fabric and basically covers, you know, different use cases across different industries, but more focused on the enterprise use cases or the enterprise side of blockchain at this point of time. So in today's session, right, what I want to do is to basically share some of those learnings, right, from working with multiple customers and basically talk about what are some of the things that repetitive things that we are trying to optimize or, you know, basically come up with a solution around it, a reusable kind of a framework and a platform around it, which makes that adoption easier, right? So what is asset tokenization, first of all, right? I'm sure you all know about it, but you know, just to, just to level set everyone, right? So asset tokenization is basically all about turning any asset, which is a value. Value could be actually, actual value or it could be intangible also, right? But turning that into a digital representation so that then you can do a lot of things around it, right? You can start tracking things. So, you know, a lot of the, in the supply chain use cases, you can start tracking things or you can start trading things after that, after doing that. So it could be physical objects, it could be, you know, intangible objects like, you know, intellectual property, it could be things like, you know, even invoices and things in the supply chain industry or financial industry. It could actually be real money also, right? Fiat currency or, you know, cryptocurrencies, CBDC, loyalty points, things like that, right? So anything which you want to have a digital representation and easily basically track or trade between multiple entities that are involved in a trustless manner, right? So that is what asset tokenization is all about. I would also like to delve a little bit on the, you know, when we talk about asset tokenization, typically what most of the conversation involves around is, you know, around NFTs and cryptocurrencies. Although that is where a lot of the asset tokenization use cases are today where, you know, you tokenize something and then basically start trading it, right? Like, for example, even if it's a real estate asset that we are talking about, once you tokenize it, then you will basically say, okay, I want to create some tokens out of it and then, you know, users or people can basically then buy those tokens and essentially by way of doing that own the real estate or, you know, fraction of it, depending upon whether you fractionize it or sell it as a whole and things like that, right? So most of the asset tokenization use cases today, one way or the other deals with, you know, either creating an NFT, a non-fungible token or a fungible token and then, you know, you start trading things, right? You start changing ownership, you start basically, basically start start owning it and trading things, right? So that's where most of the things happen. But not everything is about trading, right? When we talk about asset tokenization, like, you know, if you look at the supply chain industry, I might want to tokenize an asset, like let's say a shipment, right? Which contains certain goods or products and then that shipment moves between multiple organizations. There's a manufacturer who actually creates the product. Then it gets shipped by a logistics provider to a distributor who eventually then sells it to a retailer and then to the final customer. So here it's not really, you know, you tokenize that particular shipment and the product not to really trade it, right? But basically to start tracking it as such, right? So all the NFTs and cryptos are one of the big use cases when it comes to all the things that people normally do. Asset tokenization is not just about that as such, right? And of course, there are a lot of standards which even Kamlesh was mentioning, right? There's ERC-20 for fungible tokens, 721 for non-fungible, 115 for a standard which deals with both fungible and non-fungible tokens. Mostly these come from the Ethereum side of things, but, you know, they are just standards, right? So you can actually implement them in any blockchain as such. But when it comes to, you know, really scaling asset tokenization. Scaling means I'm not really talking about performance at this point of time, but basically using the concept of asset tokenization across industries for different kinds of needs, right? And basically really utilizing blockchain across industries, right? It's not even just about the standards, right? Because a lot of the use cases would require you to do things beyond these standards as well. Like for example, right? If I take the same, you know, example of a shipment that you tokenize in a blockchain, let's say you create an NFT, right? Which represents the actual shipment. Now, as part of the ERC-721 or 115 standards, there will be a certain set of methods that you'll have to implement. Like for example, you'll have to say, okay, you know, how a single transfer or safe transfer from what is the balance. So there are methods for that, right? But then, you know, just by implementing those methods, maybe you won't be able to do everything. For example, right? What if I need to find out all the shipments that have been delayed, right? There is no out-of-the-box or, you know, there is no method defined in any standard, which will let you query something like that, right? Which is a very generic query, if I may call it that way, right? So think about it like this, right? Blockchain is sort of like a decentralized database, in a way, right? You may have to call it decentralized database. In a typical database system, once you add a record into the system, then you can start querying and do a lot of things with that, with a lot of flexibility. Unfortunately, when we talk about blockchain, that's not, it's not, you know, as flexible as a traditional database, right? So once you start creating assets in the blockchain, there are limited things that you can do with it, right? You can execute certain functions. If you want to go beyond that, then you'll have to start rolling your own things, right? You have to start looking at going above and beyond these standards and then start doing things your own way. So there's a good related presentation also on this, which just happened a couple of weeks ago, which in a similar, you know, hyperledger meetup, I believe in US, where Daniel Barbosa was talking about, you know, asset organization. It's really far more than NFTs and crypto, right? So today what I'll talk about is, you know, not the typical NFT and crypto use cases, which I believe has been talked about a lot, right? But what if you want to do asset organization and use asset organization and maybe, you know, solve other use cases like track and trace in a supply chain or maybe something in the fintech space or insurance space where you have to participate, collaborate with multiple participants and do things like supply chain financing or invoice discounting. So these kinds of things, right? So I was talking about what asset organization is fundamentally, right? But what is, what can you actually do with it, right? There are a lot of things that you can do with it or a lot of things that it does really, you can be, it brings in transparency, which obviously we all know is what blockchain really stands for. So it makes the same set of data available to different participants and that itself basically unlocks a lot of use cases, right? It can bring in efficiency across systems that are owned by multiple participants. So the moment you enable this information flow and the single source of truth where, you know, instead of having different disparate information systems and data that is stored in different systems, once you have a single source of truth, that information can be accessed by multiple participants and systems that are owned by multiple participants and that can actually bring in operational efficiencies and even eventually cost savings because of that. And, you know, we can do things like do a lot of automation in the blockchain itself via smart contracts, which can basically use that data and then execute some business processes automatically rather than, you know, a lot of the manual business processes that happen today. And then, of course, there's the, you know, trading and fractionalization part of it where you can convert real-world assets into tokens and then you can start trading them, you can start changing the ownership of them or assigning the ownership of them and things like that, which makes that, which makes illiquid assets more liquid and accessible to folks at large. So at a high level, right, what goes into a successful asset organization solution? I would say there are three important things, right? One is, and specifically as we are talking about, you know, the private or the enterprise blockchain side of things, right? The first step is obviously having an infrastructure built up among all the participants in the network, right? Which is definitely one of the things that you have to do. And it's not just about setting up the infrastructure but also managing it over a period of time, right? And then once you have the infrastructure, you need to start basically developing smart contracts, which is basically literally code, right, which runs in the blockchain. And then once you have the infrastructure and the smart contracts built, of course, blockchain cannot really exist by itself, right? The real value comes when blockchain, when other applications, applications that are there in a customer's or organization's ecosystem already, they can be integrated with blockchain and blockchain can be truly integrated into existing business processes, right? That's in the true value of it comes. So that's the last thing, which is integrating applications into existing ecosystem, right? So let's start talking about all of these one by one, right? So when we are talking about managing infrastructure, right? There's the automation part of it, right? And we believe truly that, you know, infrastructure can be managed at scale and in a long run, only through automation. A lot of organizations and teams start with, you know, deploying, for example, Hyperlegia Fabric manually, right? And then the problems start emerging. Initially, you know, just to get a very small network up and running is probably very easy. You can also use a test network and, you know, it'll be done in five minutes, right? Or a couple of minutes. But then the real challenges start coming when you have to onboard multiple organizations. Those organizations can really be, you know, distributed across different geographies. Everybody has their own, could we have their own cloud, could have their own on-premises, where they want their nodes to be hosted, so on and so forth, right? And then of course it could be, and specifically now I'm coming to Hyperlegia Fabric and, you know, most of the rest of the talk I'll be focused more on how to do all of this in Hyperlegia Fabric, right? So I'll be using some of the specific Hyperlegia Fabric technologies. So when it comes to Hyperlegia Fabric, right? You can create multiple channels. You can have different organizations participating in those channels. There could be multiple nodes. You can have chain codes, different versions of chain codes. You can upgrade a chain code, lot of those things, right? So all of this, you know, eventually requires some sort of automation, right? So I think, you know, whenever we are talking about doing something in asset organization at scale, having that a solution which basically automates a lot of the infrastructure side of things in terms of deploying and managing is very important. And also, you know, there's a lot of key material that is used, right? So there are keys, there are certificates, even the nodes in a Hyperlegia Fabric infrastructure requires certificates or user certificates, right? And then in the long run, even if your provision certificates in the first place, they will expire after some time, right? So you'll have to start renewing them. So there's a lot of automation that goes into it. You need to figure out where to store those certificates securely. What we are seeing is that a lot of customers who deploy Hyperlegia Fabric follow the test network and then the certificates are stored in a file system somewhere, which is not the right way to do that, right? Certificates are sensitive, okay? Whoever gets access to certificates can really compromise the entire system, right? So probably you would rather store it in a secure key store like a vault, right? A hash bar vault or Azure Key Vault or any equivalent kind of technologies right out there. And then, of course, you know, as I said, the customer's environment can span across and everybody needs control of their nodes while still being part of the same blockchain network. So that's where, you know, what we have done is basically we have automated a lot of this in our... So we started with automating this for our customers that we have been working with and then eventually, you know, brought it into a platform that now customers can use directly. So I'll show you that, but before that, you know, I'll talk about how we have gone about... Yeah, until we lost the hash bar or... Yeah, we can't hear anything. Yeah, hash bar will be lost to you. Maybe some network issue. You can wait for some time. Yeah, I think it dropped out. Maybe they lost network. Just wait. Yeah, he's just joining back. He just joined. Hello, everyone. Sorry about that. Network issue and, you know, it always happens when you're presenting or doing a demo. So it always goes wrong. So, okay, sorry about that. So let me share my screen. Okay, I hope you can see my screen. Yeah, yeah, we can see. Yeah, okay. Yeah, so basically I was talking about the automation, right? Automation of the infrastructure. So the way that we had done the automation is primarily by using Hyperledge Bevel, right? Where we basically have a central control plane kind of where, you know, users can come in and then... I'll show you that. But then once you perform network operations on the console, we basically use Jenkins to schedule the automation and then which internally uses Hyperledge Bevel. And eventually, you know, the network is managed through that. So although we have used Hyperledge Bevel as such, we had to do some modifications to it because Bevel is more general purpose, right? Which deals with different blockchain networks, but we specifically deal with Hyperledge Fabric and then in a specific way, right? Where we want to provision multiple organizations, for example, together or multiple nodes and so on and so forth. So we had to do some optimizations in terms of performance and, you know, the type taken to do all of that. So we had done some parallelization rather than sequentially operating things and things like that. And eventually, you know, basically using that, we basically managed the network. So I quickly show you how we do that in our platform. So let me switch to the platform. So you can actually, you can also go to spider.app and then you can sign up to our platform. And once you sign up, you know, you get a certain set of free credits. So you get almost 400 credits that you can use to, use to try out the platform as such. So once you sign up, right, this is the kind of review that you will get. And on the platform, as you can see, right, you can create organizations, networks and applications. So network is basically the blockchain network. But as you all know before, for a blockchain network, you need to, the multiple participants in a enterprise or a private blockchain network are organizations. So you create organizations first. So creating organization is nothing, you know, it's pretty simple. You just provide the name and a few other details, which I'll not go into. What I'll focus more is in the network part, right? So we have tried to make it a little bit more simpler. As you can see, as you probably know, right, in Hyperlegia Fabric, there are a lot of things like order POS and then there are a lot of options that you can configure, right? But basically, as a customer, right, you may not need to configure all of those options up front. So we have picked the most important things which are meaningful for any organization and any use case and basically expose those as options to start with. Of course, you can customize things as you go along and change things, right? So for example, when you create a network, basically you select an organization as the organization that is sort of creating the network and then you can invite other organizations also to be part of the network. I'll just give a name, so this is pretty simple. But then most of the options or the interesting things happen in the configuration screen, right? We provide an option of creating a network in a shared environment or a dedicated. The fundamental difference is in a dedicated environment, there's a lot more isolation completely at the infrastructure level where the servers that host the nodes or the Kubernetes clusters that host the nodes and even the network through which everything flows, right? So dedicated virtual private networks and things like that. As a customer, you can select a cloud provider. So we support AWS currently and we also will be supporting Azure very soon. We support multiple cloud regions. So this is our test environment, so you only see a couple but we support multiple regions across AWS. And then there are built-in configurations that you can directly deploy. Like I can say that if I want to support like around 20 requests per second for a proof of concept then I'll create a smaller network and there are some pre-configured settings which apply, right? So this is what I was saying instead of going and individually saying, okay, I want to have this many nodes, this many size, these are the settings, these are the endorsement policies, these are so and so forth, right? You can basically select a pre-configured configuration and then deploy it as such. There is an advanced mode also where we can basically tweak a lot of those settings as well. So that's pretty much it, right? As you can see, once you do that, the network gets sort of created or start, oops, did I do something wrong? Okay, I think I have a little bit of problem with my internet. This connection is not stable. So what I'll do is let me go back and show you an actual network. I think it actually got created but maybe the network is switching on and off. So that's pretty much it, right? It got created and then things start happening behind the scenes where the actual automation starts kicking in. So if I look at one of the existing networks that we have created, so you can see that once you create a network, there are, you can actually add other organizations. So either you can add organizations that you yourself own, so I can create multiple organizations as an administrative and then add them to the blockchain network. That's one way of doing it. Or I can invite someone from a different organization, right? By providing an email address and basically inviting them, right? You can also select the level of permissions or level of access in general that the second organization will get to the same network that you are inviting. So you can say that this other organization is a network admin, which means they get equal rights and exactly the same kind of rights on the network. So here basically we are talking about other kind of endorsement policies that are applied and whether the other organization is a network admin right. So they can literally administer the network completely. They can also deploy order nodes into the network. While if you're a network contributor, right, then you cannot, for example, deploy order nodes and be part of the ordering process. And similarly, if you're a network contributor, you cannot invite other organizations. So basically you cannot decide who else gets to be part of the network and so on and so forth, right? So basically this is sort of mirroring the hyperledger fabrics ACL itself and how things work within ACL, right? But instead of exposing the raw ACLs and endorsement policies, we have bundled them into roles which basically provide certain pre-built settings out of the box and those settings are applied to the invited organization. So basically that's how you can be and you can form a consortium or a network with multiple participants and do not worry about actual deployment of the infrastructure and the configurations behind the scenes. And then of course, once you have an infrastructure, you can start doing more granular configurations like you can create channels. You can basically add or modify the existing nodes. You can start adding applications which are nothing but chain code. So we basically provide a pre-configured application also which I'll come to in the next set of slides. But essentially you can also bring your own application as in your own chain code. So we support Node.js and Golang at this time so you can create the application and once you create an application, you can add different versions to the application and then basically you can deploy an application on a particular channel and things like that. So the typical chain code lifecycle operations you can do and all the other typical operations that you would do on a fabric network, right? Hyperledge Fabric Network. So that's the first part, right? Which is more about automating the infrastructure side of things also, which we believe is fundamental to running any blockchain network and basically productionizing it and running it at scale. There are, you'll have to monitor the network, you'll have to look at statistics for the network, you'll know things like that, right? It's a lot of, and if there's something wrong, you need to get alerted and a lot of things like that, right? So you need a platform which does all of that and the intention of designing our platform also or creating our platform was to do that itself, right? But then that's not where things... That's not everything, right? Once you have an infrastructure, right? The question is then what, right? The second step is all about developing smart contracts. Now, of course, you can develop smart contracts, you can start writing code in Golang, Node.js, specifically when it comes to Hyperledge Fabric or Java, whatever language you're comfortable with. But then, you know, let's take a step back to asset organization again, right? And basically what is an asset? So there's a lot of different terminology that folks use, right? Of course, NFTs and fungible tokens are definitely assets which everyone is familiar with. But then, you know, NFTs today is mostly used for, you know, creating a storage in an NFT, really. So if you look at it, it's really an object with a unique identifier, right? Where one token is not the same as a separate, as a different token. So there is something unique between these two. So if the NFT is that of a painting, for example, painting number one and painting number two has something unique which makes them different, right? So think of it like, if you think of it at a fundamental level, it's an object with a unique identifier or a unique property, right? Is what an NFT. Folks talk about dynamic NFT, which is more about saying that, okay, you know, NFT doesn't have to be constrained to only, you know, something with a URL and an image, right? Where the properties of the NFT is hosted or how the image looks like or a video or, you know, actual, some object of the actual NFT, right? It can have its own properties, right? So in a traditional sense, anything, right? A real estate, which has a particular ID, a name, address, locality is an NFT because it has a unique ID and it describes something about the residential property itself. Or it could be an invoice, right? Which again has an ID, it has some properties, right? So folks sometimes refer to this as dynamic NFT. But it's all asset, right? So we mostly refer to it as an asset because token, at least to me, sounds like more like something, you know, which is something that you normally use for trading, right? And that's where I want to bring out the distinction that not everything is about trading. Asset tokenization is all about creating a digital representation of that asset, which you can do in any number of ways, right? Now, what are some of the challenges, right? When we talk about asset tokenization or creating the digital representation. So in any real-world use case, right? There could be multiple types of assets. And so let's talk about the use case, right? Let's say, and this is an actual example that we are a real project that we did with the hospital, big hospital chain and insurance providers. So the whole problem that we are trying to solve was around insurance and claim settlement, right? In the insurance, in the healthcare industry. So claim settlement process, typically, you probably have experienced it yourself. It takes a long time. There are a lot of things to look at. There's a lot of back and forth that happens between the customer, the hospital. There's an insurance provider and this normally a third-party administrator, right? A TPA. And this is actually a very right use case for blockchain because there are multiple parties involved. And there is some information that is about a particular diagnosis and something that was, you know, related to a hospital visit that needs to be shared between all of these parties in a transparent manner based on which certain decisions have to be made and the claim settlement has to be done, right? So in this kind of a use case, right? There is certain information about the patient, the insurance, the diagnosis that happened on in the, and the procedures that happened in the hospital that needs to be shared, right? So if you look at this kind of a use case, right? And if I look at, there are some standards which deals with this kind of patient information as well. So that's something called as FHIR, which is the standard which is used primarily by the US but also, you know, other countries are also getting on boarded to this. FHIR standard is all about how do you represent patient-related information, patient and healthcare-related information in a standard way. So that different participants can basically consume the same information easily, right? So as you can see right here, there are almost 150 different types of objects, right? So ranging from let's say an observation which is basically a diagnosis that happens. There are documents or diagnostic reports that are created. There is definitely, you know, patient. It's kind of difficult to find in this, yeah. So yeah, there's a specific schema for patient, a specific scheme for insurance, for example. So insurance plan is here when you are doing a claim settlement, how a claim form should look like, how this should look like in pricing, payments, right? So there's a lot of schemas which are already defined. And literally, if you're talking about representing all of this in the blockchain, now of course, everything need not go into the blockchain, but at least a lot of the information needs to go into the blockchain if we are to really solve the insurance claim settlement use case in the healthcare industry. So this is the kind of assets that we are talking about that will go into the blockchain, right? So now if you are to really, if you are to really, I'm getting messages that the network connection is unstable, I'm just hoping that you can hear me. Folks, can you hear me properly? Yes. Yeah, yeah. Okay, okay, sorry, yeah. Okay, so yeah, so what I was saying was that these are the kind of assets that need to go into the blockchain, right? So that's where mostly what, and mostly then in today's world, right? You have to start writing code to do all of that, right? Unlike the database in Apple just fabricated not even in any other blockchain, there is no concept of a table or a collection or whatever you call it. You can't directly define that, but there is no easy way to just carry and create assets out of the box, right? You have to start writing code for everything and then once you start putting all this information in, there's no easy way or flexible way to query things and get out of it, right? And also there's a lot of things that now has to happen like for example, patient report can only be created by a hospital, cannot be created by the insurance provider, for example, right? Insurance policy can be created only by the insurance provider, but not by the patient and so on and so on, or the hospital and so on and so forth, right? So then you have to start defining permissions and all of that, right? Of course, you can write chain code to do all of that, but there's a lot of complexity that comes into it, right? So this is kind of an asset model. This is a very simplified asset model. We have come up with just for this demo. Let's say there's a patient, right? And patient visits a hospital. There's an insurance plan that the patient has. They perform, the doctor performs a diagnosis, which is an observation. Some procedures are done and then a claim is filed which needs to be settled, right? So if you can see, this is an asset model and there are references that point to each other, right? Like patient has policies, observation is for a patient which is stored in a subject, an adequate subject. There's a claim which then is created for a patient for a diagnosis for a certain set of procedures and there's an insurance that needs to be used, right? To settle the claim. So now, how do you do all of that, right? In the blockchain and that's where our second part of the solution comes in, which is all about the built-in application that we provide that is called as asset tokenization. So the intent of the asset tokenization solution is basically to provide, so let me go back. Sorry, my internet connection is very stuck today. So let me go to, yeah. So if I go to deployed applications, right? So, yeah. So this is the asset tokenization solution that I've already deployed. So if I go to the asset tokenization solution, there are a few settings that I'll show you, right? So basically if I go to the settings, right? What we have provided is a way to, just like I was saying, right? Similar to a database, right? We have provided a way to create asset types. Think of this like creating tables, right? So you can basically create multiple tables, but you don't have to provide a lot of information unlike a table where you have to provide a lot of columns that belong to a table. And if I come back, related this back to the insurance settlement use case, the hospital might already be using a system to manage the patient records and the health information, right? So they have already defined all of that in their existing system. So you don't want them to define all of that again in the blockchain as such, right? So all that we are saying is that we define a key and LSD what is the name of the set, right? And then the second thing that we allow customers to do is to basically define the references. Like for example, if I look at the most complex reference here, it's the claim which has a field called patient that points to a patient, which means this is like foreign key references in our database, right? Where a claim has information of which patient it belongs to and which field it belongs, which diagnosis or observation this claim is being settled against and which procedure and which insurance needs to be used, right? So things like that. And then you can also define permissions, right? Like in this case, we are saying that the hospital can actually create earlier update and delete the patient reports. They can do everything with observation procedures, but insurance plan, they can only read because insurance plan is actually created by the insurer, right? And there is a hospital, sorry, the third party administrator who can also read a lot of this information because they are in the middle of facilitating the claim settlement process. So you do all of that and then you deploy the application. And what you get after this, right? Is a set of REST APIs and GraphQL APIs. So this is where, you know, the third step, right? Once you, so what this does, right? Once you create the application and the settings is it basically deploys a smart contract behind the scenes, right? And once a smart contract is deployed, the next step obviously is to be, as I was saying was is to integrate your existing applications into the blockchain. So of course, Hyperlegia Fabric itself provides a GRPC interface and basically you can actually integrate with it. And you can use certificates and all that for signing the transactions and all of that, right? But that's a bit difficult to use first of all, right? Even if you're using your custom application, but then what if we are talking about integrating into an existing ERP that a customer has, right? For example, in supply chain industry, many customers would have SAP or NMX and things like that, right? So integrating those systems directly in the blockchain is where, you know, more of a REST API interface is more meaningful. And that's what we generate by doing that, right? So of course, there are a lot of operations where you can use to create, get, update, delete assets, right? But what we also provide is a little bit more rich way of doing things. Like when you get an asset, I'll talk about references and resolving that. We also provide ways for changing ownership. We also provide advanced operations on changing ownership. Like instead of directly changing ownership, somebody can request for change of ownership and then the ownership gets changed and things like that. So really diving into a few, I'll show you how a few of these things work. So basically, if you look at what I'll do is I'll take the asset, say this case of the insurance industry that I was talking about. So let's say, you know, these are the different objects that have been created on the blockchain, right? So I'll not go into the creation part, but I'll talk about more on the querying part of it, right? Which is where we have done some work. And we believe that, sorry about that. Okay. So where we believe that, you know, there's a lot of opportunity for improvement, right? And where the real value comes in. So basically, if you look at this, right? This is basically a claim, right? So a claim has, as you can see, it's an extensive JSON structure. So the way that we have modeled our platform is that anybody can basically, you know, create an asset using the REST APIs and only mandatory field is the primary key that has been defined, right? Everything else is sort of optional, right? As in, or, you know, extensible. So you can bring in your own JSON structure all the way as you want. And basically, this is completely extensible, right? So this is whatever exists in the existing system. And this is based on FHIR standard. So you can see that there's a lot of attributes that belong to a claim, right? But fundamentally, if you see, claim belongs to, has details about a patient, details about an insurance, and these themselves are different assets in their own right. Right? So what we have basically done is that when we get a claim, right? So let's say I'm getting this claim. So at that time, right? What happens is, if you see the result, right? When I created a claim, right? All that it has is, it says that it belongs to this particular patient, right? And this is the diagnosis and the diagnosis ID or the observation ID. But if I look at the get part of it, when I get the same claim within diagnosis, this is a diagnosis ID, but we automatically expand the observation, right? With the actual data from the observation. So why do we do that? Wearing the blockchain is basically not a very easy, it's not as performant as a regular database, right? So if you have to do multiple queries, it slows down the system a bit. So we have developed a system where you can actually get an asset with all the referenced information. So for example, if I look at a more complex case here, there is a procedure, right? That the patient went through. So the procedure has a part of, which basically points to an observation. So the observation itself is expanded and the observation actually has a subject which points to a patient. So the patient is fully expanded here and then there are policies that belong to a patient and the policies are also expanded. So you can get everything in one call basically. That's one thing which we have found very useful, the querying part of it, right? When you have to vary multiple objects and get it out of the system. Of course, you can get history about a claim, right? So we have APIs for that, which will give you the entire claim and the history of when it was created, when it was approved, for example, in this case, right? In this case, there are three records for the claim. It was created by this organization. So we add a lot of metadata automatically, which tells you a lot of information about who the owner is, who when it was created, updated, so on and so forth. It was created by this organization, which is the hospital. And then eventually it was approved. The claim status was approved by a different organization, which is a TPA in this case, right? What we also do provide, apart from the regular rest API interface, is a GraphQL interface. So basically GraphQL is a way of querying, is a very popular way of representing query kind of language for the rest or HTTP interface, right? So basically what we have done is we have done some engineering on top of Hyperledger Fabric. And specifically, the HTTP is the backend, right? So we basically support a GraphQL interface, where you can basically write GraphQL queries, which eventually gets transformed into CouchDB rich queries, and then the information is sent back. The way, so using this, right, you can actually write a query any assets in a much more rich fashion. For example, right, in this particular case, if you want to get all the claims that are pending, right, you can say that, okay, get me all the claims where approval status is pending and get me these attributes of that, right? So basically when it, there are four claims which are pending and these are the attributes of that, right? Or something more complex, right? You know, get me all the claim where there's a particular type of claim and the code is 831 or 832. So the code basically in this particular case tells you what kind of procedure was done, right? In this case, it says, hospital outpatient surgery performed, right? Something like that. So I want to get that kind of an information so you can see that I'm getting a complex query which does all of that. So that's what we have done with GraphQL, which basically, you know, and it's all about making that integration easier if you think about it, right? What it actually does, right? So that's the second, that's the other two parts where, you know, it's all about art, right? Smart practice itself. You get a framework where you can actually define and do things yourself. And then, you know, you can basically query stuff out and get stuff out in a very rich and rich and easy manner, right? So this is how GraphQL works. Basically, we convert GraphQL query into a couch to be rich query and then parse it and parse the response and give it back in a GraphQL format. So we have a GraphQL engine which does that. There's also a concept of event listeners where, you know, it's all about listening to events that happen in the blockchain and so that you can react to those events on your system, right? So we provide a way to listen to those events, have those events delivered to a webhook or a web socket, and then you can filter the events that you want to be delivered with, whether, you know, it's something got added, updated or approved, you know, things like that. And then your system can basically react to those events based on that. What we also provide is some additional integrations and we believe, you know, integration of the blockchain system with existing ecosystem or applications is really the key for adoption, right? And that's where we actually have gone beyond just exposing APIs but providing integrations which are really no code solutions which can directly integrate with the existing customer ecosystem. And the way that we have done it is by actually using some of the existing workflow automation platforms, if you are aware, like XAPR is there, Power Automate is there. So we have created connectors which can be, you know, used along with XAPR or Power Automate. And basically you can do something like, you know, once when something, when a record is added into SAP, a particular type of entity is added that can trigger a workflow in XAPR which will basically call the Spira APIs and create that asset in the blockchain. So you don't have to write any code for that or similarly, you know, even to the level of once when you add a record in a CSV or an Excel sheet then create a record or a bigger record on the blockchain or vice versa when something is created in the blockchain then that event gets sent to ZPR or Power Automate and then based on that you can put it into a database for example and things like that. All of that without any coding required as such. And we believe, you know, this kind of integration is what will make it very easy for blockchain to be adopted in typical enterprise use cases. Of course, you know, you can also write your own code as I was showing, but some of the innovations that we have done in that space is even with your own custom chain code, you get very similar functionalities. You can invoke or query your custom chain code methods using a REST API. You can actually query using GraphQL as well and you can add the event listeners or use the listener functionality with your own chain code as well. Last but not the least, what we have also done is, you know, if you're anywhere using your own custom chain code or writing your own custom chain code, there is no easy way to debug code from an IDE currently like from a Visual Studio code or any other IDE that you're using. So we have actually published a VS Code extension which makes it easy for debugging applications right from within Visual Studio code. So the way that works is, right, you just have to install the extension. You basically provide some configurations to say that this is the debugger that you want to invoke and basically just, you know, start debugging the code right from within Visual Studio code and then, you know, also submit requests. So you can invoke methods in your chain code right from within Visual Studio code. You can invoke a transaction or query, send a query and then you can get that results. And the debugger, you can, you know, create breakpoints within the debugger and the debugger will be, the breakpoints will be hit and you can do line by line debugging inspect the variables and all of that, right? So yeah, so that's what we have, you know, we have done over the period and then what we have basically, you know, realized that how, you know, some of the things that should happen for enterprise blockchain solutions to be adopted at scale across various use cases and, you know, some of the learnings that we had over the period of years, right, based on which we have made this platform. So feel free to, you know, look around visit spider.app and try out the platform and, you know, see how useful it is and if there's any feedback, we are more than happy to listen to it and hope that the session was useful. Thanks, thanks everyone for joining. If there are any questions, I think I didn't get a chance to look at the chat, but if there are any questions, I can take that. Feel free to stay back, you know, whoever wants to have any questions or if you want to ask something, feel free to unmute and ask. Yeah, thank you for that great presentation. I have a general question for the audience. Mostly companies are doing tokenization on any kind of public blockchain. So what motivates and inspiration to do on a private or hyper-ledge fabricated blockchain? I know, but I want to get the answer for the other people. Sure, sure. So I think it really all depends on, you know, what you're trying to do, right? If there are a lot of use cases, you know, where there are the data that you are with the assets that you want to tokenize, you don't necessarily don't want to put it in a public blockchain. Like if I talk about an asset, sorry, a supply chain use case, for example, right? Then there's a lot of data about the shipment, the product and things like that, right? Which you want to do a track and trace across different participants. So that's probably not a use case where you would go to a public chain, for example, right? Or, you know, in the insurance or the inverse discounting or supply chain finance kind of use cases, right? Where the collaboration is between different, not really between end users who are directly interacting with the blockchain, right? But between organizations who are interacting with each other and there's a business process going on between organizations and data exchange is happening, right? So those are really use cases which where private or enterprise blockchain really shines and probably the right model also, right? Because you don't want that information to be shared between everyone in the world. You need more access control in it and more privacy within it. Yeah, sir, I agree. So for other, like even if you lead nowadays or maybe go to any Web 3 and blockchain events, you must be seeing everyone is talking about and building from there and tokenization with different, different framework. And recent like SEBI circulation about creatives of regulatory framework around a fractional ownership of real estate. So even if you read today's economic times, we're also mentioning that fractional ownership of regulatory framework up to SEBI intervention. This is going to be a hot topic, like how we've seen the ICO in 17 and 18 and then NFT in 21. So obviously. So I think even when you question, you can ask to Ashwath over his screen. You can unmute yourself and you can ask the question. So just a general question from my side. I know wallets probably not related to physical assets. It's more related to movement of money, but any specific use cases that Spydera has done around wallet integrations and tokenization in that space? Yeah, so we have done some work also, but I think in sort of answering the larger question, not necessarily wallet integration is about money or cryptocurrency. It could also be, for example, an asset that you own. It could be a real estate asset, for example. When you anything that you own can actually go into a wallet. But I think in an enterprise case, use case scenario, I think the question is more around who are the participants in the network? Are they end users who are in the participants in the network? Then yes, absolutely it makes sense to basically whatever you're issuing token or asset or NFT goes into the wallet of the user. But in a lot of cases, the participants are organizations, like in the insurance use case I was talking about. And insurance is an asset which is owned by the insurance company. In this case, of course, it's actually issued to a user, but in the use case, it's the insurance company that has to do something with it. So in that case, the wallet sort of is owned by the organization and not really by the end user. So I think that's where you need to look at what is the actual use case and where the asset should actually be owned and which wallet it should go into. Right. Okay. Thanks for answering. All right. Yes, I think a lot of the questions seem to be already answered. So I'm not reading through all of that. But yeah, if there's any other questions, please feel free to unmute yourself. Ask. Yeah. If no question, then we can stop and you can find this recording on Hyperledger YouTube channel. All right. Thank you everyone for joining. And you have a great day ahead. Thanks very much. Great presentation. Thanks. Thank you, Ashfaith. Thank you.