 Okay. You were live. Okay. So good afternoon. Good evening. Good morning. I'm not quite sure which location I mean, so this is hyper ledger and then I'm gonna hear on this meetup basically a speech on tokenization on enterprise ledger, which is I mean, not so much, you know, popular topic at the moment, but it might be getting into hype, going into hype, perhaps in a couple of months or even couple of years. So it's getting more and more important. So this is hyper ledger. If you're considering not familiar with the stuff. So it's basically an open community, mostly for consortium blockchains. There's one exception as well, that's hyper ledger Bezu, which has some public parts as well. But basically, there's not much like, you know, usually and facing even by the looks foundation. So, you know, it's just free of charge open source and community basis. So everybody is just welcome to contribute or share any knowledge or anything. So the agenda for today is something different. I've just built up my presentation step by step. So first, I will talk a little bit about blockchain evolution. I'm not gonna go very deep into the details like so I don't start from Bitcoin very strongly. And it's just gonna be one slide. Then I speak a little bit about tokenization generally some example tokenization use cases as well. Then we see token standards, very briefly, something which is token taxonomy. It's not so much right now in the public area or public space. And then I'm gonna give some, I mean, I have one slides on tokens, how tokens look like on hyper ledger Bezu and hyper ledger fabric. I mean, these are hyper ledger products or platforms. I got one slide as well on our free quarter and tokens, which is not hyper ledger, but basically it's a consortium of distributed ledger platforms. So it might be interesting. And one slide on interoperability, especially on tokens. And last but not least, I'm gonna have a demonstration. I will show how hyper ledger fabric implements one token. I mean, it implements several, there are examples for several tokens. I will show just one ERC 20 token. We don't have the time to go very deep into the details of other tokens as well. All together, I think it's gonna be like one hour. And at the end, we can have some time for general discussion or sharing knowledge, sharing XPS or any kind of stuffs. So that's the questions and answers at the end. So I would suggest, I mean, I would just try to make my presentation in one shot. So if you don't understand anything, then please stop me and then I will try to go into the details. But for longer discussions or sharing experience or knowledge on tokens, on consortium networks, I would propose the end the question and answers session. So let me start by tokenization. And I said it's a little bit like blockchain evolution. And I mean, surprisingly, I don't start with enterprise tokens, but I start just with the basic tokens, I would say. So the evolution looks somehow that way at the moment on the public area that we got somehow Bitcoin, Ethereum, and then from Ethereum, I would say the evolution of blockchain somehow splits into two directions. One is somehow the infrastructure layer. And I would say it's something which is an infrastructure innovation. And there are many very interesting infrastructure innovation in both the public space and the consortium space as well. It's usually like layer one scaling or layer two scaling or even something as just an answer that there's gonna be a record. And then it's on YouTube and you will find the record actually on the Hyperlegger YouTube page. So it is recorded as far as I know at the moment and live streamed as well. So back to the topic, we get something as an infrastructure innovation, which is very interesting and very challenging as well, including layer one scaling, layer two scaling, and a lot of interesting stuff as well. But what's perhaps more interesting or less technical at least, that we got something as an innovation on the application side as well. And basically, one of the basis of this innovation on the application part is like defining basic building blocks for an applications that are basically the tokens. So I would say tokens or tokenization is something which is an application side innovation. And it's getting to be standard, getting to be standardized. And this will be basically the basic building blocks of many different applications. But it's a conceptual layer. So it's not necessarily, you know, doesn't relate it very much to the infrastructure side. It's rather something which is a conceptual building blocks, how you can build up applications on top of blockchain. So this kind of innovation going a little bit to the application side. And the, I mean, the most famous example, of course, you know, like NFT and DeFi, that's the public space. So for instance, if you, I mean, NFTs, I would say it's like a little bit hyped at the moment. But if you take a look on like DeFi, DeFi basically consists of many applications and all of these applications I build up with the help of tokens. So we got something which is basically, you know, I mean, from an abstraction layer over smart contract. So basically we get like token, the API smart contract, but smart contract is almost like infrastructures, infrastructure and token, I want to slide, you know, conceptual building blocks, one layer above the smart contract realization. And basically applications like, like at DeFi are built up with the help of tokens. And of course, I mean, this is public blockchain. It's very much hyped at the moment. But it looks that way that so customers getting used to these tokens basically in the public space. So they're getting used to that, here we got something as a fungible token, we got something as a non fungible token. And it looks that way that basically as they, as they already have these tokens, even at building up like, like very classical consortium blockchain applications, they want to do use these tokens. So it means that tokenization in at the, at the enterprise blockchain skin is not so much, you know, hyped at the moment or not so much, you know, popular, but it's getting to be more and more popular. And again, so as basically customers getting used to, to having these, these concepts, like different kinds of tokens, they know what's the different between like fungible and non fungible tokens, they want to use basically the same tokens in enterprise ledgers as well, and in enterprise blockchain applications as well. So for these reasons, it's pretty much, it's very much interesting to speak about like tokenization and how tokenization can be supported on on consortium or enterprise blockchain applications as well. So there should be one arrow here, like tokenization, and there should be something here as, as, you know, consortium blockchain applications, and then token based consortium applications, which still doesn't exist, but I mean, it's, it's coming. So basically in the, in the nearest future. So speak of tokenization, I mean, that's the, I mean, you know, I mean, that's the, that's the basic, basic roadmap. Usually we distribute like, I mean, I mean, depending if you're, if you're very deep in blockchain or just a high level, if you're just a high level, we distinguish like three different major, major tokens. If you're very deep in blockchain, then, then you, then you differentiate like, I don't know, 25 different kinds of tokens, but let me just start with the three major ones. So basically we got like the two major categories are like fungible and non fungible tokens. Fungible token is like, so basically you get a token and two tokens are practically identical. So practically, they are the same. They can be used exactly in the same way in same circumstances and so on and so so fungible token is like money is like currency. If, if you got your, like, you know, 10 euro notes, then one 10 euro note should be actually the same as another 10 euro note. So they shouldn't be different somehow. So it means that if you just talk and tokenize like, like euro with like CVDC or something, something similar, then basically one token, one fungible token should be actually, actually the same as another one. So it means that like, you know, I mean, these tokens are identical to one another. It's like the exemplary case is cryptocurrency, but it's in a public blockchain. But I mean, like, I mean, supposing that, you know, CVDC reaches actually the production level, I would say that fungible token will be like of CVDC, for instance. The other category, let me just check if there's like a chat. Yeah, I mean, I mean, you can say that, but so I mean, as a usage, basically in all kind of, yeah, like, like you can say that, I mean, it's physically, it's one paper is different from another one. But you know, I mean, tokenization is an abstraction, basically. So in all usage situation, you use one 10 euro note as another one. So it's more or less the same. Because it is, I mean, I mean, even if you say coins, you can say that it's in a physical way, one physical token is different from another one, because it's a different physical object. So, you know, in this sense, fungible is basically an abstraction, which might not exist purely in the physical world. But I mean, it's a good analogy just to imagine as, you know, as a currency, basically. You know, I say cryptocurrency, I mean, you might as well discuss some cryptocurrencies are not totally fungible. So like Bitcoin is not totally fungible because, because I mean, I mean, you can you can track actually the money and be like a transaction graph analysis. And in this sense, it's not fully fungible. It's like Monero or Zcash are basically fungible cryptocurrencies. But again, it's just an abstraction. So it might not, you know, I mean, fully 100 percent or very blue overall, but it's a good structural framework differentiate tokens. So the other token is like NFT, it's a non fungible token. The idea from non fungible tokens that each token is different. So like one token is totally different from another one. It's again, it's, it's, it's an abstraction as well. But one of the example is like, let me just imagine, we tokenize, we tokenize basically art, like we tokenize the Mona Lisa and, and we tokenize like, for instance, Picasso. So in this sense, because when Mona Lisa will be totally different, totally different tokens. So that's non fungible tokens. And it's pretty much hyped at the moment. And we got like hybrid categories as well. So hybrid categories of tokens is something in between which is, which is partly fungible and partly non fungible. So basically, in this category, we get like categories of tokens. And in the category itself, these, these tokens are fungible. So they are, they are similar to each other or they are identical to each other. And between the categories, they are just totally different. One example for that is like, if you tokenize a game, like a role playing game and where you have like assets, like, you know, swords and shields, for instance, these are big, two big categories of tokens and basically in one categories, the tokens, the assets are the same. So you can say that like, once what is, is exactly the same as another one and one shield is exactly the same as another one. But between the categories, it looks that way that you can't really exchange them. So you, so once what is not exactly the same as one shield and one shield is, is definitely not, not the same as, as, as a sword, as for instance. So that's like hybrid tokens. Let me just give some, some example. And these are some of the examples originated firstly in the, in the public blockchain world. So for fungible tokens, we got like the cryptocurrencies. But again, you can say that if you don't like cryptocurrencies, then again, use just CBDCs. We can say stable cryptocurrency, that's pretty much the same. It's like platform tokens, like Ethereum. It's still public, but like if we just, you know, I mean, imagine like securities token is tokenized stocks or tokenized bonds. It's something which is a token. And you might as well imagine actually in, in, in like, you know, in a public blockchain as well, there are already initiatives for this as well. But it's typically something which is, which is relied on consortium ledgers between banks, not quite with a hyperledger fabric, but hyperledger fabric does us, for instance, but like there are certain examples with fabric and with like, with like IR free corner as well. So these are like, you know, tokens on enterprise ledgers representing kind of, kind of let me get more or less in public, we get some governance tokens and like tokens representing actual resources. These are what basically are like public fungible or public fungible examples. Just close basically this chat because I mean, there are some, some questions that I would rather try to answer at the end of the presentation. Otherwise, let's just change topic to, too often. So let me add just examples for, for non fungible tokens. Examples for non fungible tokens is for instance, like tokenization of physical art. It's like Mona Lisa and Picasso. It's, it's, it's very much hide like tokenization of virtual art. It's mostly happening on public blockchain, but like, you know, I mean, tokenizing the physical art can happen actually on a consortium ledger as well, like with different galleries and so on and so on. It's very much hide like, like, like the virtual reality games, especially like metaverse and stuff like that. So like, you know, I mean, selling virtual properties or any kind of stuff on these games that are like virtual cards as tokens in different games in different strategies games, like asset tokenization in role playing games. So gaming is a very, very strong application. You can do something as physical property tokenization. It's not so much hide because it's, you know, I mean, practically it has some legal problems. So legally it's just not so easy to tokenize or perhaps partially tokenize basically like a house and then sell it. But like, for instance, one such use case is I would imagine more like on a consortium ledger basically. And it's again a public blockchain like tokenizing funds in the five protocols and then like crypto collectibles again, that's the most public club use case. Nevertheless, sometimes there are some possible applications on consortium ledgers and I'm sure there's going to be more in the future. So these are like example tokenization use cases. So going a little bit to the details into the details. So we get, I said we have like three different kinds of tokens or if we want to go very deep into the details, we get like, I don't know, 30 or 40 different ones. So if you really want to take a look on the different token, token, token possibilities, I would say one idea and that's the most common way is to take a look on token standards. And these standards are initiated by Ethereum. So they are like ERC, ERC, Ethereum change request basically, that was somehow the original name. And basically, I mean, the whole world is getting used basically these concepts, even if it's not used in Ethereum, but somewhere else. So we usually say that like ERC-20 is a fungible token, ERC-721 is an NFT token, ERC-1155 is a hybrid token. We usually say that even if they are not exactly on Ethereum and even if they are, they doesn't really look like exactly as the original standard proposition. It's so important actually to look. Basically in Ethereum, there are like, I don't know, at least like 20 or 40 different, you know, like ERC proposition, they are all related somehow to tokens. Nevertheless, it might not make sense to use all of them overall. So I mean, it's practically a good idea to say like ERC-20 is a token which has some functionalities. And even standards basically describe the major functionalities of the token. That's practically the interface. And it might make sense like to use ERC-20, not just with Ethereum, but overall basically. There are some token standards in Ethereum however that are not necessarily the best idea to use somewhere else. So like ERC-233 is like an extension ERC-20 token that protects from like accidental transfer of Ethereum and of tokens of ERC-20 tokens as well. So it's a good question if it's such a standard that's possible to use somewhere else or is it kind of a stuff which is very specific to Ethereum and shouldn't be actually very much considered like on other ledgers as well. There are like ERC-777. It's again, it's like you define operators to send and receive tokens. It's again a good question. How much it is very much on focus on Ethereum and how much it is something which can be basically imagined somewhere else as well like on a hyperledger fabric. I'm not quite sure if it would make sense actually on a hyperledger fabric basically such a thing. Again ERC-1155 is a hybrid token. It's definitely makes sense somehow on consortium ledgers and on enterprise ledgers as well. Perhaps not one to one but just major functionalities or major interface. There are some other things or other token standards that can be considered basically in like I mean enterprise or consortium ledgers. It's like ERC-377 is basically something which is a recurring payment standard. It would make sense if there's really payment in your ledger which might not be the case but we got like standards for security token basics or security tokens or even for sec compilant security tokens. These tokens have like the functionalities for key YCs and stuff like that. So they are certainly something or standards that could be considered basically on different ledgers as well. So one starting point to get tokens I mean from somewhere to the enterprise and consortium word is just I mean considering the ERC Ethereum token standards and taking a look if they are able to like enterprise or consortium ledgers as well. So that's the most common way. There might be another way as well which is not very much used. It's pretty much like a niche product. It was a good initiative for some reasons it is not very much used and that's the token taxonomy framework more specifically. It's basically an attempt to define like on the region of tokens like different tokens with different properties and different behaviors and attributes and it's just a definition. So they try to do it somehow in a totally blockchain agonistic way. So again it was a good initiative. It is not widely used. So I saw like you know I mean in like 20 white paper you see like one where like token taxonomy is even considered basically. But nevertheless it's an interesting idea. It looks basically that way that token taxonomy framework has a kind of a calculus. Calculus is you know like a syntax basically that looks mathematical even if it doesn't really have semantics behind or form semantics. What you do basically is you can define like basic types it's like fungible and non fungible tokens. You can define like like behaviors or behavior groups. So like you know transfer for instance or or minting or stuff like that and you can define properties on these tokens. And basically it looks that way that your token definition is described somehow. Again it looks looks to be a little bit like formal and mathematical. So you got like definition for for like the base types. You got like like behaviors these are the behaviors. So like I'm not quite an expert of these syntax but you know I mean if you have like minting functionality then there's that's kind of behavior that can be seen here. And then you can have like properties as well like I don't know in NFT like if you have like a link to an external storage where basically your digital art is stored that's kind of a property basically. Surprisingly there are some platforms that the try I mean that start somehow to support the stock and tax only framework. So one thing that might worth looking is basically that's a visual studio extension. And in visual studio you can you can see like so if you just start visual studio and basically take a look on extensions you find like two or three token text on the same extension. This is not installed. You can't do actually very much but I mean I mean you can get a feeling at least how it works. So you get like you know I mean a lot of like token artifacts. So it's like this is like a fungible token. You get like fractional and fungible token. It's like singleton which is kind of an NFT which is exactly one and so on and so on. So get many many basic types basically. You get like behavior so it's like bear neighbor and then clicking on bear neighbor you see exactly what bear neighbor means like delegable I don't know. It's something that I know and so on and so on and so on. And it looks that way that I mean you have behavior groups as well and you have like properties that are somehow separated into property sets. So like you have a couple of examples here like properties related somehow to carbon emission core carbon mark attributes and and stuff like that. So the idea is somehow that you usually have a token designer as well. So if you just want to design a new token I just start a new token. I hope it's going to work. It sometimes I mean crashes my visual studio but basically you can somehow design your token in a way I mean the drag and drop. So like you want to have a token which is a fractional fungible token whatever it means. So that's like your base token and you can have some some carbon emission properties on that. So we have carbon emission and then we want to make sure that we can burn this token. Again it's not working at the moment but drag and drop sometimes crashes for me. It works. So this is bear neighbor and then we can have like I don't know which is the attribute basically that I know that we have like whole table, indivisible, there's something as ish label or mint table perhaps that we have some ish label. I hope it's gonna work. It's gonna work. So like this is a token definition and then there's a formula as well. So this is the formula of your token definition and again so at the moment it's it's nothing more than basically kind of formalism how you can describe tokens or even build these tokens into into higher office as well. But as far as I know there are already examples for that that based on this token definition you can you can generate code like you can generate like solidity code for instance and and based on the token definition you can really create your smart contract. So it's again an interesting initiative. It's it's not so much hyped. I hope it's it's gonna it's gonna be further developed in the future. So that's basically token taxonomy framework. And let me see some examples of how like hyperlegia or consortium support basically tokenization and I have like two hyperlegial examples. The first one is the easiest. That's hyperlegia Bezu because hyperlegia Bezu is is basically a consortium ethereum technology platform. So basically what you do is is you build up consortium ethereum networks with hyperlegia Bezu. It's a client. It's an ethereum client basically. Mostly for I mean consortium scenario there's a possibility to to run actually public networks on top as well. So hyperlegia Bezu is easy. I mean I mean you just you just get your solidity tokens, your solidity token implementation and basically you can you can use it one by one. So without any modification. It supports I mean the ethereum virtual machine. So you can basically run on hyperlegia Bezu any kind of token any kind of ethereum token that you want. Just mentioning perhaps that hyperlegia Bezu gives you like two ways of somehow further developing these tokens or or adding like additional functionalities for these tokens. One is kind of an advanced privacy and the second one is kind of an advanced authorization. So advanced privacy looks that way that basically I mean in ethereum practically everybody gets the transaction. So every node can basically validate your transaction but it's pretty much a privacy problem. It's pretty much a privacy concern. So what Bezu introduced is like a privacy group. A privacy group looks that way that only only special specific nodes in your ethereum usually consortium network gets your transaction and only special nodes validate your transaction and basically it looks that way that there's a public and the private state as well. So if you have a privacy group and not all of your nodes basically get the transaction then the changes of your transaction are practically recorded just in a private state. So not in a public state. But again it gives you kind of a kind of a privacy. As far as I know there's two implementation. One makes sure someone is a cryptographic implementation and another one is a physical privacy. Same physical privacy. I mean exactly denotes that should get that transaction. I think it's like with an additional technology called tesera if I'm not mistaken. But again it's a physical privacy. In a cryptographic privacy all nodes get somehow your transaction but there are but it's an encrypted transaction and only some of your nodes gets the possibility to decrypt it basically. So that's something that you can consider. You can have your tokens on Hyperlegit Bezu again just any kind of solidity ERC anything implementation but you can consider to somehow enchant them with like advanced privacy scanners or options. The second one is called kind of an advanced authorization. It looks that way that you can you can grant access for an account for instance. You can do it on several ways. You can do it on a node level. It doesn't bring much basically I would say. But you can do it in a totally decentralized way as well. So it means that there's a special governance smart contract running on your Hyperlegit Bezu consortium network and you can grant access for specific accounts or deny access for specific accounts on that smart contract level. And basically the smart contract is considered in the mining. I mean it's not mining it's validation basically but it's considered in the validation and the block creation. So practically that means if you do not grant access for an account in the smart contract then this account I mean the transactions from this account will not be mine very specifically. So that's another thing that you can consider with your basic tokens. So that was Hyperlegit Bezu and of course I mean the big platform on Hyperlegit that's Hyperlegit Fabric. So Hyperlegit Fabric has many more than one possibilities for realizing like different tokens. And these are the perhaps the most important possibilities. There are implementations for ERC 20, ERC 721 and ERC 1155 that's basically in Fabric samples. If I find Fabric samples that's Fabric samples. Let me just bring it a little bit bigger. So you can find in Fabric samples these are like a specific way of these tokens or specific implementation of these tokens in Hyperlegit Fabric. I'm gonna show at the end the ERC 20. It's again not exactly the same as a solid ERC 20 token because in principle the general idea of Hyperlegit is different. I mean the general structure and the idea behind is different from Ethereum from Solidity. So for this reason what you see here is not exactly the same as a solid ERC 20 but something pretty similar. And you find like 721 and 1155 as well and basically this is a community project so I mean other tokens might come as well. So that's one important thing in Hyperlegit Fabric and there's like two other initiatives as well that might be interesting in terms of tokenization. So first Hyperlegit Fabric is an account-based ledger and their account-based ledgers are not so easy sometimes in terms of privacy. But the other ledgers as well it's the UTX ledgers the unspent transaction output based ledgers like you know Bitcoin that can be much better fine tuned in terms of privacy. And the idea is something similar as speak by Zcash. So in Zcash you use like UTX based ledgers and you get some advanced privacy constructs like zero knowledge proof and it gives you a pretty good privacy basically. So for this reason I mean the same idea was I mean is initiated somehow on Hyperlegit Fabric as well. So there's basically something as an UTX ledger you can find basically the token UTX ledger as well. So there's the unspent transaction based kind of implementation or initiative of tokens as well in Hyperlegit Fabric and I mean the developers try to bring somehow the same privacy guarantees to Hyperlegit Fabric that is available in like in like not in Monero but like in Zcash. So mostly we Monero uses like ring signatures but like you know I mean I mean in Zcash you get like like like zero knowledge proofs. So basically the same ideas are being developed here at at the token UTX model as well. So that's one interesting project and there's another one interesting project as well it's called the token SDK. It looks that way that there are the so-called Hyperlegit labs and like I'm not quite sure if I have that open but I have this open. So Hyperlegit labs are like small projects basically in Hyperlegit so not like big platforms or not or still not big platforms perhaps they're going to be big platforms in the future and there's one interesting lab which is the Fabric token SDK. This is the Fabric token SDK and Fabric token SDK tries somehow the the abstracts of the definition of a token from an exact implementation. So the guys try to do kind of a general framework where you can define and somehow I mean partly implement as well tokens as well but as much as much as possible in a in an implementation agonistic way or even even in a blockchain agonistic way as well. So the idea is something similar that you can define tokens for the first time for Hyperlegit or Fabric but like you know I mean I mean you can define which which are the privacy guarantees that should be available for your token and then based on your privacy guarantees it can be decided is it something which is deployed to an UTX ledger or or you can use something which is which is a totally standard Hyperlegger Fabric like ERC-20 implementation. It's a modular architecture so I mean the idea is that on the long run you can define tokens but these tokens are not only developed or deployed to to like Hyperlegger Fabric but basically to some other blockchain as well. So it's like as far as I know there's there's only some single or being developed to be cross-chain stop. So it's tried to be some kind of a general abstraction framework for tokens but you know not just a stock and tax only framework which is more like a rather theoretical and description scene but basically the idea is here that anything that you implement generally can be run basically directly on one or on several consortium blockchain ledgers. So that's stock and tax only sorry that's stock and SDK it's a very interesting initiative. I was checking a little bit details about other Hyperlegger leds or Hyperlegger products as well like Hyperlegger sol2s or Hyperlegger I don't know I didn't find much of a condition in this project so I'm not quite sure if they're doing perhaps there's some initiative I just didn't find it. They are not so much in in Hype. So last but not least one interesting idea which is basically not Hyperlegger but it's an enterprise ledger. There's like token frameworks in R3 corridor as well that's called the R3 corridor token SDK and I mean actually corridor has basically a totally different approach than most of the blockchain platforms. It's not even called blockchain it's like a distributed ledger platform and basically the idea is here that so first it's not not decentralized but you can define how much you want to centralize or decentralize your use case. Basically UTX is working in contracts so contracts in terms of real contracts and not not necessary smart contracts and basically the ledger is kind of an evolution of these contracts in a UTX model basically. So they define I mean it's very much you know in a financial and banking specific stuff so like an R3 corridor token is basically something which is an agreement it is regarded as an agreement between an issuer and the holder it's like a contract and not smart contract but like almost like a legal contract between an issuer and the holder and basically this agreement is considered as a liability from the issuer and it's considered as an asset to the holder. So you know I mean you can't live in R3 corridor without like WN3 accounting all of the concepts try to get this idea. So nevertheless even in R3 corridor you can you have the token SDK you have something as Fungible tokens you get something as Non-Fungible tokens as basically the cord ledger is like the evolution of contract you can have something as ever with UTX so that can really be modified or extended on the long run and there are like Non-Fungible tokens it's like you know like like an NFT that changes perhaps only the holder that's like a Non-Fungible token and you get like word force and processes as well. So first like define issuers, redeem or sell at different kind of tokens are basically in cord ledger in your logic you can even define who should validate basically your contract or your transaction so it's a little bit like a more specific more special and a little bit like you know little bit different ideas than than general blockchain platforms but nevertheless you can find a token SDK in R3 corridor as well. So last but not least I got some some ideas for interoperability so as basically there are many blockchains having like different different tokens or different type type of tokens it might be an idea how the how they can be I mean you know work together just interoperability bit and then for blockchain interoperability there are like two examples in terms of tokens and the two major examples one is like doing atomic cross-chain swap and the second is like something as a cross-chain token this is from theoretical point of view you can find on the right side that's an atomic cross-chain swap so it looks that way you want to send one token on one ledger and another token on another ledger so basically what you do you do not really send these tokens but you initiate something as a hash time lock contract which is basically a transaction which is not fully executed but only halfway executed and then you initiate an hts and another ledger as well so then a halfway executed transaction and basically you get something which is a which is a hash lock and a hash key so you initiate these halfway transactions this hts is with a half with a half of a hash hash lock and supposing that you have the key you can unlock this transaction with a key and if you unlock one transaction with a key your key will be visible on one blockchain so the other transaction can be unlocked as well that's the idea and if you don't unlock these transactions there's a there's a timeout that expires so they will be rolled back practically that's like atomic cross-chain swap very briefly some are more complicated under the hood and the second idea is in terms of blockchain cooperation and tokens that's something which is a cross-chain token and cross-chain token looks that way you get we get like two blockchains the two blockchains having like tokens i mean native token in one and native token in two so what we do basically is we somehow lock token one token or several tokens on one blockchain we give basically a cryptographic proof that this token was locked to another blockchain somehow with a type of smart contract or some other things and as soon as it is proofed that tokens on one chain is locked we can make a new token practically on another blockchain it's like you know the classical example is red bitcoin where we practically lock bitcoin somehow on the on the bitcoin blockchain and then as soon as this lock is is proofed basically we mean one bitcoin on the ethereum network which is basically a red bitcoin and i mean the other direction is pretty similar so if you just you know i mean burn the token on one blockchain then it can be unlocked on another one so that's like cross-chain tokens i mean certain implementing such things are not so easy so there are some initiatives for for for general interoperability platforms between different ledgers and especially between different enterprise ledgers and two initiatives from hyper ledger one is hyper ledger cactus that's that's a general modularized interoperability framework it has or it plans to have at least i guess there's some implementation as well both the retomy cross-chain swaps and cross-chain tokens as well anyway just one so basically i mean if you if you want to do interoperability between blockchains in terms of tokens it's not so easy necessarily because i mean what you have to to pay attention that basically the double spending between two blockchains should be avoided as well so it's a little bit like tricky but like you know i mean these two mechanisms are basically capable of of avoiding like double spending even between between ledgers as well there's another initiative as well it's a hyper ledger weaver that's that's a hyper ledger lab and it has basically an interoperability toolkit as well it's it's it's it's still a lab not a full project but it might be further developed in the future so that's the presentation and now i can show some demo or i would propose let me just have like a three-minute break and if there's like you know i mean very specific question that i can answer in three minutes so there are many questions um so not quite sure if i if i should start answering the questions right now or shall we have basically the the demonstration and let me have that at the at the end so i would i would say the following proposition if anybody anybody having like a very you know i mean in a one-minute question or something uh i can answer otherwise for for longer questions i would propose first that i show the demo and then and then at the discussion session we can cover these topics so anybody having a very very brief like one-minute question so there's one new message yeah i mean as far as i know bezu is already the protein production even in even in public networks as well so like if you go to to public ethereum nodes then like seven percent of the of of all the ethereum clients running on hyper ledger bezu so yeah so uh let me just take a look uh it's a good question how i can so what i'm gonna show is basically we have something as uh as an erc 20 token uh that's in hyper ledger fabric and let me just show demonstration on on this erc 20 token it looks that way it's in fabric samples um so let me just try to show the code basically what you have is is a folder uh with your erc 20 chain code and there's a read me as well i would just try to start the first version of the read me unfortunately this is like uh this is like you know i mean hyper ledger fabric so doing anything with hyper ledger fabric is always like i mean complicated so first i would just start my network it looks that way that if you go to uh to this erc 20 token then basically it works with the test network uh you get in fabric samples basically a test network as well it's pretty well documented anyway so if you can't follow me uh you can follow basically the description so there's something which is a test network i start the test network the test network looks that way that basically we get like two organizations uh we have it certificate authorities so each organization having a certificate authority there's a one one node ordering service uh which has a certificate authority as well and there's a cli as well so practically that's on uh the second step is to deploy the smart contract so what i'm gonna do i mean as i started the network basically i have created a channel so what i'm gonna do is that i will deploy this example uh to the to the channel so that's the erc 20 token on the channel uh not question if it's too much but yeah it looks great so basically it's the deployment process and i i don't know what's the best way of you know i'm doing demo with hyper leisure fabric until everything gets done and gets configured it's always a little bit complicated so certainly i got some some parameters um it looks that way um so fabric is is basically um a little bit different like like like a ct view uh so so the idea looks that way that we get like organizations and then different organizations you know it might have might have different roles can do different things so like in this csc 20 example uh we get two organizations we get two organizations as well in the in the in the test network demonstration uh and the organization one organization and the organization one is like having the like a central bank so they can meet token and organization two can transfer token but organization two shouldn't have something as you know i mean token or burn token so that's something which doesn't really exist in in in in an ethereum implementation um but again it's it's kind of a i mean uh uh hyper leisure fabric specific uh version of erc 20 so what i have to do basically is that i need to register identities identities are hyper leisure fabric are not the easiest to do because everything is done by public key infrastructure and then we get like some some certificate authorities issuing x509 certificates and these are practically the identities these are the users so it's just not so easy as an ethereum that you know i just just generate a private key a public key and that's all so what i basically did i generated one identity and that's gonna be in pure organization and in pure organization i would say that will be somewhere else users so that will be basically here uh we get organization one and we got organization two and in organization one i got users i got one admin and one user one that's generated automatically and i just created a mean there so this user identity can mean practically token uh that's the idea i mean any kind of uh user identity here in organization one can mean token but i just created this one specifically that this one can create token so that's the first step then what i should do basically i should create a user on the second organization as well so i have just a second window uh it's again some setup i have to create a new identity this new identity will be the recipient practically so i created a recipient identity uh it's a little bit complicated it's basically it has two phases one with registering with the certificate thing authority and the second one is enrolling with the certificate authority so basically at the end of the day what i'm having here in organization two there's a recipient uh identity as well and i get all the you know i mean certificates here and this recipient will get practically the token so having that uh let me just mean some token it's again thousands of uh of parameters that i need to set but as soon as they are set i can issue basically one call uh which is basically kind of a chain code invoke uh and then what i'm gonna do is that i call one function which means basically 5000 token to the current user i mean i just set the current user basically with this or all of these parameters but what i'm having here is that there's another chain code i can ask how many tokens i have uh there's a client account balance because it looks that way that i mean the the balance basically an address but the address is a little bit complicated to get here so i get another function which is client account balance which gets the balance of the of the current of the user and it's not really logged in uh with the the parameters uh that i set basically i just referred uh to the to the x509 certificates that i created so basically that's the current user in a way just to make sure i'm not i don't cheat uh let me just try to mint 5000 more tokens and let me just take a look if it's like 10 000 it it looks great it's it's like 10 000 tokens so i got basically tokens i minted it so let me just do something as transferring these tokens um what i'm gonna do i'm going to the second window uh it's something which is set up or i'm going to set up to organization two so this one is organization two it's a little bit like complicated but i can get the client id now it's for some reason it doesn't work yeah just a second so i hope it's gonna work something went wrong but anyway so you saw basically this was this was one transaction be careful Daniel your host you can mute people if you need to okay awesome okay uh so we got some technical issues uh basically uh so yeah exactly so i'm guys if you be so kind if it's not related to the meet up okay awesome okay so let's continue with some after some some technical issues please that's not appropriate we'll need to remove you from the start okay so let's try to continue uh basically uh so react some technical issues but anyway so at least at least one uh one transaction was working so you can see basically i can mean basically tokens to one uh to one ledger uh to one to one account so just see all right so just taking a little bit the the code itself um so we got like you know chain code this chain code is in is in is in go so we got like you know i mean means uh we get the functions like transfer uh burn uh we get like transfer form and stuff like that this is transfer and we get like transfer form um but perhaps interesting um is like the future that i mentioned so if you have mint uh basically i mean the whole authentication uh works uh with like the uh with like the membership service provided ids and the identity identity ids so like you know if if i mean uh anybody who is in organization one uh can mean so basically what i'm doing is is that i'm checking what's the membership service provider id and if it's organization one then i can mean i'm just not not authorized i don't don't go pretty much deep into the code but basically another thing is uh it's again membership id uh basically for burn and then if you use something as transfer then it looks that way that it works with the client identity so if i just create basically i created with with the certificate authority a new new identity a new x5 or nine certificate practically then then this this identity gets basically the token uh so that's the account and then and then the whole code basically checks if that account having the necessary number of tokens and then basically uh the the the tokens are transferred from from one account which is one one like client identity to another one so that's the major idea uh basically and we got like transfer balance of we got like some some client account balance uh which uh takes a look what's the logged in practically logged in identity and stuff like that so that's basically the code and i would say uh so that was basically the official part of my presentation of my demo it's half levered unfortunately but you know i mean that's the that's the usual demo case so i would say that's the uh that's the uh that's the end uh and then i can take the question so where did i where did i stop you can take attributes for fungible tokens yeah i mean so so again um so this fungible and non fungible stuff that's that's like an abstraction so it's a good question if there's really something which is fungible and really something which is totally non fungible um we might argue actually so you can take something as as attributes as well but i mean if you distinguish attributes basically might not be really fungible actually interested more in change or that's its structure so that was the demo i can't go at the moment very much deeper it would basically need something which is which is another uh you know i mean meet up uh to prepare uh as as as as you see uh as you see then then basically uh yeah pretty much here and the end at the end of the presentation uh is digital art first practical use case of NFT uh yeah i would say yes i'm not quite sure i think the first NFT was was still actually on a on a bitcoin network and it it was it might be i'm not sure it was i think it was it was virtual art it was like in 2013 or 14 if i'm not mistaken and the and the second one is basically like like crypto crypto pranks if i'm not mistaken that's like the second use case they are all or like physical sorry virtual art virtual arts so as far as i know yes uh that's basically uh yeah that's with NFT an owner can only own one at yes so i mean i mean you can you can own more than one NFT uh that's the logic uh basically so you can you can own uh any any any kind of any number of NFTs uh that you want that's already answered sorry i'm just uh from a receipt of a ticket so aside aside from digital digitization how NFT differs from receipt of a ticket yeah i mean it's a good question i mean it's the question how how do you consider ticket uh so if you consider like a physical ticket it differs pretty much from an NFT like you know i mean if i if i consider like a concert ticket it it might not be an NFT basically um you know i mean there are like thousands of of tickets for a concert that might be actually fungible in the category so they are not so much an FT and then it's like a little little bit like different different questions but yeah basically you you digitize kind of a poker jet on i usually say and that's what's running on the blockchain that can be sold that can be traded that can be used in in any kind of practically uh applications and that are basically integrated with each other so of course we find a certain fashion owner something uh what's the name of the of the extension so the extension that we saw here is basically if you just uh go in and token designer if you just look for uh for for token designer token taxonomy framework you you get you can you will see like three designers if i'm not mistaken so these are the extensions yeah exactly so what i was using here is the iwa token designer um you've got like two designers for for neo which is a blockchain as well so i didn't try it and i'm not so much familiar with neo but it might happen that actually new manages to to generate quotes directly uh with the help of like the token taxonomy framework um yeah it's it's all right so basically this token taxonomy framework doesn't run on any kind of ledger for the first run there are like code generators uh or the idea is using like code generator and then you just define your your token framework model generate code and these generators might be a solidity that you can run run basically on like like like ethereum compatible uh blockchains so basically this is not a state machine i mean if you take a look on this on this token designer uh this is not a state state machine itself it's basically it's it's it's called a corpus if you're familiar like with glomba corpus it's something similar it's a it's a syntax with practically a non-formal semantics or something similar hey could you please read the questions i came quite late and i don't see them in chat so it would really help me to know what questions you are answering thanks true i'm just browsing it a little bit uh but so so i'm just browsing the the the questions most most of them are related to to uh to the stock and taxonomy frameworks most of them related uh where where the stock and taxonomy framework plugin is to be formed and that's something i i show and there was one question if the stock and taxonomy framework is like a state machine uh and for that the answer is not at the moment uh but basically it's rather like a corpus so one question sorry uh yeah i mean we can do it that way so so just raise the question uh if if if you feel like i'm just dancing the chat yeah so sorry maybe i wasn't clear so i came late and zoom doesn't show me the chat and i see another person is also late so we don't see the questions and you just give answers and i don't know what question you're answering so it's a little confusing if you could just read the question allowed it would be before answering it would be very helpful yeah so so i was like the questions and answers a little bit uh they were related mostly for this uh for this for this uh for this plugin for the token taxonomy but sure i mean i mean i will just read uh as soon as i find which is a question and not an answer for another question perhaps so like here is one question what is the significance of the zrc implementation in private network how close they are to to actually sys and then so the so the answer is that they are not necessarily the same uh but i mean as you so basically they they cover somehow the specifics of the of the underlying platform so you know i mean even in even in hyper ledger as you saw there are some specialties because like you should consider the the organizations and the and the structure of your of your of your of your hyper ledger fabric uh you know i mean network but if you get something which is an even wider distributed ledger platform like r3 coda uh then then it's getting me more complicated or from the really RC like standards so like for instance in r3 coda you don't call them ERC you call them as fungible non fungible tokens so they are they are a little further from the early RC standards uh and then what's the significance uh again so basically this is this is the like that was the first side the first slide from me the the beginning of my argument uh it's very simple i mean i mean if you build like applications for blockchain then basically you want to use the basic building blocks and the basic building blocks are the tokens and that's fungible and non fungible and even if you use like you know i mean consortium ledgers or enterprise ledgers uh that's where you start uh helping the blocks like your supply chain and then you get an asset moving on your supply chain i mean you will you will for the first round say then hey that we have this asset as an as an NFT or as a as a hybrid NFT token and then that we have let me integrate some payments in a consortium ledger that's going to be a fungible token and then basically use tokens as a building blocks basic building blocks of your application so the hyper ledger capital market's loop also has a project called nef 30 and on tokens uh that's good that's very good i i didn't know it it's it's very interesting uh i'm not that sure about theft token if it's if it's ERC 20 it's probably yes it's it's i think it's a very old thing so it probably covers kind of a fungible token so here's the answer to the theft tokens was in favor of token solutions on top of fabric and the various areas in UTX token chain yeah so so i'm not so much familiar with theft token to be to be absolutely honest for the questions uh ERC standards it was UTX so one question is i did not follow any of the ERC standards it was UTX in the in the family similar to fabric samples token UTX and SDK but that's not a question sorry uh it's hyper ledger already deployed in production i answered the question uh can we have these instructions uh yeah so so i can put everything actually um into a github repo uh like if you mean these instructions basically uh like like running the uh lining running the demo but it's not very complicated so i would say if you just go to fabric samples and then you read the manual um you can you can find the instructions here so here are all the instructions i just copied into basically into like you know i'm not bad uh so so this is a little bit like description but you get the first step is let's just start like fabric test network uh let me start fabric test network with this script uh let me register an identity let me set basically the the fabric parameters let me export i mean this is again a fabric parameter let me register an identity let me enroll the identity and and stuff like that so if you just go to fabric samples to the github repo and take a look on token ERC 20 and take a look or read me you can find all these instructions uh yeah so i can't i can't explain at the moment erc 721 code in in hyper ledger fabric um i do think very very very much uh deep deep into the under the hood um it should be actually an nft version so you got like nfts uh that's practically that should be an integer and then the ownership of this of this of this token practically should be changed and probably i mean the ownership to an account means something that you get in you get the an you get the account as as basically um something which is a client id and then on top you get some authorization practically uh based on a based on organization that should be the general idea i i didn't take a look very very deeply uh the code actually uh what is what is the tps i'm not but if you see that so that here that transaction per second or or what what you mean exactly uh okay so there's one there's one question what what language are you using to write a code and how can i write it so it looks that way if we take a look the the hyper ledger fabric demo uh then hyper ledger fabric uses like three different languages for your chain code so you can use like go you can use java and you can use node gs uh the code i show very briefly that was that was a go code uh but basically it depends on your framework so if you like you know use like hyper ledger bezu uh then you use solidity probably okay okay okay transaction per second okay so i finished basically the chat so is there any questions uh i mean either in chat or or basically uh you know i mean just just live so basically if there's no more questions uh then i would say that was my presentation and yeah half of my demo it looks that way that you know i mean that demonstration is always difficult but at least mint was working uh as expected uh this is it okay okay uh so there's one question is uh can you expand on the primary object hierarchy for a for a smart contract i'm not quite sure what you mean so you can use like inheritance or or stuff like that uh to expand like the functionality uh but i mean what you have like in hyper ledger fabric uh is basically you know it's a demonstration so it's not like a necessary an official code so you can just extend it as you wish basically um and then if you use like ERC 20 tokens in ethereum uh what you need to be sure that you use like the the standard interface for your ERC standard and at once your implementation is totally up to uh yeah so yeah again that was basically the the presentation for today so i i hope i hope you you get some new you know knowledge as well based on my presentation and i hope that it wasn't very boring uh so thank you very much for the for the for the for the attention and then well i don't know um see you perhaps uh i mean see you as online uh somehow next month or in two months uh at the next uh hyper ledger meetup thanks daniel oh hi daniel uh let me have us question i have a question also daniel are you still there hello sorry um so i'm still here yep sure just go ahead hi daniel the this victor i'd like to ask you a question uh you're talking about the use cases for the token in all this enterprise blockchain just check with you what is a good use case for creating payment tokens for all this enterprise blockchain because in the sense that example you given us about in a supply chain you use a token for payment but another day how can this token be used to convert to fiat for all this payment yeah so so in terms of in terms of payment my experience is that i mean i mean you got public blockchain on the public blockchain you use practically cryptocurrency as payment um on a consortium or on enterprise ledger this use case is still not so much typical uh because on a consortium or or or enterprise ledger the payment use cases are initiated by banks so there are there are two famous uh or getting to be famous the examples for payment one is cvdc that's central bank digital currency uh for which you still don't find very much examples i mean live examples but it's pretty much hard at the moment uh so i would say that's for consortium ledgers in terms of payments one example we have one very exciting example in the future it's gonna be cvdc and another one might be again initiated by bank that's that's something which is it's called the digitized commercial bank money if i'm not mistaken and it's again a use case which is which is not you know not a cryptocurrency and still doesn't really exist but it might come or it might be coming in the future uh as a payment on on really enterprise or consortium ledgers so i would say i would say these two things uh but basically if you have like you know general application and if crypto payment is is okay for you uh what you can do is that you like an enterprise or a consortium ledger for for for a supply chain practically and you integrate uh with uh with the cryptocurrency you know it's gonna be another blockchain so you need to have some kind of an atomic cross-chain swap for or cross ledger integration and your cryptocurrency gonna run on i don't know on ethereum or on bitcoin for instance of course it's it's a question if your use case accepts something which is a crypto payment okay yep thanks i hope i answered the question so i'm still here uh if you have some some other questions yeah hello hello daniel hi hi yeah thank you hi i was one that asked um which programming language you told me go java no js now my concern is this i'm new to i'm a programmer but i'm new to blockchain technology now how is there a link that i can guess what i can start from the foundation because i major with uh c sharp mostly so now i'm going into this aspect so how can i is there a link to start the foundation for me because now i'm new to read totally new to read so so that wouldn't miss out i would not double here and go here and go there and come back again i don't know what i'm doing please help out on that uh yeah that's that's a good point uh so if you if you have actually new in blockchain it's the question is which which platform you want to start with uh so one option might be like hyper ledger fabric but you know i mean i mean fabric is is not the easiest and not the most i mean perhaps interesting platform to to start with with blockchain uh because it's very technical uh you have a lot of you know i'm in work setting up your infrastructure uh and stuffs like that so if you actually knew with uh with blockchain i would propose to use solidity as a language it can even be used with with hyper ledger basis for instance so you can run in in consortium network as well and like when we are starting um you know i mean programming with with solidity that makes fun is is to find uh is to use crypto zombies crypto zombies is a game for for solidity programming it really makes fun i'm just let me just try to find it and i will just uh put it put it to the put the link okay yeah so i mean this is actually the meetup session so it's the informal session so is there like any other questions thank you so if there's no more questions then again uh thank you very much for your attention and then yeah again perhaps see you next time thank you hi everyone thank you