 So today we're going to be talking about how Hyperledger Fabric and Simba Chain work together in this particular case. Today I'm going to be talking about Hyperledger Fabric. Today I'm going to be talking about Simba Blocks, of what we do as our product blocks. What products we work with, a project we work with, with Hyperledger Fabric, and what we intend to do for the next upcoming future with Hyperledger Fabric. So we'll talk about who Simba Chain is today, what we do, blocks our platform and how we work with Hyperledger Fabric and how it's implemented there. A Hyperledger case study of the work that we've done with Hyperledger Fabric, some of the customers that we've worked with, and then what the web-proof future would be like with blocks in Hyperledger Fabric. So let's talk about the origins of Simba Chain. Simba Chain started in Garford Grant in 2017. So a lot of the work that we've done has been aligned in the government and large enterprise space to primarily focus on private and public block chains. So the first one that we started off with was with Hyperledger Fabric back in 2017. And then once that started kicking off, or on 2018-2019, we really started to get some traction with Boeing, with Nav Air, and some of the other projects that I'll be talking about today. But then we decided that we want to go into the more enterprise space. And that's actually where my background comes in from. I come from Accenture and Salesforce, where my job was to really commercialize the engine that we created and make it to where it's more of a SaaS offering platform as a service offering built in out of the box as functionality. That's where we launched blocks in 2022. And so now with Simba Blocks coming out in 2022, this is pretty much built as a platform on which enterprises can leverage transformative capabilities to Web2. We want to allow them to be able to seamlessly, whatever their Web2 mechanisms are, whether they're whatever cloud, omnichannel, whatever they're presently focused on, we want them to be able to build that and bridge that within Web2 to Web3. And so we really focused on future proofing our solution, right? We've realized really quickly right away that the majority of our customers kind of go through this matured model of being able to identify a use case, build that POC, the problems that they face within the POC build phase, comparatively to the problems that they face within the test or scalability phase, we're different. And so our modules that we built within our product were built for each specific phase and each specific journey within our maturity journey that they had. And so here you can see this is our platform block really broken out into individual core. Our whole entire purpose is to abstract the infrastructure layer. So that'd be public change, private change, it doesn't matter. You can bring your own or prevent it out of the box for you. Cloud services, whether it be any of the three cloud providers or even IPFS, you can bring that to your storage services. Wallets, for example, bring your own or you can provide utilize our out-of-the-box solution for custodial, non-custodial wallets you like. But really it's the whole purpose of being able to abstract the infrastructure layer, right? Whether the identities, wallets, cloud services, or blockchain. And so our developer toolkit is really built around the platform block where we provide interoperability, whether it be a public or a private chain, it doesn't matter. Our off built-in for enterprise security and scalability. Smart contract designer for quick development and design deployment of tools. Whether the chain code or actual smart contract code via EVM, it doesn't matter. Both of them are applicable. So right once deployed to all type of mentality is kind of what we've done in the looked-in. And so I'll talk about a little bit more on our benefits of the whole entire platform, right? Dynamic APIs is really the initial phase. It's to quickly get started, whether it be a mobile app, a web app, a postman, it doesn't matter. Really you want to be able to spin up, design the smart contract as quickly as possible. High availability, so regardless of TPS and transport, we'd be able to provide that as well. Full chain freedom. So then it's two public chains, two private chains lying in the box. And then we also have other additional chains along with that from the venture foundation. We have some of their ecosystem projects as well. Most of our focus has been around developer accelerated tooling. So developers are our primary users, whether it be enterprise or cross-function development. Structured data is kind of the key approach there where we allow developers and enterprises to be able to query across multiple chains with one query and one endpoint using GraphQL or Graph-like tools. And then we're enterprise ready, right? We're compliant. We work with the Department of Defense, our largest customer. So therefore we do have the credibility and capability to provide that support that we find secure. And kind of the business benefits that we follow, right? They don't have the blockchain resources, so we provide auto-dynamic APIs. The blockchain can't be decided which one to choose. Sometimes the customers and enterprises feel uncomfortable diving into one particular chain, whether it be hyperlinked with fabric or a public, like Ethereum, for example. How can you have an interoperability solution? This is how we provide that. Can't test or really iterate quick enough or be able to accelerate features out to their customers? Once again, private or public, it doesn't matter. Our rapid development is built around that, right? And concerns about unlivable blockchain. Well, we kind of abstract that, right? We're making it easy for our developers to be able to be a hybrid solution, whether it be a public or private model, and really extend the functionalities of Hyperledger and its ecosystem, along with the public chains that exist today. So we really kind of provide a lot of advantages across Hyperledger and all the other chains that exist today, kind of abstracting the entire infrastructure layer. And what do we sell and who do we sell to, right? And that's kind of our product at the core, right? Blocks. That's really what kind of allows you to be able to have future proofing into whether it be a private chain or a public chain, or kind of a hybrid solution model, which we've now come across a B2B2C, right? So let's say you have a supply chain, you have parts and product, but then you want to bring that to your consumers on a public chain network, right? So how do you kind of still manage to cross that data interoperable? And that's how we would do that with the core of our product. We have a platform, just the platform itself, which is a product, but then we also have a tech enablement team, which is the services team layered on top that really provides a full implementation. Our customers for those are the three sales direct motion. We have a direct tech integrator and a system integrator motion. So therefore, enterprises that we have that can be a full product play, that can provide our product, utilizing all the benefits that come out of that, so therefore they're abstracted, utilize Hyperledger or a hybrid solution in this case. A system SI is built on top of our platform, utilizing our platform for their end customers and consumers as well, which then they can sell to those enterprises as well. Then we also have technical integrator partners like Aletheon and Fujitsu who provide a layering integrated and embedded with us as well. So now we have a go-to market together that is utilizing Hyperledger and Hyperledger Cat-Tie, for example, with Fujitsu, being able to provide interoperability there. And then the largest customer that we have is our government, which is Department of Defense. They provide us all the complexity and all the structure of the data, and then we kind of build that services on top of our own platform as well. So on the left-hand side, it's more of a services approach to it. And on the right-hand side, it's a full product play where customers can really get started with our product today. And so now that you kind of understand how blocks is built, let's talk about how Hyperledger Fabric plays in, specifically with the projects that we've done. And so what we do with the blocks platform is really designed to make it abstract into where you don't have to worry about the oncology, the network, the topology, any of the above. We really abstract the entire infrastructure so you can focus on the application development that needs to happen. And that's really, really at the core of it, right? So the project that we built was the BIPAR product which was connecting OEMs with the Department of Defense. The two contributors and stakeholders that we had, which was Boeing and Navair. And so our entire goal here was to register and track components in an immutable way, in a non-immutable way, track the Boeing production schedule for F-18 wings and tailhooks. So those wings and tailhooks have a bunch of different parts, like screws and parts and nuts and bolts that they get from n-th degree of suppliers. How do we track that across multiple trains, whether it be private or public, and how do we have immutability across all of that, the transparency of that data, right? So we use Hyperledger Fabric as the blockchain to provide automated shared progress updates for each of the individual parts so therefore the larger consortium owners could see where that product was in the assembly line or the shipping line, in this case scenario. And so let's talk about that. The overall goal was to track parts that were coming in from OEMs and track the progress of those individual parts. For example, the OEM, in this case, Boeing, might be able to make a wing for an F-18. So Boeing uses their internal insights, ERP systems and all of the above legacy systems that they have. They want to share the progress of that, but they don't want to expose all of the data. So how do they work with their suppliers and that keo information that they have in their ERP systems and XYZ systems for the wings, utilizing that. So they bring that on to Hyperledger Fabric, where then that allows them to be able to share private permission data to the other providers, in this case the OEMs that they have additionally across. So now NAVARIC can receive these updates using Hyperledger Fabric and really gain more fine-grained view in the entire end-to-end process. So they can see that this supplier is providing this particular screw and there may be a delay, there may be a possibility that that order may have some hiccups or even a recall, for example, can all be tracked and now with the combination of predictive analytics and AI, you're able to actually stimulate exactly how that process will look and feel. Now you're able to really forecast all of that information, right? And so now parts are tracking, the tracking that we are, are tail hooks and wings specifically for the F18 end-to-end process. And so here was the blockchain architecture where we had multiple chains really working together. NAVARIC was on Quorum and they had their specific sunken cost that they had to operate and manage with Quorum, but then Boeing was on Hyperledger Fabric along with TAMCO, another processing manufacturer. So how do we work with Quorum and Hyperledger Fabric? We need them to be able to interoperate with each other. So there are two parts to the system, the OEM blockchain and then the NAVARIC blockchain. Each which will host their own smart contracts and have to work with each other, so therefore the data reflects across both chains as well. You need it on one particular chain, which is Hyperledger Fabric in this scenario. So you can see Boeing has their legacy systems that they have to work with, which is their ERP, NES, all their purchasing order systems, all of the above. We placed our instance within their organization, within their intent as well, so therefore they could upload that data onto the blockchain ledger that they wanted to choose of, which in this case was Hyperledger Fabric. Now, you can see that they had to go through multiple steps. There was an ATL process, there was a lot of configuration, a lot of manual massaging aggregation, right? And in the same way in, you would have to expect that that would also be the same way you have to extract that data. Manually massage, multiple blockchains, aggregated, manually consolidation, and then finally really get to the data. Well that's where we come in. We kind of provide a full abstracted level to where you can utilize one endpoint and one query across all chains. So NavVare didn't have to worry about if it was on Quorum, if it was on Hyperledger Fabric, or if it was on Ethereum, a public network. To them, it would not matter. It would just be one API endpoint and one query that they'd be able to get all of their data back. And in the next few slides, I'll show you how that actually looks from a data perspective. So the blockchain process was pretty simple. NavVare had about two nodes, Simba and Ataco on Fabric, which then Boeing has a script that queries their ERP system and extracts that information into the different parts that we are tracking. Once they've done that, they've actually periodically generated a CSV file and then gets uploaded, which is the data input onto the ledger as well. So now that you've done the ETL, it goes on through the APIs that we provided to them. They were able to immediately upload that data to the ledger without any hesitation. And now that we're able to do that, the OEM, onto the OEM chain, that is immediately available for NavVare to be able to pull that data up and use that data across all the networks that they have available. So therefore, they could utilize it with Quorum and Hyperledger, and that data was immediately available to them. Now, let's talk about NavVare's view. They had multiple Quorum networks, about 10 to 20, and now that's what they wanted to get to. So NavVare's data is collected by NavVare's smart dropper application, which is built on Simba's application, which really what it does is four data houses update the periodic once in a day. They just kind of fetch that data constantly, right? So NavVare queries based off of Boeing's update to the ledger on Hyperledger Fabric, which is generating those multiple tiers from files and contains information of those parts that we were specifically trying to import. So now we've got a combination of happening. An ETL update here, a pull and fetch, and actually uploading of data from Boeing and from NavVare, both the OEM and the Department of Defense working together. Once again, NavVare also needs to push data up and pull data down. So therefore, that data needs to be immediately available on any of the ledgers that they choose them. And that's when we come in where it doesn't matter which ledger that they belong to, utilizing GraspQL, they'll be able to pull that data immediately across all their chains as well. So this was both of the two processes. So now, the purpose was the multi-chain matter scenario. They didn't want to be locked into one particular chain, and they didn't want to be just kind of operating just silently, right? They wanted to work together as a team, right, and provide that data. So the support from multiple blockchain bindings using the interface and adapters was the model that we chose, and that's actually how our inter-offering really plays. It's based off of adapters. And so now, there's no dependency on single blockchain, and along with that, there's a support for multiple blockchains per application. So therefore, I could have done the same application on Hyperlegic Fabric and Quorum right once, deployed all. So as a developer, enterprise, or consortium owner, I can fully abstract my level of blockchain of infrastructure that I'm causing and working with. And so now there's a lot of key benefits, right? We have a generic API for multiple endpoints. So I as a developer and enterprise company don't have to have specific endpoints for Hyperlegic Fabric versus Quorum. I cannot inter-operate with both of them. Or some of the other ones that we've mentioned here, such as Binance, Burl, RSK, Stellar, and Ethereum, and also some of the other EVM compatible ones as well that are not even working. So graph relationships can be made from an asset or a transaction, and one one chain with one another chain as well. So therefore, if I make any changes on one chain, I don't have to manually go in and make those updates on another chain. So any transaction that happens on Hyperlegic Fabric will also follow through on Quorum. So therefore, when NavAir or PoE pulls the information from the ledger, they have the latest information constantly updated on both of the ledgers in this scenario. And then that allows you to really search across all connected chains and smart contracts. Now you have relationships built in with those smart contracts. So what that means is we take a different approach, right? And this is very common in the Web 2.0 world where you kind of create a business operation logic, create all of it, you kind of just dump everything on chain, and then you do more of an analysis afterward. You kind of put the pieces to puzzle together later on. Well, we say let's do it before the fact. Let's put them on the smart contracts and chain code, and therefore now those relationships are actually queryable right away rather than having to build them later on. So what that does is abstract the infrastructure layer. So now you can deploy on any chain, because we're API based, but then the transactions can be searched using GraphQL across those chains and data contracts. And so in the next few slides I'll show you guys how because of this format, we're actually able to see exactly how one query and one endpoint can be done across all the networks you chain. And the complexity that we're tracking for is part tracking. The bill of material, VOM, right, is a list of parts and assembly that need to go together. Each assembly contains another VOM and so on and so on. So this relationship tied into the individual assets that have so much more weight and value than just being an asset by itself. So these complex relationships are across different suppliers and the degree of suppliers that they have to focus on in the supply chain. And so that's really the synopsis of what we're trying to query and how we're trying to plan for it. So you can see the smart contract defines relationships between the aggregated data sources and how they're recorded onto the distributed legend. For example, in this case, we have the selected you can see how the data is mapped from a supplier which is captured on a hub log in the information and the VOM data to the depot itself. So you can see that I have a stock item that's associated with a heart that's associated with the supply that's associated with the supplier that we got it. So these are individual assets that now actually have relationship. So now with one query and one endpoint, I can actually indicate all of that and see all of that, right? Do you notice that I clicked on a supplier stock item in this case scenario? And now I have supply as an orange, right? And what that does is now I can actually drill down into that. I can take a deeper dive into that with another double click. So you say, okay, let's add a filter to stock number ID and I put in a unique identifier number for that particular stock because that's the exact part that I want to get down to. So now we select that and now I can see the first level which is telling me just the stock item itself which is just the individual part. So you'll notice on the bottom there as a tag I can actually click and double click into that data set and just find out information for that particular supplier all within one query and one endpoint. I don't need to have multiple endpoints and queries regardless of what chain it belongs to. So now this view shows all the suppliers for this particular part that provided this particular part to me and all the suppliers that touched it within the supply chain process as well. You can see that I'm second level nested into that data point from stock item to supplier. I can actually go third level nested as well with one endpoint and one query. So I can see the supplier that provided this supplier with that information as well regardless of what chain and network they belong to. So now with one endpoint and one query I can get three layers of data of information available to me. And now you can see with a much more granular view of how that would work with a consortium-like view where you have multiple networks and multiple chains. So in this case Progress Tracking is on Hyperledger Fabric by Boeing providing that data. Inside this black line that we have another private chain which is Quorum and then outside that is Quorum as well. These are all providing three different layers of data. But in this case I only query the PL details. Once I've query the PL details I can see what supplier belongs to where it is in the status of the Progress Tracking which nth degree of supplier provided that and which part provided that as well. Along with that I can actually double click and triple click into which aircraft that particular belongs to now at the end of the supply chain process with one endpoint and one query. So regardless of how that is regardless of the infrastructure and how it was set up you can actually query across multiple chains and networks. In this case which is what we call Interoperability 1.0. Being able to read across multiple networks regardless of the infrastructure and network there may be. We're working on Interoperability 2.0 which allows us to read and write. So for example if the part price goes up for this particular part the product details and the OEM delivery price also goes up and basically includes our contracts and chain codes without having a reactive human intervention to it and that's being able to write across multiple chains as well. So we're working on Interoperability 2.0. And this is what we delivered for NavAir in our Boeing blockchain initiative which was being able to talk to three different environments regardless of infrastructure and choice. In this case we had Hyperledger Fabric in this case we had Lockchains Interpise Blockchain Service of Azure along with their OEM version of the Fabric and then we also have NavAir which has their own Hyperledger Fabric system as well. So now you've created a foundation of data sharing and trusted this data manager. So the outcome was pretty simple. We seamlessly integrated NavAir and Boeing systems using Simba and Hyperledger Fabric so the two apps would continue to exist. And then implemented a secure access or robust data validation for enhanced system reliability. That was one of the really cool things we wanted, right? We automated that data time updates and real time critical updates through smart contracts. So kind of speaking to that interoperability 2.0 we were able to create alerts now we want those alerts to automate, right? We want them to follow through with action as well. So when an alert happens right now it's more of a manual intervention we go in and do what we need to do. But we want that to be more automated so where smart contracts can pick up on that alert notification and complete the transaction that they need to complete. Digitizing and optimizing manual process, right? That was all manual. That whole entire thing with the ETL process and the way we uploaded data or brought data to the chain as well, right? And expanded blockchain model by incorporating additional FRCCs and unified solution kind of unified it all but really more importantly than anything are the benefits, right? Life cycle traceability, part history inventory levels are now available. Everything that we were looking at from a traceability that was not available from the supply chain perspective is now all available. And with those data points now companies can make better decisions, right? A predictive analytics layer on top to make those decisions in a much better way. And so this is kind of how the infrastructure really look, right? You have the Symbouching API, CacheGate going in and out. You have NASPAIR with Bones infrastructure involved as well the Service Plus. So you have Hyperledger Fabric really built up a core, right? And all the Hyperledger Fabric users tie to one configuration. User and onboarding users is always a complex process when it comes to our mission chains. We make that super easy by building it more out of the box for us. So therefore customers don't really have to worry so much about how the network technology has to be and onboarding folks to your consortium is much more easier with that being said. And so what do we intend to do going forward? Well, we have StratFy, we have some integration with our technology partners, and then there's a lot of Web3 tech trends, right? With hybrid solution, with a more B2B like solution, how do we incorporate that into it easy, right? This kind of brings all that technology together. So for StratFy, we've got a recently $30 million Department of Defense contract that we've just awarded. And so because of that, the whole purpose of what we're doing is modeling across objectives, right? Moving digital assets across. So this is kind of what I like to call is the phase two of what I just explained was the five part, right? It's not really a phase two but it's kind of going into that same direction of being able to now associate metadata with those individual assets that we just started tracking, but more off-chain data, right? We were just talking about on-chain data in the previous project, right? Now this associates on-chain plus off-chain, like the PDF, so the invoices that you may have that you want to associate to that individual transaction as evidence, how you can do that. That's how we're going to do that. And so we have more of a state machine smart contract mechanism that we like to implement with, which will allow us to see off-chain data of the digital file storage but then also incorporate how those assets are actually characterized and used using DIDs and VCs, which I'll talk about in the next slide. And so this is kind of our infrastructure that we'll go with is securing those digital assets, utilizing the TDPs, design files, those documents that they need to be able to provide with those transactions. We're going to utilize DIDs and VCs using the smart contracts to authorize that, right? Then we'll have supply-chain data with that as well going into the same process and flow. And so process, materials, tracking, tracking more than just the FAT parts that we did in the first part, right? But then now, now that we have that data, we also want to track the finances that go behind that as well, the transactional actual data along with it. So budgetizing with that as well. So we want to put that on our assets as well. Once again being able to provide a predictive analytics layer on top of all of that is very important. So therefore we really abstract all of the blockchain infrastructure for a predictive analytics company to come in and just utilize the data based on their access that is allowed to them using the smart contracts as well. So they are now part of the consortium rather than being an outside layer of the consortium providing predictive analytics. And this allows us also to be a part of a secure IL45 environment which is what we're aiming to do. And so that was more about the stratify, the government work, but we also have the enterprise, the technical integrators and SIs that we cater to. Deloitte being one of the first ones that we're focusing working with which is kind of their tech trends that we're kind of working with, right? So we're looking for mission networks. We want to continue to grow on hyperledger and some of the other ones that come into the market. Improved interoperability being that hybrid model allowing customers to not be locked into a particular chain or even having to worry about which chain or why. Actually just getting the benefits out of, for example, hyperledger being able to utilize the benefits right away that's what we want them to focus on. And more importantly, tech improvements and innovation such as ZKP, DID, DCs, this is the new identity model of the remainder of the year that's kind of what we're all focusing on, so implementing them as well. And so kind of the trending initiatives, projects, it's a type of projects or use cases that we're working on currently or we have within our build pipeline or sales pipeline. It's all catered from supply chain all the way to circle economy. Customer engagement is more of our B to C. Supply chain is more of our B to B track and trace, authentication providence inventory. NFB is the new one that we're working with as well which is non-fungible documents, right? This is more like titles, credentials, liquor licenses, marriage licenses. They all have municipals, right, that need to go through a certain life cycle of the asset, right? That may have multi-party systems, soulbound system, for example, like that. So those are the kind of things that we do. Sustainability ESG is a huge one, right? Carbon tracking, be able to input that information, kind of output that information as well. And then some of the other ones that we're now kind of focusing on is economy of things or implementing more of AI data providence as well, being able to provide more onto that side as well. These are kind of the initiatives. Recently we worked with Philippion, a partner of ours, to make physical NFTs. So what that means is actually they're able to take an image of any particular item. Right now, glass is the only thing that's a variable in specific types of glasses but any other item, whether it be this particular item here, my jacket, my shirt, or an expensive handbag for example, you could take that picture using an iPhone and that immediately registers it as an NFT. Now, once again, if I want to validate or see if that item is a counterfeit I would scan using the Philippion app the same image or any angle of that actual handbag, for example and you'd be able to immediately identify if this is a counterfeit product or not. And then you'd be able to track that using the NFT. Therefore, it's created as an NFT and this could be really a simple non-functional token when you want to use an Ethereum or a chain code, for example. So this architecture reference is built for any type of infrastructure chain that we have to use whether it be public or private. And this would allow you to actually check the image from your point with the NFT and if it's authentic it releases a lock which is pending and then we can transfer it. If it is a fake item, it will actually reject but it's not authentic so therefore it will cancel the request. That is technical integration partnership at ATFINUS so that is with Illytheon who we partner on top with providing really the infrastructure or the smart contract, everything on the blockchain side while they focus more on the counterfeiting side. And so this is the five steps, right? The supplier uses an app to photograph the item. It is request, the ascent to Simba's platform to be an NFT that's muted and the request contains a name, description, hash code and then the off-chain file as well. So the image itself can be stored in an off-chain storage whether via blob storage or whatnot and then it creates a hash with an on-chain so therefore now the associated off-chain files are now stored via a hash on-chain as well. And so now you can check if the item is authentic, you can do the solution queries that Simba chain provides and then if they are, you've completed the check you can actually transfer, burn, move over sell all of the above now that you've authenticated the actual part of the sell. And so that really kind of provides authentication and verification. That's something that we've done on a public chain. We've also done this on a POC level or a sandbox environment on a probation chain like for example, I've learned a fabric and forum and we intend to roll this out as a virtual market solution with all of our customers, regardless of what chain of choice they need private or public and available for both. And that's really us in a nutshell. That's Simba chain and all the work that we've done with hyperlinks of fabric and all the things that we're going to be doing in the upcoming future. Thank you.