 And you're live Okay, thanks a lot Maybe from my side, my name is Daniel Segel. I am a software architect At the moment, I mainly work on blockchain projects I have two directions Of course, blockchain On the one hand, I work on hyperledger factory projects So that's really this classic consortium On the other hand, I sometimes have solid Ethereum projects And then here I practically have solid IT development, I would say But then here I also have a consortium as well Public blockchain smart contract programming, I would say But as I said, the topic is today Blockchain and interoperability How different blockchain solutions Can work together or communicate That's the agenda for today I have built up a bit of a step-by-step First, I would briefly talk about blockchain and interoperability So why is it important? Why is it exciting? Why does the market need such solutions? Then I would actually like to Show you a little bit in detail These are the blockchain, Rackern, Crosschain, Crosschain, Chocker and Chocker And atomic crosschain swap or atomic crosschain exchange Then I would generally talk about interoperability platforms And then I would really go into detail How blockchain cooperation in hyperledger and consortium blockchain looks And in the end I also have a slide Or actually two slides about hyperledger Cactus I also have a demo, I hope this thing will work And then in the end I thought that I would have 10 minutes For questions or 15 minutes for questions and discussions In general, the idea, my proposal will take about 40 minutes If I have a bigger discussion or questions I thought at the end If I have a short question Or maybe my network will come together and I have to repair it Then we can also have a short pause in the middle And then I will try to answer the questions Or if my network and laptop will come together I will repair the thing So that is the agenda for today Then let's start What is blockchain interoperability? And why is the topic important at all? The problem is that there are many different And sometimes competing blockchain platforms On the one hand there are the so-called public network Or the public network For example Ethereum, Cardano, Neu, IOS, Algorand, my smart chain And so on and so on On the right side I actually have a tablet There are different public networks So public blockchain solutions And then there are about 15 of them I don't even know half of them And I would say we could theoretically still have 20 or 30 Such public blockchain networks Some such solutions For a specific purpose For example identity, blockchain and identity solutions Or crypto currency There are also competing blockchain solutions Or platforms So for example from general smart contract-based blockchain platforms We actually have 20 or even 30 of them And that is just a part We also have the consortium chain Where you can use blockchain in consortium, enterprise or enterprise There is no crypto currency in here So maybe the topic is getting a little less marketing hype But still it is important So here we have such platforms For example Hyperledger Fabrik, Bezu, So2, Arfi, Corda and so on I would say we are not so far away That everyone on the earth already has their own blockchain platform But the number of the blockchain platforms in the last five years Would be significantly increased And therefore we currently have a lot of competing platforms The problem is that sometimes compatibility Between such blockchain platforms Is normally not a design goal So the blockchain platform would not develop that way That they can somehow communicate with each other Or work together On the other hand If we are talking about a complex decentralized application Or I would say that if we have a simple decentralized application Then it can happen relatively often That we have to work together with several blockchain platforms So for example Astriminus 4 We somehow have a decentralized application For a supply chain management application Then And so that this supply chain management software Decentralization also has a part for crypto payment Then there is somehow the possibility That the users can also pay in crypto If we look at this scenario Then the idea is often that Okay, we have a supply chain management Then we would like to set it up with a consortium blockchain For example with Hyperledger Fabric But of course crypto payment does not work with Hyperledger Fabric So that means that if we still need crypto payment Then we probably need it on the one hand Bitcoin or Ethereum or whatever And then we are talking about three blockchain platforms That in a not necessarily very complex decentralized application Must be used And then there is no design philosophy Really How to use such applications And integration Must be used by the blockchain So that's why the topic is hot And that's why the topic is very important I would like to show you three ideas first What one can practically understand about blockchain And then the first idea is These are the so-called blockchain oracle My blockchain oracle Is that we have to import an external data into the blockchain So first of all, we don't have a blockchain We only have a blockchain for the first term And then the problem is that a smart contract system An additional application is relatively closed The blockchain itself is also relatively closed So that means that if we need external data Then we have to have an idea or a so-called oracle What can the external data have? So imagine that we have a decentralized application That, for example, has to start with euros and dollars exchange rate That dollar and euro exchange rate is an external data That you have to import into the system And possibly that has to be transferred Otherwise, the system can actually be pretty strong Despite the blockchain and despite the smart contract Another example could be If we have such an insurance application Then maybe we have to measure the temperature What is the temperature today? And what is the temperature? Or what was the temperature yesterday and the day before yesterday? And depending on whether the temperature is somehow 10 degrees or 40 degrees Is the logic in our smart contract different Will the smart contract practically apply differently? So how does such an oracle system work? I would actually show it on the picture here So first of all we have an external data source That can be a database or a website or something And we have to do that or we want to put that into the blockchain As I said, two examples Such a data can be, for example, a euro dollar exchange rate Or at least the temperature So to import the blockchain into the smart contract We need an oracle An oracle is the first word, a server What this data also reads and then practically sends into the smart contract This server could theoretically be a piece So the system is relatively centralized Something like that we don't really like in blockchain So that's why such an oracle structure is sometimes decentralized That means we have several nodes, several such oracles They read the external data sources regardless of each other And there is also a consensus mechanism between the oracle nodes And then at the end of the consensus there is a decision what is the correct value And to really deliver a correct value Are normally responsible mechanisms So for example this consensus and the correct value Is normally supported with a token Then there is a choice based on these tokens And then there is also a business motivation So that the independent oracle nodes really deliver the correct value So such motivation is for example staking or slashing If we have the correct value then we have to bring it into the smart contract So here we still have a few things that can go wrong So here there is probably a network channel So the data has to be connected to digital signatures and so on And at the end of the day we have our data in smart contract So the data can be used practically in a decentralized application Here we actually only have one blockchain But the screen can simply be used to scan two blockchains So we can imagine that this external data is not a standard Data source but that is another blockchain So for example if we want to connect Ethereum and Hyperledger Then we could say that this external data source is an event in a solidity smart contract And we would read that out and then the oracle nodes would read the data from Ethereum blockchain And import it into the Hyperledger smart contract Then practically to say we have a collaboration between two blockchains Between Ethereum and Hyperledger These are the classic examples for such oracle algorithms or platforms So chaining and provable, these are the two that are commonly used I think provable was a protocol a few years ago If I am not mistaken And then for example it is a band protocol It is relatively new as far as I know So that was an approach to integrate blockchain platforms Let's look at another idea, another main idea The other idea is the so-called cross-chain token idea Here the problem is that we normally have two blockchain platforms in this scenario And then we have two blockchain platforms The easiest example is Bitcoin and Ethereum And what we would like to see, we would like to see Bitcoin on Ethereum Of course we have two new platforms Bitcoin can only be created on Bitcoin and then there is no Bitcoin on Ethereum With such things or such integration you can do something with cross-chain tokens So cross-chain token works the following The work mechanism has two parts The first part is that we have a bit of Bitcoin And from this Bitcoin we would like to create a similar thing on Ethereum And then we call it RectBitcoin This thing works like this Two steps in practice First we have to transfer our Bitcoin to a so-called custodian A custodian is a institute It is a bit more complex than a custodian is an institute And our Bitcoin in this institute is closed So that means that someone can move it This is the first step The second step, if we are sure that our blockchain token or coin Our Bitcoin or coin is closed in this custodian in this institute Then we can create a new token on Ethereum So practically mint And then we call these tokens as RectBitcoin That is the second step And so we are sure that if we see a RectBitcoin token on Ethereum network Then we can be sure that somewhere behind it is actually a normal Bitcoin So the second way is also logical If we want to switch the value of Bitcoin back to a normal Bitcoin Then the mechanism also has two steps First we have to delete our value of Bitcoin That is a burn functionality And if we delete something Then our Bitcoin can be released by the custodian from the institute Or switched off Or simply returned for the owner Of course, here I said that this is a custodian This is an institute To see technically, this is not an institute So in a blockchain environment, we don't like the so-called centralized institutes So practically to see this custodian, this institute is not a centralized institute But it is also realized, for example, with Bitcoin For example, with Hash Time Lock Contract or with Multisiguality For such a blockchain cooperation So classic examples, for example with Red Deaterium In Red Deater there are actually no two blockchains, but only one The classic example is Red Bitcoin Then we have, for example, the REN project Is somehow a general platform for such cross-chain token exchange scanners Then we look at another idea It is also a good idea How to integrate two blockchains platform And this third idea is the so-called atomic cross-chain exchange Here it goes again We have two blockchains again And we have a blockchain transaction And then we would somehow achieve that a transaction on a blockchain is carried out Only if the other is carried out So either both transactions are carried out Or none of these transactions is carried out I'm talking about transactions There is a general model where you can really exchange atomic cross-chain with transactions But the classic is that these transactions are not general transactions But really token transfers So here, for example, the easiest example That we have, for example, a Bitcoin network and also an Ethereum network And we would like to have a Bitcoin transfer on the Bitcoin network And we would also like to have an Ether or ERC-20 token transfer on Ethereum And we would like to be sure that both transactions are carried out or none of these transactions is carried out So that's atomic cross-chain Technically speaking, such atomic cross-chain exchange is based on HTLC HTLC is a hash-time-lock contract A hash-time-lock contract, so to simply put, is something like a temporary transaction So a transaction that somehow has been carried out, not 100% but 50% And then there are two things that you can start with such a temporary transaction, such a 50% transaction There is a key and if the key is available, then this temporary transaction can be carried out consistently From 50% it can be 100% And there is also a period of time And then the period of time means that if you do not use the key for this temporary transaction In the period of time, then this transaction will practically be carried out So from 50% it will be 0% And then somehow the main idea of an atomic cross-chain swap is that we start with two such HTLCs So we start with one HTLC on the Bitcoin network and we start with the other on Ethereum That's wrong, but it doesn't matter So that means we have two 50% transactions on Bitcoin and on Ethereum And if we have the key, then with the help of the key we can carry out both transactions consistently So both are carried out And if we don't use the key, then both transactions are practically rolled back So we guarantee that either both transactions are carried out or not That's atomic cross-chain swap After these three simple interoperability ideas I have a slide on public interoperability platforms They are mainly used for public blockchain platforms And they are generally used for cross-chain bridges and for common purpose solutions In general, with the help of such a platform you can use a lot of blockchain cooperation as a scenario So for example, you can exchange data, transactions together between several blockchain And then have multi-asset solutions and so on A classic example for such a public interoperability platform is Polkadot Polkadot is based on sidechain So that means that we have a main blockchain, a meta-blockchain I would say it's RelayChain And RelayChain is the interoperability solution itself The interoperability solution is also a blockchain itself Which of course has so much complexity, but it doesn't matter And we also have so-called parachains, and parachains are sidechains And parachains are actually the blockchain solutions And you should somehow create some communication, data exchange and general transactions Between these parachain platforms, between these sidechain parachains RelayChain, the main meta-blockchain, is responsible for the fact that this communication can run cryptographically So that's the main idea of Polkadot There is also a second general interoperability platform, mainly for public blockchain platforms Cosmos has a similar idea, but is based on sidechains So it's a bit different We also have some solutions that are not so well known Now the main meta-blockchain solution is also a sidechain solution We also have one that doesn't have a meta-blockchain, but rather some blocks Between different blockchain platforms for communication Which of course is much more interesting What is Hyperledger about blockchain interoperability Or what are the possible uses of Hyperledger for interoperability Before we look at the details, you have to notice that Hyperledger itself is not a blockchain platform Hyperledger itself is not a tool, but Hyperledger is practically an incubator project And there are several sometimes independent and sometimes competing solutions in Hyperledger These are tools, these are representative blockchain platforms and so on I have the thing that is still open, but this is the Hyperledger roadmap Or these are the Hyperledger main projects And then you can see that under Hyperledger there are several independent projects They are also in different statuses, so they are projects that are still in incubation This means that they are not yet in the productive area They are projects that have already graduated, they are practically completely productive And you can now use them without any problems And we also have projects that are not continued, they are so deplicated And then the first thing that was exciting, I have to say, regarding blockchain interoperability is Hyperledger Quilt Hyperledger Quilt is an implementation of interledger protocol I would say that interledger protocol is an extension of atomic cross-chain exchange With interledger protocol you can not only exchange between two blockchains, but between three, four, five, six blockchains And then with interledger protocol you can exchange this atomic cross-chain exchange Not only between blockchain protocols, but blockchain and centralized ledger solutions It has become somewhat deplicated It has not been continued, I don't know why But then it was definitely an exciting project Then the main idea for Hyperledger and blockchain interoperability is Hyperledger Coctus I think Hyperledger Coctus is still in incubation on this side But I'm not sure, I think last month it was already graduated So, as far as I know, the project is already live and productive Hyperledger Coctus was an integration framework for blockchain It is an enterprise architecture, enterprise framework, I would say That means modular, expandable and also a big dinosaur, I would say You can't see it, Coctus, transactions and many other services on multiple ledgers Without additional blockchains, so the approach is not the same as for example Cosmos Network We don't have a main blockchain or relay blockchain In the next slide, I would go into the details What is perhaps important is that Hyperledger focuses more on the consortium world So that means that the solutions that you find here Focus sometimes also strongly on the consortium world So if we talk about Coctus for example Then the idea is that Coctus creates a collaboration mainly between For the first word, mainly between consortium blockchain platform Or maybe future, I mean, I mean, it is already integrated by public networks But maybe future will integrate even more public blockchain platform But at the moment it is not the main root What is still exciting to mention Let's see if I can find the slide Hyperledger is not just full-time projects So these are the full-time projects, even if they are in a gradual phase But there is something that Hyperledger lives What do you call Hyperledger lives? Hyperledger lives are such small projects They are not yet full-time projects But projects, I would say And then maybe in the future they will be practically full-time Hyperledger projects And then we have here the amount Of these many Hyperledger labs Small projects, I have found two That have something to do with blockchain interoperability On the one hand, Hyperledger Weaver Hyperledger Weaver is a cross-chain solution Really for blockchain interoperability So really cross-chain transactions That you can set up between two blockchains And then the other solution is Framework is mainly thought for off-chain transactions So there are so many channels And you can really send transactions to such channels And it is much faster than everything To run on the blockchain But PerunLab also has so many integration functions So then we look at Cactus As I said, the productive possibility Of Hyperledger to the blockchain and interoperability Is really Cactus Cactus is a pretty big dinosaur But it creates a lot of possible scanners And then it will also be further developed So probably we will create more scanners It is based on validator nodes And there is also consensus Between these validator nodes There is no own blockchain But that is very important What is exciting Architectural techniques, the two important components Are the so-called ledger connectors And then the blockchain plug And then ledger connectors Communicate really with different blockchain platforms If I can do that So these are the ledger connectors And that means As the platform is available And then we currently have This is a new ledger connector But you can also write more Or implement more At the moment we have a connector for Hyperledger For the fabric Go Ethereum, Forum and Xd As I said, it is a plug-in-based application So if you need an additional ledger connector For example Bitcoin Then it is impossible I wouldn't say it's easy But the architecture supports Such ledger connectors To write And then you can also Set such applications Where, for example, Bitcoin is available And then Blockchain cooperation Between Bitcoin and fabric And so on And so on The other idea is These are the blockchain plugins And blockchain plugins Are the best-made Business models For this We need to work on two blockchain plugins So Practically these are the scanners That I mentioned earlier So we have Ledger The ledger is a cross-chain token We have an atomic swap It is similar to an atomic cross-chain swap With HTLC and so on We also have ledger interaction It is similar to With an oracle Two blockchain plugins We also have Coordination On an entry point That means That you can, for example, configure The thing in a crypto wallet And from a crypto wallet Or a blockchain wallet You can't just start transactions On one network But on several networks And then practically Cactus Uses Some routing These transactions, for example What is also exciting There is a difference in ledger objects There are two different objects On the one hand, we have the tokens So it is called Practically the same On the other hand, we have data And what is exciting Is to understand the hope ideas Between these two objects So when we talk about data Data is, for example, the temperature What we import from the outside And then we can Distribute it on any blockchain That means Data can be distributed without a limit Copied And so on And so on With these tokens Or assets They are such fungible and not fungible tokens Practically to say But we have to pay attention to the doppelganger output So doppelganger output Is normally not possible In a blockchain But if we Two or three blockchains We can already imagine that That we have a token in a blockchain And this token is Expected in a completely different platform And what is exciting Is that the cactus is visible This difference And then this Doppelganger output is avoided Even if we are more than one I mean, in the sense that the doppelganger output Not only on a blockchain But between several blockchain platforms I'm not sure Everything is already really productive But in any case Are the ideas in the White Paper Already listed Then For the end I have a demo I hope that the thing will work It is the fastest demo What you can start You just have to The docker command And then it actually works The idea is Is a very simple demo There are three steps We first have to create the bamboo As a raw material Then from this bamboo A bookshelf Is somehow built together And then these booksshelf Will be somehow transported Somewhere It is not a complete application But the main idea is a bit similar So we have a raw material Then we build something together Based on this raw material And then transport it Will somehow What is exciting is That the application is based on Three different blockchain platforms Everything that somehow The raw material Will be stored in Hyperledger Everything that Is somehow built together As a bookshelf Will be stored in Hyperledger And then the Transporting information Is stored in Hyperledger And then the three blockchain Have somehow a simple assembly There is also an idea What has to be synchronized And then somehow referenced So practically With the bookshelf This bamboo idea has to be referenced What does it mean that the idea Or between a bamboo frame Has to be synchronized And then the idea of the bookshelf Has to be referenced in the Transporting That practically means that this idea Between frame and factory Has to be synchronized And then the demo is actually relatively simple I have the thing somewhere here So this is the demo application And the thing looks like this So there is a simple user interface You can't really See the blockchain solutions They are not hidden In a container But in any case exciting To be honest, we have bamboo That is in Hyperledger Besu We have the books They are in Hyperledger What was it? This is a solution This is not a Hyperledger But a solution And then shipment These are the transportation things They are stored in the factory And then If I create something new Then these are the information I will submit Then the new information Is now stored in Hyperledger Besu If I create a book regal Then I have to reference On bamboo On the transport So that means this idea This idea Has to be synchronized Between Hyperledger Besu And Quorum So we say ok We say submit We have a new entry And then at the end The thing where to transport So that means I need an idea About the book regal Which somehow Between Hyperledger Between Quorum And Hyperledger Submit And I have a new entry Theoretically There is Not Somewhere There is also a Of course all open source If you are not really Known with Hyperledger Everything that Hyperledger Is in these open source projects So that means Hyperledger Cactus is also 100% open source I mean, of course, you can expand the platform But as a starting point Is maybe not the Not the best idea The platform I mean, somehow to advance But as an example There is a cactus And the examples And these are simple examples So for example The Supply Chain App What I just showed You can also find here Then we find, for example So this is the supply chain back end front end For example, the supply chain back end Is The smart contracts That are used For example, these are the Bambu Harvest repository And we also have The bookshelf repository So these are the information That I saved here These are the smart contracts Back end And then we also have Shipping Shipping is practically Something to transport It is based on Hyperledger And it is a good brand And if you also have a little patience Then You will find Some more examples here For example Electricity Trades Carbon Accounting So probably Is the best idea To start here If you want to start with a cactus So that was my presentation For today And then It took a little longer Than I thought Can we really have a break And if Questions are Then I can try To answer the questions Or if there is any discussion From someone Then we can discuss I will try So there is a chat Of course I didn't manage To watch the chat During my presentation At the moment the chat is here So if anyone has questions Then Then I would like to On the chat So if anyone has questions Then I would say That was the end My presentation Then I would I would I would thank the participants I hope That I Made it To tell something new Regarding Blockchain and Interoperability So then Next month I will In English About tokenization And consortium ledger A meet-up In two months In English About CBC So I would say Slowly The German community Will Return to life Hopefully We will This year Have more German suggestions Thank you very much And then Goodbye and see you again