 Hi to California, hi to Lithuania, hi to London and hi to Pennsylvania. Hi everyone and welcome again to this hyperledger in depth member webinar with Kaleido on tokenizing assets at institutional scale. We'll get started in just a couple of minutes just to give more people a chance to join. Welcome everybody and for those of you that joined me for my last check-in I also invite you to use the chat button. Say hello and tell us where you're zooming in from. Hi to Turkey, Germany and India. Welcome, happy to have you. All right, so we're gonna get started. Hello everybody again and happy to have you. Welcome to this hyperledger in depth webinar with Kaleido on tokenizing assets at institutional scale with Kaleido and hyperledger technologies. We're delighted to share this new webinar with you. And my name is Tomasz and I'm an ecosystem manager at the hyperledger foundation. And it's great to see everybody here, including our panelists who I will introduce in just a moment. Today, as usual, and if you have attended any of the previous member webinars, you know that we have some housekeeping. So, first of all, I would like to say that everybody is welcome in our hyperledger community, and that we are striving to create a welcoming environment for everybody. So please follow our code of conduct when interacting with other participants of the webinar and broader in our community as well. And you can find our code of conduct on our website and on our wiki. All the hyperledger foundations are held under the Linux antitrust policy. And you can find that on our website and our wiki as well. This meeting is being recorded and it will be available for you to review later in our webinar library as well as on our YouTube channel. So if you miss something, you're always welcome to go back and check it out there. And the slides will also be downloaded. It will be able for download in our webinar library. This meeting is also being live streamed on YouTube and LinkedIn live and welcome to everybody joining us there as well. Now we like to encourage these webinars to be as active as possible. So if you have a question or a comment, please feel free to use the raise raise hand function and we will unmute you and you can ask your question to the speakers. You can use also the Q&A box as well as the chat button to ask your questions. And for those of you joining on LinkedIn live and YouTube, feel free to use the comment box to ask your questions there. And, you know, we would really encourage you to be as active and ask as many questions as you would like because the more participation we will have the better experience for everybody. And for those of you that have questions that don't get answered, we will also share our Discord channel as well as the contact of our member company Kaleido so you can contact them directly as well. Now without further ado, I would like to introduce Lana and Nick. Lana is a principal architect digital assets at Kaleido, and Nick is a solutions architect at Kaleido. Nick and Lana, over to you. Thanks Tomas really appreciate it. And thanks to hyper ledger and all the attendees for the participation today. As Tomas said, I'm an architect at Kaleido. I've been involved in the hyper ledger community for about eight years seven and a half eight years now, spanning from a previous career at IBM, where we worked very closely with the hyper ledger fabric protocol. Since then we've remained very active in the hyper ledger community, contributing to repositories like hyper ledger base who we seated the code base for hyper ledger firefly and are very active inside of that community. So you'll see some glimpses of both of those protocols and no clients today, as well as a great glimpse of hyper ledger firefly so excited to be here. Welcome to everyone and I'd reiterate what Tomas said, please don't be shy. Any questions raise your hand use the chat. We love interaction so welcome over to you Lana. Awesome. Thank you for having us. So my name is Lana Kalashnik. I'm a principal architect and I focus on financial institutions and digital assets at Kaleido. I've been in the blockchain space for quite some time to go in about eight years now and during this time we've accumulated quite a lot of knowledge and little nuggets that we've been collecting over time that we want to share with you. Prior to joining Kaleido I led venture building at FIS, which is a great company for building out financial products. So we focused on digital assets there. And prior to that, I was the global technology lead for the blockchain segment and Amazon Web Services so I had quite a lot of experience building companies and helping customers kind of grow their footprint and their use cases based on hyper ledger products. So thanks for having us I'm going to go ahead and share the slides so we're going to go over just a few. I wanted to share some of the, some of the things that I've learned over the last eight years or so. And then we're going to go through a demo of actually showing how you can think about the space, how tokenization enables new use cases. In my case for financial companies but not necessarily. So this, these technologies are pretty broadly applicable to to, to a lot of these cases. Right, this is us. So, I'm a little bit about Kaleido so we've been around for a few years now so it's going on to the year six, and during this time we worked with global leaders in multiple industries. So, standing up consortia is something that is not traditionally easy to do, however we've combined our open source product along with, with the Kaleido platform to automate a lot of the functions that used to take a lot of time. Today we're going to be talking mostly about how do you move from consortia or from your test blockchain networks to tokenizing assets. And when we mean assets there are multiple definition of what an asset could mean. So for somebody let's say from Shell an asset could be a barrel of oil versus somebody who is working in capital markets this could be a different asset type. So for us it's just a representation of financial asset or an asset that is kind of reflected on chain. And one of the examples that I like to bring up is our work with Swift. So Swift is a, is a global leader in relaying transactional data between multiple countries multiple jurisdictions and so on. So it was really interesting to trial a new CBDC solution that they were working on. If you've been following CBDC development it's a pretty basic tokenization example of tokenizing an asset such as a currency, and understanding how can global banks and central banks communicate with each other. So this, the, the example that I'm bringing up here is the second pilot that Swift ran on top of Kaleido, where they were interconnecting global banks so we've had over 12 banks I believe here, and also interacting on chain data so based on Ethereum protocols, and also with their internal processing systems. And this is something that I continue hearing from customers is that, although, you know, tokenization and blockchain bring a lot of new use cases you have to integrate them with internal systems. So if you're from the capital markets background you're probably likely interact already with different asset types so what we're doing here is that we're tokenizing new asset types and adding it to portfolio, let's say traders and so on. So this is a question that comes up quite a bit, you know, for example, you know, do we tokenize real world assets should we focus on financial instruments and so on and so forth. And typically would suggest that you're that whenever you're trying to create a new asset to tokenize, you're really looking to create interoperability between your systems. So you're looking to increase liquidity of these assets, and possibly create new financial instruments. So there is there's a new trend that's been going on for about 15 years or so of private markets growing a lot faster than public markets, so companies tend to state private longer, it actually created an acronym SPL. So where a company tended to IPO within four years from its formation now it's taken up to 12. So the funds kind of moved into these private markets, which presents a really interesting opportunity for folks to tokenize those assets which brings new standards brings liquidity to the market and allows you to have fractional ownership of these assets. It also helps you was improving settlement times. So as a, for example, an example of tokenized corporate bonds, you're able to get money faster. So by tokenizing and selling those bonds at a certain price so settlement is accelerated versus going through really inefficient structure that some of them are currently using and waiting for months let's say to take advantage of that liquidity and global 24 seven markets so this is really attractive. If you're looking to take advantage of let's say arbitrage opportunities between different markets. So let's say you have a spread between you know Japan and US markets that you want to take advantage of. So this 24 seven global market settlement is really attractive to folks. So just to reiterate is we're looking to tokenize assets that could benefit from increased liquidity that are kind of not well defined right now so bringing more form and standard to this tokenized assets that allows you to create new financial instruments or not even a financial instruments there are some tokenization use cases around loyalty port points, tickets and so on and so forth. So based on this we've been building out our asset tokenization offerings. It's all based on the open source engine which I think is really important for business continuity in just helping each other grow. So we are pretty strong believers in open source and working with organizations such as Hyperledger on a growing products or projects like Firefly, BESU and multiple others. So we are building integrations for these protocols it with a high quality chain infrastructure if you try to run notes before making sure that they're they're up and at the correct block height is really really important for you to kind of know if if you're if you have the correct data. We've also are right right now going to be showing you a tokenization platform which allows you to create a new asset type by leveraging the smart contract management interface. So managing smart contracts that are representation of these tokenized assets is something that we've put in quite a lot of work into. So a little bit more about the our blockchain business cloud as we call it so the way we see it is that on chain activities only about 1015% of the final solution. There's a quite a bit of integrations that need to happen for for folks to take advantage of tokenization. So for example thinking about things like custody how do you manage it how do you integrate it was the key management systems. What about messaging or what about you know pews and and the chain infrastructure itself. So we've built this multi layer platform that allows you not only to manage your chain so you could be using any hyperlature flavor here so whether this is BESU or hyperlature fabric. And on top of this we've built a middleware layer called firefly that really simplifies messaging and even take some of the transactions that were typically done on chain off chain. So this is secure messaging between members of a consortia let's say or your trading partners. So really fun product which Nick will be talking about later on. On top of this stack this really solid foundation, we're building new products. So we have the institutional but three asset tokenization platform that really allows you to simplify this integration to simplify issuance of new token types in management of these smart contracts. We've done the same thing for NFTs. So this is also also allows you to pin off chain assets. So in this case an asset meaning an image file or any other digital representation of value. And we are also focusing on consortia so really simplifying management of multiple members of your business network so this is all built on top of the open source technologies and hyperledger technologies at their core. So this is a closer look at the simplification that we've achieved by using hyperledger firefly. I will let Nick jump in here and point out a few things that are going to be most interesting for the folks on the call. Nick you're muted. Nick you're muted. Sorry. No, thanks for this. I was going to say you could use either side but this is fine. What you notice very easily on this slide what you can extrapolate is that there are a lot of things that sit in between your front end application and the blockchain right and these are what we call middleware. These are the things like, you know, sort of message buses, for example, or databases or, you know, different Oracle plugins right, it turns into a long laundry list of, you know, functionality and you know sort of integrations that you need. The next is that out of the box middleware piece where it's a event driven orchestration model, highly highly pluggable for things like databases, things like key modules, and it's meant to be this very elegant very clean integration into your application and into your systems as well. It supports different types of messaging public messaging right blockchain first broadcast messaging with IPFS, but then organization to organization private messaging. We can think of the importance of that in all sorts of use cases supply chain capital markets insurance healthcare, even in gaming or retail and entertainment for that matter right and so you start to understand and you start to decompose. What goes on chain what goes off chain and how you deal with sort of events that your application or organization is going to ingest right. I've ingested a blockchain signature a transaction event. I've ingested something that's been broadcast to the network or I've ingested something that was sent privately to me. So the way you write code against Firefly is really sort of a state machine right you you subscribe to these different APIs with web books or web sockets, and then you know you write your own custom business logic about what to do when a certain circumstance happens right there. Firefly also has a ton of easy buttons inside of it. One of my favorite features such as you know turning solidity or you know chain code into web to interfaces so that you know it's not just the web three savvy developers that can use this system, but it's any any developer not even a blockchain developer. But what you'll notice as I take you through the demo and I'll turn it back to you here in a second Lana is that you're only true requirement when you come to the asset platform or when you come, you know into Firefly is to provide source code right to provide some type of chain code or solidity or business logic. And the beautiful thing is that if you want to leverage some of these really battle hardened token standards, like fungible tokens non fungible hybrid tokens etc. We bacon templates that pull from that opens up when library. So this could be, you know, very, very low barrier entry to anyone that just wants to get started with digital assets and start understanding how to model, you know financial barriers of oil real estate etc. So we're huge fans of Firefly huge fans of all things hyper ledger, and we highly highly encourage folks to you know sort of join this community participate on the discord. And you know maybe even, you know submit a good good first issue pull request that would be awesome. Yeah, absolutely. And the idea here is that we want folks to participate and bring their skills to the table so for example you don't need to know even solid it in a lot of cases which is why Firefly is really focused on building API so this is an API network project to where you can code against those API's with whichever language that you prefer. Obviously the data is going to be persisted on chain, and there is a facility component which they could go over, but the idea is that we want to decouple some of the flows, as far as the data goes, you know messaging that shouldn't be on chain should be on a different persistent layer, which is what Firefly provides. Awesome. Okay, so I wanted to talk a little bit about the custody and management I think this is an interesting point so if you're looking at the ecosystem. There's been a lot of different custodians that came and went in digital assets so they're multiple types right so we have we're all are familiar was hot and cold wallets so hot are the online wallets and offline ones, but it can be sometimes tricky to figure out which asset type deserves which custody because there are also a lot of cost considerations here as well. So based on this and because of this we've decided to be not opinionated on which custody solution you plug in, but we've built API for you to be able to plug in them anyway. So based on this we're supporting for different types of custody solutions through Firefly integrations. So the first one we offer is is collider hosted wallets. So this is your you could use either a hosted node wallet or you can use an HD, which is the hierarchical deterministic wallet that allows you to obscure your identity for example and allow you to manage all of your addresses through a tree. So this one is a lightweight collider hosted really robust wallet that allows you to manage your contract your assets and different account types. And then if you're moving further to further down the slide, you will notice that we also have cloud service integrations. So some of the cloud providers such as Amazon web services do provide services like KMS that you might be using already for key rotation and as a part of your infrastructure. So you can absolutely use that or Azure Key Vault to to provide your custody and key management solutions, and it does work for a certain protocols so for example some of the curves on the elliptical curve are now supported so that's so those solutions are available. And if you have requirements for HSM so this is more of a heavy duty hardware security modules that do mean that you are or are allocating a cluster of hardware modules that can be plugged in as well into your into your asset platform. So we're supporting AWS cloud HSM as a part of this, but also if you have your own, let's say on premises custody solution or or a key management solution you can also plug it into the platform as long as it's a compliant with our standard. And we're also looking at the development such as MPC. So MPC is a very interesting development that happened over the last few years in the way that key management is done through sharding a single key versus having multiple participants sign and approve transactions like you would in a multi signature scenario. So MPC here allows you to provide signing off chain which does have some performance benefits. So, for example, if the, the, if your token doesn't support on chain multi signature configuration, you can be using MPC through provider such as fire block, which we've integrated with to provide multi party computation. And if you have any questions on the trade offs, let me know. It really depends on the asset type and, you know, other considerations such as your security posture, the frequency of traded assets or transactions and how many folks do you need for approvals. I've personally talked to some capital markets customers that were really concerned about how custody is managed within their organizations. So for example, due to due to insurance limits you need to spread your assets between multiple custody providers so balancing that really let's focus on well outside of custody what else do we need well we need a policy engine, which brings us to a policy engine that we've built on as a part of the asset platform. And this is, I think a good way to think about the space so when you're thinking about securing your digital assets after tokenization. You really need to start thinking on multi layer policy engine and implemented as such. So starting from identity management. So really think about how you you're mapping your web to or existing identities to on chain identities services authorization so for example who is allowed to issue new assets was allowed to to trade you know our blocks and kind of control velocity here so velocity is a term of who's allowed to trade on and how much of a different asset type. custody management something would just went over and also transaction management so if you're if you're operating in the regulated space transaction management is where we typically do a lot of white listing of accounts so let's say who's you're allowed to trade with KWC and other configurations, also as a part of transaction management, you can set, you know retry attempts to make sure that you don't accrue slippage if you're in the trading scenario, and you are trading at the kind of the right price point. And obviously all of this integrates all the way to connectors on chain, but as far as we are looking at securing your digital assets, we should be thinking about as a multi layer policy engine that goes from course great to find great controls that should be integrated into into your policy management systems. So moving on I will hand it over to Nick in a second but I really wanted to touch on evolving tokenization standards. So specifically when we're talking about financial assets there's been a lot of work done between by multiple companies have done a great job and in a lot of ways of figuring out how do we recognize these standards right and when we're talking about CBDCs for example, each country is going to create their CBDC based on their own needs. So they're going to have some overlapping features and functionalities but they're going to also have some divergent ones. So based on this how do we think about tokenizing assets. The answer is we don't see a clear one answer. We're seeing tokenization standards evolving. So something from a fungible protocol, fungible standard like ERC 20 to ERC 721, which have been made prominent by NFTs, but actually can be extended and do you have really nice features. We're looking into financial asset tokenization down to new security standards that are evolving such as 1100 series and 400s. These are a little bit more heavyweight standards that do have a level of sophistication to them that folks have been working on and open sourcing a lot more. We'd love to hear from you. So if you want to drop in in the comments, which talk token standards you're looking at. We'd love to discuss that and share what we've learned here as well. And a compliance. So we all love compliance. Nobody likes being audited. So I would say front load any compliance conversations. So we've done this as a part of building out collider from day one. So SOC ISO compliance is something that we've built into our platform. And really think this is the kind of the responsible way to build in the digital asset space. And this is it from my portion. Please let me know if you have any questions. I'll be lurking in comments and probably interrupting Nick as he's going through the demo. You'll see our information here. We're on LinkedIn and you can email us anytime. And, and yeah, thank you Nick over to you. And you're still muted. Still muted. Okay, well thank you Lana. That was great. Hopefully I'm unmuted now. So that was nice table setting out of Lana there. The theme that I'm really going to try to highlight during my portion here is, you know, really around flexibility. So Lana took you through, you know, the full spectrum of key options that you saw available. Well, if you have a different service provider or a different, you know, implementation, just let us know right we built firefly we built this middleware to be inherently inherently pluggable so it's not necessarily just what you see on the glasses what you can use. It's not necessarily you have to choose one wallet type right and it's one size fits all can be multiple wallet types it can be bespoke integrations and you can, you know compartmentalize different asset classes against different wallets maybe if it's an NFT I don't really care about I'm cool with a, you know, a server side custody wallet. Maybe if it's a high fidelity financial instrument I'd like that key that's associated with it to be you know in fire blocks behind multi party compute signature thresholds. So I just wanted to reiterate that similarly with the policies right doesn't have to be one policy that fits all policies for different, you know, asset classes different smart contracts different workflows. We're going to spend the majority of the demo today taking you through what we refer to as the asset platform. So looking at this top layer up here with a particular emphasis on what firefly does the open source hyper ledger project to kind of help make all the magic happen. But I do want to spend a couple minutes down here, just on the protocol piece to let you know what kaleidos been doing for the last six years. And as I mentioned at the beginning, we support a whole slew of different, you know, permission and public blockchain protocols, including two, you know, really prominent hyper ledger libraries and distros. And hyper ledger fabric and hyper ledger basu. So I just want to take you through the experience of how that looks on the kaleido blockchain as a service offering in the event that, you know, you just want to basu environment or you just want to fabric environment and maybe you're not ready for, you know, all of this abstraction and the 1000 API is I'm going to show you. I'm going to take a quick look at a few of those environments and understand sort of how that manifests on kaleido. So I'm going to go ahead and log into my kaleido account and probably move this zoom bar 50 times throughout the demo here. And what I did was I just went ahead and created a consortium named it hyper ledger six seven for the date, and I created two different flavors of environments I created a basu with IDFT consensus environment and stood up three nodes inside of here. And I had the inspiration to do, you know, a basu environment a fabric environment or, you know, get, quorum, quarter, the polygon, etc. It's a matter of clicking, you know, three buttons inside of the console, and you're going to get your own sovereign permissioned, HADR sock to compliant, you know, enterprise grade blockchain platform, which has API is behind it for you to start using it directly. So just a quick snapshot of a basu environment, you know, all sorts of rich experiences directly inside of your runtime to you know you have your logs directly available for you, you know the core node runtime logs your wallet logs, and then the abstraction logs where we sort of remove the need for you to use a you know a client library or an SDK so just a quick glimpse at, you know, Ethereum will spend more on Solidity spend more time on Solidity and Ethereum today so I won't take you through that example. I'm going to take a peek at fabric in a bit more detail. So, similarly, I've created a fabric environment on Kaleido haven't done anything overly fancy. It's using level databases using raft ordering service. And I just have a single order of single peer. And then I have a self signed certificate authority that's being managed by Kaleido. Now, the thing I want to point out, it's just as easy to create these run times and you know we even created default channel for you out of the box on fabric. It's really cool. You'll get this in Ethereum you'll start seeing this in the asset platform is we've put abstraction layers into all of the hard things that exist, you know, in blockchain and that's really kind of the ethos of Kaleido. We want customers, regardless of your size fortune 50 enterprise to, you know, mom and pop startup, we want you to get to value, meaning we want you to codify business logic right whatever you need to run on chain. We want you to build an app on top of it with a lovely user experience. If you have to spend 80 70% of your engineering cycles on these very complicated SDKs and very, very esoteric protocols. Chances are you're never even going to get to the business logic right. So we've done things in fabric like abstracting you know interactions with the certificate authority no need to run a CA client. We've done things like abstracting the ability to send transactions in right no need to run a SDK and collect all these different endorsement signatures. And similarly we've done the same thing with you know subscribing to events or understanding state changes in the network so no need for you to run your own you know polling client or you know right low level code to subscribe to events. You simply just tell the system, hey I care about this type of event and I want it to be delivered to this endpoint or I want it to be ingested by this Web socket topic. And we'll see all that in real time here, but just to give you an idea I've already gone ahead and then roll the user right so it's as simple as, you know, making a post call to you know slash identities right here. And here we can see you know the full msp portfolio enrollment certain CA certificate for this user right so we have an identity that we can use inside of the system. Alright, I've deployed a piece of chain code inside of this environment right here I just use the basic asset transfer chain code so we can go into this transactions endpoint right here, and we can invoke that chain code right so we can use the user that I just looked at right So user one, like I said the system creates a default channel for me so I don't even have to bother creating channels, and then I have a chain code inside of here right on the channel already instantiated called asset transfer. So we'll just go ahead and invoke the method inside of asset transfer called create asset, which we can see right here. So very straightforward method method just takes five arguments for, I believe it's a marble or some arbitrary object in here ID color size owner and appraised value so just a bunch of strings and integers inside of there so I think on this notepad right here I have a little cheat code. So we'll just go ahead and create like asset 03 think I already created 02 and 01 earlier. So let me just paste that in will call this asset 03. Share with me will make it green will give it a size of one will give it to Tomas and we'll give it a fake value of 10,000 right here. So this is how straightforward it is to just like invoke a smart contract or a piece of chain code using this, you know, piece of middleware that's called fab connect which is inside of inside a firefly right here. And what what we'll see is that rather than having to query a smart contract or rather than me, you know, grabbing that transaction ID and calling this path right here. What I can also do is create an event stream and then create a subscription against that object. And what will happen is collido firefly the asset platform these libraries, they will dynamically, you know, deliver these events to you. So this is one example of how firefly the asset platform and you know collido at large. We see it very much as an event driven system right you're just listening to things that interest your organization your application and then you're reacting to it. Whatever is on chain, whatever you could possibly care about, you just create an event listener in a subscription for those state changes, and then you can create, you know, serverless functions lambda functions etc to ingest those and react to those downstream. Very very straightforward and we'll see events littered throughout this demo today. I just wanted to spend a few seconds actually showing you the original, you know, not original it's the lower level of the stack collido blockchain as a service. And now we'll start moving up the stack and actually take you into the asset platform experience so shocker that this logged me out. So, give me a second I got to steal a password real quick. So let me log in and we will start sharing again. Well, I'm trying to answer questions in the chat so if you have any, just drop them in the chat and we'll try to get to them either during the talk, or afterwards. Yeah, and feel free to throw them at me Lana if I can help with any questions. Okay, so we are in the asset platform experience right now we're at the top, we're in that top pancake that we saw on the stack that Lana showed and that I showed. And there's six very very intuitive modules inside of here. You have a landing zone for all of your business logic. Right so this is going to be your source code whether it's tokens whether it's you know different bespoke, you know business logic if this then that statements. So this is where the firefly name spaces. So this is where your API's will get exposed this is where you'll have the ability to, you know, create those event listeners that I'm talking about to send private data back and forth etc. You have a whole suite of wallet configurations. And again just to reiterate as I mentioned, you're not limited to one flavor of wallet right so even a single user themselves could have a key and seven different wallets right if they if they wanted to. You could have an HD wallet you could have, you know, you could use that as your your runtime wrapper and you could have 10 HD wallets underneath it. If you wanted to have wallets for different lines of business right or if you're a gaming company and I want to have a different wallet for every game. So this is the entire NFT factory that makes it really, really easy to manage the, the DNA, the metadata of your NFT, and then very elegantly create what we call collections against those, and then programmatically, you know, allocate or mint NFTs against those collections. These are exactly what they sound like this is where you can create connectors to public ecosystems, or to collider hosted, you know, private or sidechain blockchains, and then IPFS again could be public could be a private collider cluster. This is typically where the metadata for an NFT is going to get stored. So I'm going to take you through this journey and I'm going to hopscotch back and forth between some action some applications so that you can see sort of how this process works. So I'm going to start by clicking on this builds tab right here and we're going to create a new build. And so what we'll notice and as I mentioned one example of the easy buttons that we see, you know, in the asset platform and in collido is that you don't have to write code right so we can create a token called hyper ledger and we'll give it a symbol called HL right here. This is going to be a non fungible 721. And we can give it characteristics right we can give it parameters mintable burnable I wanted to have your eyes storage. We see that the code is dynamically built for us. And if you're new to solidity if this is you know sort of, you know first three to six months of you in the space, you can port this code directly into remix, and you can try to extend it, you can add a new method or you can add a new event. And then remix is a wonderful ID just because it you know it'll dynamically compile and let the code for you and tell you you know where you're where you've gone wrong with your syntax or, you know your usage of solidity. So really, really straightforward. We can click next here. And now I'm going to actually create the compilation so I can create a new folder, call it HL again right here at that. And then we'll just park this build inside of the HL folder right here. And then we can create that. And behind the scenes what's going to happen is collido is running soul see on our behalf right we're running that compiler, we're going to generate that API and that bytecode, and it's going to allow us to start doing stuff with it we can deploy this smart contract onto one of the blockchains that we've connected to we can generate open API as we can start creating event listeners etc. So we'll start by just saying deploy right here as one example. You'll notice that there's all these custom actions that are available for you so you know if you want to do, you know, sort of logical naming based on your business or your UU IDs that you guys use. That's perfectly fine. You'll have sort of default entropy generated by collido. So we can see the success of that deployment right there we can dive into a block explorer to see the transaction, we can see you know sort of where all the source came from, but we can also see really really important low level details for this transaction as well. So if I go back to my sort of landing zone right here, my main page, and I look at our blockchain connectors that we have. And I go to the blockchain that we're hooked into, which is a private basu IDFT blockchain under the covers, and I go to the transactions, we can see the full lifecycle of that you know ERC 721 deployment. And this will start giving you a sense of what fireflies really doing under the covers. So this is something that you know a C sweet person might like to see right maybe a CTO would want to see more but you know just a high level business person that knows enough about Ethereum and the lifecycle of transactions just tell me tell me the main things that happened and tell me that it got onto the blockchain and that's good. But if you really are interested in all of the checks and balances and all of the little micro API calls that that fireflies making get past all the binary. We'll see here that it's doing all of the hard Ethereum things on your behalf right RLP encoding sequencing or nonce management, which is a really nasty one. It's been listening right coming back from the blockchain from the smart contract to make sure that transaction was properly, you know, executed and confirmed. And if you were talking to a public network, you could set different thresholds to say, for example, hey wait 10 blocks right let this guy get nested 10 blocks in before you give me that confirmation operation right there. So just a quick glimpse of like what Firefly does on your behalf inside of here. So that's an example of just using a collider template, where developers will ultimately get to is you may start using some of these templates and samples but you know eventually you'll extend them you'll have your own proprietary source code, and you can bring it into the system however you want to bring it into the system right so run your own VMs have your own change management system, push it from your machine push it from a public or private GitHub. All of those are possible as well. So it's not a one size fits all just like policies just like keys. Before I run out of time and I'm going to speed up because I want to make sure we can see the applications happening. It's worth noting that every single thing every button you can ever click in collido inside a Firefly inside of the asset platform, everything will have an API behind it. So the asset platform API becomes your one stop shop for all things you would need programming wise, it's your, you know, it's it's your DevOps pipe for all of those crud operations of creating namespaces or creating blockchain connectors or smart contracts, but then it's also your sort of landing zone to talk to the smart contract or, you know, to create event listeners for example inside a Firefly or to send private data to, you know, another organization. So this is you know when I referred to 1000 API is this is, you know, probably, probably roughly 1000 with the same authentication schema so it's again one stop shop for kind of all of the programming interfaces that you would need to, you know, build out a full stack application will come back to the wallets here in just a second namespaces will dive into the namespace so I'm not going to go through the whole ceremony of like how to create a namespace. The 22nd version is you need to create a blockchain connector either to a collido blockchain or a public blockchain, and you need to have an IPFS connector again public or private, you take those two objects those two configurations, and you pipe those into an IPFS connector to create a namespace, and now you can start doing work with that nice little API surface that that I just showed you right there. Okay, so let's start taking a look at the apps, this will be more fun. Okay, so what I have here is I have two different applications I have company one and company two, and we'll look at the mechanics of starting to tokenize some assets for example right. I have a gold bars demo right where in my back office right I have a database I have a portfolio of a bunch of bunch of gold bullion with different serial numbers different weights different, you know geographies etc. And I want to tokenize those so I can use them as collateral or so that I can do a delivery versus payment or so that I can fractionalize them for example, right all sorts of different fun things that you can do with, you know, any asset once it's been digitized. I have a new one, apologies for the slack. We'll give it an ID, I'll just say 555 right here, we'll give it a made up weight of 100 pounds. Again, gold bullion right here. Say it's in the USA, and I'll just say ABC for the nodes. So this is no blockchain transaction that's happening right here. Okay, this is, I may need to log back into this application, sorry. This is, this is just basically mirroring something that's inside of your back office. Okay, so again, not creating a not creating an asset on the blockchain, but basically putting a one to one representation of what's in your back office private database into your private database. And apologies, I think I need to, I may have this saved on the keyboard right here. Okay, I do. Alright, so let me start that again and just create a new asset right here so we'll say 444 again saves 1000 pounds in the USA and ABC right here. So we can go ahead and add that again, not a blockchain transaction just mirroring what's in your back office right here into your Firefly database. So now we can say hey, I have an asset right here. I want to do delivery versus payment against this allocation of gold bullion that weighs 1000 pounds. So we can go down to this deliveries tab right here and say hey I want to start a new delivery right. So we'll say six seven for the date right here and I'll say it's delivery be for example, destination, right, we're running a multi party consortium in another company that has the entire full stack of infrastructure that I can send private messages to they have an identity I can send assets to them. And so this is going to be sort of the first portion of that ceremony where I say, Hey, organization number two I'd like to start doing some business with you with, you know, this asset right here. So I'm going to go ahead and start that flow, and we'll see some stuff happening, right. Remember, the asset itself has not been tokenized yet so that's an important step that's going to happen in here. All right, so now the asset itself has been tokenized, and we're able to see you know the actual index inside of the smart contract we're able to see the blockchain, you know transaction inside the explorer, and we're able to see that you know publicly available right that I pinned against it right there. How did we get this information right this information just like we saw with hyper ledger fabric came back to the application via an event listener. So this is something that I care about right I cared about smart contract transactions against this address right here. So this application has a WebSocket client saying, Hey, tell me when things happen right I want to know the event back for you know this index right this item potency key that I've passed in. So that's an example of events coming back to the app right there. So now what we need to do is we need to use hyper ledger fireflies, private messaging rails. We need to talk to organization to and say, Hey, in return for you know this 1000 pounds of gold bullion I would like you know a million fungible coins right a million USD, right a stable coin that's paid to you know fiat currency right there. So I'm going to send a private message to the second organization, saying, Hey, do you agree on 1000 pounds of gold for you know a million stable coins and organization to can come in here. We have we have a few of these on sort of like auto accept, and they can say, Yes, I do accept that right there. And after they accept it, they'll push their fungible coins into that escrow smart contract. The, you know, a nishing party pushes their NFT into that escrow smart contract. And then if this is a real world delivery versus payment, you also have the ability to say, Hey, I'm not going to actually invoke the smart contract and unlock my assets until those gold bullion bars are in my vault right here or until, you know, I have the the deed to that piece of real estate or, you know, until the cargo container came off the ship and you know my signatures on that bill of lading or customs document. So you can put these these thresholds in there. And then ultimately what happens is after you've confirmed receipt of the real world item, both parties here, this is using a settlement contract under the covers. The parties are going to call an approved method inside of this settlement smart contract right here. And it's basically going to unlock the counterparts asset so that they can extract it. So this will in turn, I go back to the app sorry, this will in turn provide you know the token identity right the NFT the gold bullion to company number two. In return, right this person gets $100,000 not not a million dollars I missed a zero right there. So a very very straightforward but also powerful example of delivery versus payment. How do we marry on chain logic with off chain logic. And how do we sort of start implementing, you know, different classes of smart contracts without having to, you know, spend all of our engineering cycles understanding how to talk to that smart contract and so this open API interface for just speaking web to but having it translate to Web three can be really really powerful and an incredible accelerator for you know a lot of different use cases and you know a lot of different types of developers. So that's dvp. Let's go ahead and create another gold bar right here. I was going to say 666 but let's 777 and said, we'll say this one's 900 pounds this one's in Europe and XYZ or the notes right here. I'll just go ahead and immediately mint this one but I wanted to show sort of the two ways that you know an application can, you know, or the or the asset platform can, you know, say, Hey, just mirror an asset for me or actually create that digital asset for me immediately. And now inside the app we see, hey, I can do some more stuff with this right, I can move it. So let's think about a scenario where, you know, maybe we want to leverage a gas free side chain to do millions of transactions at you know high throughput at very very little cost but every once in a while we're going to have a real high value NFT, and we want that to exist onto a public network for example. So the asset platform in collido supports a trusted bridge right where all you need to have is just a connector, a namespace right which is the nomenclature into a different type of network a public network or another private network. You would supply these three parameters right namespace token pool, which is the indexing service and then the address of the identity that you want to receive it. So this will bridge private to private public to public private to public whatever what have you right there. So very straightforward to just you know cross blockchains to move these assets, even more straightforward to move the asset within the same blockchain fractionalize this is quite an interesting one. And this uses a example of a vault contract that we have so say we want to add you know more divisibility or fungibility to that 1000 pounds of gold bullion right there right, I want to turn them into you know very easily spendable fungible token so maybe we'll say, I don't know, call this one collido for example and KL and say hey I want to turn those, however many pounds I said into you know 1000 right I want to divide it by 1000 right there. So what this will do is this will actually pass ownership of the NFT to the vault contract, and then you know 1000 was passed to the constructor inside of there. And now we have you know a new pool of tokens that we're able to spend or transfer that are representative, you know, of that NFT, but now way more divisible. So if you click this transfer button and I can move that add attachment. This is also another example of you know, hey I have some rich information associated with this digital asset but you know shouldn't be public to all or it doesn't belong on the blockchain. So you can arbitrarily add you know any form data right to a smart contract or to a to a digital asset inside of the system. You can choose to move that attached data arbitrarily if someone requests it if someone purchase it purchases it if someone's entitled to it etc. Or you could just broadcast that data to the network and allow everyone to pull it down from IPFS right kinds of different ways to deal with on chain off chain public data private data. Okay, that's a kind of a whirlwind tour through. I guess a few example applications that you know sit on top of the asset platform service right here. Of course we can follow any of these hyperlinks and these will take us directly kind of into the asset platform experience. So we can go see you know the actual you know mint operation or the transfer operation. So this will take us you know into the actual method that we invoked on that 721 smart contract. This can get exposed you know completely publicly to your consortium you can put O off in front of this and have this as like sort of a quasi public block explorer. This can be just a completely private block explorer that's you know only accessible to you know sys admins that are inside of the organization. So this one's a flexibility on the service we call this KBI right here collider blockchain indexer. So that's one example. This token pool is another really important example of you know sort of how the system, you know keeps track of your information. So a token pool what it is is it's an indexing service for you know specific smart contracts and specific interfaces. So you can say hey create a token pool for me for this you know gold bullion NFT smart contract right here and start listening on block number. 50,000 for example, and what it'll do is it'll you know start at that block number and it'll replay every transaction. It'll show you balances it'll show you transfer mint burn approve operations. So you have you know granular visibility into whatever data that you need inside of that smart contract, you could extrapolate that same information just coding against you know the different event interfaces. This is you know kind of a convenience function because you know this this means that you don't even have to run like a you know API endpoint or WebSocket client you can just call this API. And then you can scrape whatever information you want off of it. So conscious that we're running a little low on time let me spend a few minutes on the wallets and a few minutes on the NFTs and then we'll see if there's any questions here. I'll spend just one minute on the wallets like Lana said right whole suite of wallets if you have a requirement get in touch with us and let us know. We can talk about sort of the commercial and engineering lift to bring you know another vendor into this ecosystem or you know a bespoke configuration inside of there. But the short answer is you can have as many many different wallets as you want. And like I said inside the HD wallets you can have you know as many actual wallet run times as you want as well. Now, one lovely sort of convenience feature inside of here is sort of the life cycle of these keys. So we can easily add and delete new keys. So we'll create one for Tomas right here Tomas one. And you have full flexibility over kind of the naming conventions right this can be an email address this can be a unique identifier this can be first name last name right. Whatever someone's logging into your OAuth system with this is typically kind of the syntax that you would paste against this URI right here. So we can add that key. And now when I'm calling the smart contract. I don't have to call it with the public address I can actually call it with this sort of syntax right here, meaning your application starts getting smarter and starts getting more automated. So Nick Gasky that logged into the system, sign the transaction on his behalf with slash keys slash Nick Gasky for example, right so very very intuitive if you add users, or need to off board users. And again, API underneath this so if someone comes in and they don't have a key programmatically create a key forum super straightforward. I did mention I would show the NFTs super quickly so let me just jump in here. I'm going to switch to company one right here their view of the world. So we can go to templates templates are the DNA of the NFT right so think of this as you structuring the metadata these are the files that you're reading and these are, you know the different parameters that'll be nested in the JSON object etc. These can be as simple or as sophisticated as you need them to be. Once you've created yep. Now I was just going to point out we had a question earlier about you know the asset types that are supported within the platform. This is how you would define it. So essentially you can import the different template types and define your asset per your use case so it's not opinionated as far as you know, asset types that we support. It's completely unopinionated just takes an arbitrary JSON or YAML object right here where you enumerate those parameters. And then you can even, you know, click this parse button and it'll show you a preview of what you know that template that you've created what the out, you know the outbound asset would look like right there. So I'll just I'll use that today for you guys. And again, you could have hundreds of these thousands of these millions of these right so you know as your designers add new different you know artifacts into your portfolio as you you know have new pieces of real estate come in as you have a new financial instrument, etc etc. You just programmatically create new templates. And what you'll notice here is that everything can just get automated right the end to end journey of you, you know, deploying a smart contract or adding in new NFT DNA is really just as simple as getting familiar with this API surface right here that we already looked at. So last thing I'm going to do is I'm just going to go into this collection that I have called robot examples right here. I've created a few already, and I'm going to just create another one so I'm going to create it against this robots template. I'm going to choose an image, just just example robot right here. And again, this is an example of where you can just store as many sort of off chain files as you want right. And this is hanging out in your private database so you know this can be, you know, financial information stock certificates KYC information, you know pictures of real estate. What have you so we could say robot for and now this allocate to feel this this is where if you're a developer you can sort of really really close the loop and get to the end of the journey. And then minting this asset directly. What we can do just the same way that we created those keys and the syntax inside of the HD wallet. So we can just allocate this to you know an alias that someone's going to use to log into your application tier, and then they will have the ability to say oh cool I got a new wallet I got a new asset in my wallet because I, you know, past this certification right where I, you know, I earned this new digital asset because I did XYZ right or whatever circumstance takes place. Sorry, we had a question on off chain data storage so how do you configure it based on your requirements for example, as three versus, you know, other solutions. So the databases themselves are completely sovereign to this stack right so when we say a stack right this is a dedicated VM this is like completely firewalled run times, all of the different pods and containers in there are solely part of your organization for your organization. One of the many things you get in there is a Postgres database. There's a Postgres for the state of Firefly. There's a Postgres for your private data, but that private database right can be swapped out for a custom database or cloud services database, something like an s3 or something like Azure blob container. So if that's already your landing zone for existing assets, rather than kind of you know, making an unnecessary API call to mirror that data into Postgres. Instead, you can just integrate that database kind of into your asset platform experience. The data won't persist that data, but we'll provide you the messaging rails and the pipes for you to move that data to other participants. So, in reality what could happen is I could have an asset platform stack with an s3 integration. I could have an asset platform stack with an Azure blob integration. And the only thing that's happening inside of kind of the Polido guts and the Polido infrastructure is that data is flowing via Apache Kafka from my s3 to Lana's Azure blob container. And then based on the application the business logic etc someone purchases purchases it requests it proves that they're entitled to it etc, you can arbitrarily, you know, send them that data. You know, prescriptive on when you should use what we are, you know, again I'll use the term flexible, we want to delegate and allow customers to use as much of their existing cloud estate and back off this infrastructure is possible. Robot type I'm just going to say metal and then I'm going to say 123 here just because we're, I'm already over on time right here. I'm going to take a picture of this guy. I'll create the NFT. And again, I haven't minted the NFT, but what I've done is I've pushed it into user ones wallet. So if I go to, I think this is the application for user one, we're going to find out real quickly. But if I go into this wallet right here for this user. Okay, already logged in. Let's try this again to new. Anyone second I get a copy to password but this will be the end of the demo. That's, that's really, that's really sort of the flow right there of, you know, sort of simplifying interaction with the smart contract. And, you know, being able to understand when you need to do a blockchain first transaction versus sort of what we'll call a lazy mint or an allocation transaction. So let me again log out of the admin login as user one user one right here. And if we go into here doesn't like my password. But we can see that now I have robot for that off chain NFT object that I created inside of the wallet. And now as a user, I have the ability to, you know, claim and mint this right. And say hey I want to claim and mint this thing into the wallet that I already have or, you know, maybe I want to use a metamask wallet or maybe I want to use a different type of wallet so again this this allows you to sort of deal with digital assets at scale. Not everything has to happen on the blockchain as soon as you want to create an asset, it can be delegated to users you can pre populate wallets with digital assets, you can do air drops, a whole slew of flexibility that's available here so it just gives you an idea. Yeah, go ahead please. Yeah, and I was just saying that there's practical application for this development pattern. So number one minimizing cost. And number two is like really understanding of when you want to mint assets. So for example we worked with a company called cold green fence on a Kroger use case where we minted coupons that could be dropped in folks wallets that might not have a bank account so lots of cool applications. Yeah, for sure. And last thing, and again thanks for giving us the extra time too much. We are an enterprise company right and so everything that we do is going to go through the cavity search the infosec departments of banks insurance companies healthcare companies. So, all of the different runtimes that are inside of the asset platform inside of the stack right there. As a system admin, you know as a, you know, keeper of the keys type for your company, you will be able to customize your own view of these different pods of their consumption of CPU of their usage. This can be for runtimes this can be specific on the blockchain. This is every view that you could possibly need sitting here inside of this you know Grafana Loki experience for user logs you know what's happening inside of your tenant what's happening on your blockchain. What's the health of your transactions. And you know, I imagine enough folks are familiar with Grafana you can you can customize the views you know sort of however you see fit right there. There's a sense of like, you know, what's actually running in the background, which is a whole bunch of things right there. So, I'll call it quits with the demo right there I think I showed most everything I wanted to see but I'm going to stop sharing and I'll let Lana put back up our contact information. You know any of the infrastructure you saw today, whether it's blockchain as a service whether it's the middleware component of Firefly, or whether it's some of the value add stuff that we put on top of it, you know would be valuable to your company, regardless of what stage you're at. Reach out and get in touch with us right we're happy to have a non non aggressive conversation we can go as technical as you want or as business oriented as you want. We're again in the business of wanting companies to get applications out the door, get them from POC to pilot to MVP to production. And, you know, again, our thesis is trying to lower that barrier of entry, while still using very sophisticated enterprise technologies. And so we love this space and we'd love to talk to you and, again, huge fans of open source and Firefly so incredible thanks to everyone for for sticking to the end of the call, even though I'm probably 10 minutes over at this point and big thanks to Ben and Tomas for helping helping facilitate this and huge thanks to Lana for sharing her expertise on financial services and capital markets. That's been really great. Thank you so much Nick also very cool robots. And thank you Lana. Thank you both a lot for sharing this interesting information for anybody that wants to get in contact with collider these slides that Nick and Lana were presenting will also be available on our webinar library just in case you haven't managed to, you know grab them from here. You're also welcome to reach out to us and reach out to collider team as well they're very helpful very responsive so I'm sure you will get your response quite quickly. And thank you of course everybody for joining us. Now, just before we leave just wanted to invite you to join our hyper ledger discord. We have a lot of real time interaction there you can also explore the channel related to fly firefly, and also to other projects as well. We also have some other upcoming webinars. So one Wednesday, June 21, we will be hosting a webinar about the universal digital payment network done by our member red day technology and their partner GFT. And then just a week later we will be hosting a webinar from Infosys about driving process transformation in public sector services using blockchain, and I would invite you to join us there as well they're going to be exciting webinars as well. Please go to our event event website to register. Thank you again everyone for watching and thank you so much to collider team. Thank you, Nick. Thank you Lana it was a very informative presentation and I can also see from the comments that our attendees have enjoyed it a lot as well. And as mentioned, just feel free to check back on our YouTube and our webinar library where we will be sharing both slides as well as this video. Thank you everybody and have a nice day. Thank you.