 Perfect. So with that, I'll go through the policy reading as usual. By the way, welcome everybody to this meeting, the Linux Foundation and Trust Policy. Linux Foundation meetings involve participation by industry impactors and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable and trust and competition laws. It is therefore extremely important that these deeds meet agendas and be aware of and not participate in any activities that are previously under applicable U.S. state, federal, foreign, and trust and competition laws. Examples of types of actions that are previously at Linux Foundation meetings and connection with Linux activities are described in the Linux Foundation and Trust Policy. If you have questions about this message, please contact your company council or if you're a member of the Linux Foundation, feel free to contact Andrea of the Grove, the third guest of the Grove Therapy which provides legal counsel of the Linux Foundation. Hyperledger is committed to creating a safe and welcoming community for all. For more information, please visit our code of conduct. Welcome everybody. We're going to have a good speech today by Tom Corbett of Digital Assets. I believe the stage directly to him to have a presentation. Tom, please take the word, the stage is yours. Feel free to show the slide to the deck. Thanks Andrea. Can everybody hear me and see the slides? Okay. Yes. Okay, very good. Yes. So first of all, good morning, good afternoon, good evening from wherever you are in the world. Thanks to Andrea and to Hyperledger Trade Finance, especially interest group for kindly inviting Digital Assets to present this webinar. And thanks to everyone else as well for attending and making the time to participate in the webinar. So today we're going to introduce you to Digital Assets, our demo application platform and how demo is transforming supply chain and trade finance for global enterprise. My name is Tom Corbett. I'm based here in Dublin, very stormy Dublin today with Storm Barra in the middle of it at the moment. I'm originally from London, as you can probably tell from my accent, I'm still working on my Irish accent. I think I still have a bit of a way to go. I'm self-associate for the EMEA Industries team here in Digital Assets. So I look after new clients in the supply change, trade finance, manufacturing, retail, luxury goods, the telco industries. And alongside me is my colleague Ian Woodgate. So I'll let him just introduce himself quickly. So thank you very much Tom and good afternoon everyone. It's great to be here today. My name is Ian. I am a technical sales engineer with Digital Assets and I shall be walking through the demo today. Thanks Ian. So today I think what makes sense is probably to start from the beginning. So before we dive into kind of the trade finance side of things and the demo, we'll speak a little bit, give you a bit of an introduction into Digital Assets and demo. I'm not sure how familiar the audience is with Digital Assets. We're a global organization that are headquartered in New York. We have six offices globally. We're backed by some of the largest financial institutions and global technology corporations. You can see some of them on the right hand side there. As creators of the Linux Hyperledger Foundation, Digital Assets acquired Hyperledger in 2015 and then donated the brand whilst helping to create the foundation. Digital Assets provides extensive industry knowledge and experience in helping clients build real-world solutions with smart contracts and blockchain technology. The 4th of April is Daniel Day which recognizes the date with which we open sourced our Daniel Smart contract language. We were founded in 2014 and we grew out of the financial services industry. You may be asking why I'm showing a financial services slide on a trade finance webinar, but because basically the reason that we're growing so quickly is because we're creating a step change in the financial services industry, improving processes across the end-to-end life cycle of nearly all the functions within finance. Some of our clients would include the Australian Securities Exchange, Goldman Sachs and NASDAQ to name a few, but this step change from Digital Assets is also enabling other industries such as supply chain, manufacturing, trade finance and healthcare because the process efficiency, automation and security characteristics of Daniel are as applicable if not more applicable to those industries as they are within financial services. So Digital Assets are the creators of the DAML application platform which is quickly becoming the industry standard for enterprise business and multi-party systems of record. So leading enterprise businesses rely on DAML to transform their disparate data silos into synchronized networks that eradicate latency and errors and guarantee consistent shared and secure data. So we solved the agile problem of keeping non-trusted parties in sync with their data and completely eliminating reconciliation pains. So currently work flows stretch across multiple participants. You have multiple technologies, different systems, different infrastructures, there's no common data model, there's no common data governance model and what this results in is significant reconciliation and conflict management, all of which is costly to maintain. So if you try to solve these challenges with traditional or legacy technology and you end up with those reconciliation and conflict management challenges. So what DAML does is standardize the data model, standardize the data governance model with a virtual shared state system. So that means that we eliminate the reconciliation processing pains and provide the privacy and security characteristics that are required for enterprise systems of record whilst also enabling extensible DAML networks. Traditionally when you want to solve for these distributed workflow challenges you will typically examine some of the infrastructure providers and these will be long projects that will involve lots of evaluations and trade-offs between the ledger designs or committing to development on a native language which can create risk for the project that you're undertaking. DAML removes the risk by abstracting the application layer from the infrastructure layer and allows you to build applications with all of the distributed computing benefits but connect to any ledger of choice during the lifetime of the application. The time and the cost for building these solutions for these pains with traditional technology could often be a barrier to entry. With DAML we focus on the business logic which enables you to build your applications and move to production more quickly and deliver value from your applications from day one and all of the solutions that are built with DAML are future-proof as they are portable across storage layers and interoperable across networks and this is a key differentiator for DAML as that there are maybe not only truly agnostic and interoperable smart contract languages currently in production. So I'm sure we're all familiar with smart contracts so just a quick introduction for those that aren't. Smart contracts are small computer programs that are executed consistently by each node within a distributed network. DAML is a unique smart contract language in that it starts from the building blocks of rights and obligations. Any asset class such as a letter of credit can be accurately tokenized as a bundle of rights and obligations and the rights and obligations can also be used to model shared workflows to fully automate complex multi-party processes across an ecosystem of parties such as a trade finance ecosystem. So when you build your applications with DAML you can connect and with all of the benefits of a distributed ledger or with the existing tech stacks and run them centrally and DAML connects to all of the leading enterprise blockchains and DLTs and databases so you're future-proofing your tech stack and by choosing DAML and DAML's design makes it low code which enables your developers to create applications and innovate very quickly and efficiently making it faster to get your products and services to market and we're creating with DAML a very low barrier to entry to start innovating around your existing tech stack and start modernizing legacy tech and or building new future-proofed products. So now that we've kind of given you a bit of an intro and a bit of an insight to digital asset DAML we kind of want to take a look towards trade finance and how DAML can be used in in this area right. So if we start to look at some of the I suppose the current challenges that we have within trade finance and the global trade finance ecosystem is estimated to be worth 5.2 trillion dollars and according to McKinsey there's a gap in trade finance availability that's estimated at 1.7 trillion dollars. So if we look at some of the macro economic factors that are affected some of the macroeconomic challenges that we're seeing within trade finance at the moment over the last little while we've all seen the increase in the global supply chain uncertainty and how this has maybe had an impact on banks appetite for risk. Small and medium enterprises make up the majority of firms within global economies and again according to McKinsey 40% of these SMEs have their trade finances rejected last year so you can see that there's some current macroeconomic factors affecting the ecosystem. When you couple this with the more I suppose legacy and operational side of the trade finance ecosystem it's a complex web of technology, complex web of systems, different data models, lots of different participants, multiple parties within that ecosystem. It relies on a manual paper-based process which can be time-consuming and especially when you have complex transactions that involve multiple parties. This means that the actual transactions themselves can be printed delays and all this does is create more bureaucracy and regulation and create barriers for these SMEs and to get access to structure trade finance and increases the cost for them to do so. So if we look at a future state solution with Dammel to solve for the challenges that we looked at on the last slide. So Dammel and a future state solution would leverage the unique properties of Dammel to provide all of the relevant participants with a streamlined process for structure trade finance. Dammel will provide a single source of truth for capturing a standard day capturing and standardizing data across all of the legal entities and participants within the trade finance ecosystem with an automated rules-based workflow that eliminates the current manual processes and facilitates the seamless flow of information across the ecosystem. But importantly with that you have the strict privacy and security characteristics with the ability to set entitlements for key participants such as manufacturers suppliers, banks, insurers and so on. So this is potentially what the future could look like through using the Dammel solution. So we're going to look at what one small part of that now for a demo overview. Before we jump into the demo itself and Ian takes you through the demo I'm just going to kind of outline exactly what we're doing here. So I will draw your attention to the right-hand side of the screen. So we've created a trade finance loan approval process using Dammel and that will include like different points within that process. So we'll have participants and supply chain on boarding. We'll go through the certification of the participants within the supply chain. The manufacturer will create a fulfillment request that then cascades down through the different suppliers that are in the supply chain. One of those tier three suppliers will then request trade finance and we'll see how that trade finance loan can be approved by the bank in the application. A couple of things to call out. This is a very simplified process and we've simplified it for demo purposes but you can make it as arbitrarily complex as required with your specific use case and it's also open source. So Dammel's structure trade finance demo is open source is available on github and we'll make the details of that available after the webinar. So one last slide from me. So I'll just run you through the flow of the trade finance demo. On the left-hand side you have the participants. So you have the manufacturer. You have in our case we're going to have three suppliers. You've got the external water start and you've got the bank. So step one will be the manufacturer on boarding their supply chain. So they're on board all of the different suppliers onto the supply chain. What's key here and what we'll see through this flow is the dotted lines represent visibility into the smart contracts for the different participants. It's all done on a permission basis. So when the manufacturer is on boarding the supply chain all of the other participants can see who else is on that supply chain. So once they've been on boarded the manufacturer will request certification from an external auditor. So this could be for any type of certification. For example it could be to validate the supply chain participants. It could be for CSR requirements or green credentials and the auditor has visibility into who the participants are within the supply chain. So the auditor goes away does their due diligence for the happy path scenario and we will say that the auditor has certified the supply chain. The next step then is the manufacturer to create an order fulfillment request for their tier one supplier. So that goes through to the tier one supplier. They can they accept the order fulfillment request and then that cascades down where they subcontract part of that order to the tier two supplier and the tier two can accept that and subcontract to a tier three supplier. So by the time we get to the tier three supplier in this case it's going to be Gamma Copper they will have visibility into an audit trail of those contracts. So they won't necessarily see the specific details that are the contract between the manufacturer and the tier one supplier but they will see that they will have an audit trail that a contract exists and that data will give them confidence that when they go to the bank to request a loan that they will be able to prove the cash flow and the contract which will help them to first of all get loan approval and also potentially get more favorable terms from the bank and you can see here that the bank will also get visibility into that contract audit or audit trail to enable them to feel confident that they can approve that loan. So again for the happy path we will go into we will let the bank approve the loan for the supply for the tier three supplier and that will be the flow of the trade finance demo. Before I hand over to Ian just the the last bit for me is just to kind of validate for you you know what's the point of this why does it make sense for these participants to be part to be part of this demo. So for the manufacturer it means they can validate the work and it means that they can deliver on their CSR initiatives with a real-time audit trail for the suppliers it means that they can validate the tier two tier three suppliers of the work done but it gives them better access to trade finance and proof terms the provable linkage to that top level procurement and the external auditor gets a more efficient certification process using smart contracts and the bank themselves enables them to increase the addressable market for trade finance solutions with a verifiable proof of contract and cash flows from credit worthy borrowers. So that's the that's it from me for now I'm sure you're sick of the sound of my voice I'm going to hand you over to Ian who's going to take us through the demo. Thank you very much Tom. So I want to start actually by looking at some code it's always good to kind of look under the bonnet. So this is the code hopefully you can see my screen now is that showing okay. So this is the code that you're actually about to see running okay this this is how we define our smart contracts and it's all written in the language demo that Tom talked about just now. I'm not going to go into it in any details don't worry this is not like a code review session but a couple of things I do just want to highlight the first is that the entire application is about 240 odd lines of code we haven't got some initialization scripts after that okay so it's quite short and that's really representative of the fact that dammel is very efficient at encapsulating our data models our data governance and our business logic. The other thing that I wanted to highlight as well is that there's no implementation specific code here this is pure business logic and this is one of the key strengths of dammel actually is that you can take this code and you can run it as is on any of our supported ledgers in a decentralized way without any modifications okay and participants can run their own nodes in that and they could share nodes and the dammel toolset ensures that we have consistency sharding and security of data across all of those nodes. What I will do is I'll just go and look at one example of what we call a template here and the template really is a blueprint for our smart contracts okay so you can see here it's got quite a simple structure we define the template itself we define some some data so this is like our data model for the onboarding invitation we've got a list of contractors and the new subcontractor that we're onboarding we then find who can who's able to sign the contract that's a who's basically able to create one of these contracts or to archive it and then we've got a couple of what we call choices they're really like methods if you're familiar with OO type programming we've got the ability to accept an invitation and what you can see here that all this is doing is if you accept the invitation it creates a new contractual relationship adding the new contractor to the list of subcontractors and if you reject it does nothing other than return okay so that's the that's the kind of language that we use to to build out our templates and our smart contract based solution if you if you want to know more about that that and have a go yourself as Tom's already alluded that this this code here and this whole demo is open source you can download that from github and we'll be sharing the link and you can also download our SDK for free from www.dammel.com okay so now on to the demo and just to give a quick overview of what we're going to see again we're going to create a simplified supply chain we're going to have the top level manufacturer of the supply chain going to request supply certification from an external auditing body we're then going to create some orders and have those cascade down the the chain of suppliers and then we're going to have a subcontractor asked for trade finance from a bank and they're going to present that audit trail of the order hierarchy as evidence of their credit worthiness and that includes the signature from the top level manufacturer in the chain as Tom has already said the demo is simplified it can of course be arbitrarily complex the focus is really on the process I'm just using a simple developer UI for demo purposes and also because it actually helps show you what's happening under the bonnet but for a production ready app you would of course build a richer UI than than what I'm going to show you today and the scenario that we're going to use is that of the manufacturer of phones okay mobile phones so what I've got is I've got a phone manufacturer which is imaginatively called ultra phones ultra phones is going to order phones from a company called phone maker phone maker is going to order cases from alpha cases alpha cases is going to order switches from beta switches and beta switches is going to order copper from gamma copper okay and there's a couple of other parties or roles that I'll bring into this as well we're going to bring in an external auditor who's going to perform the certification of the supply chain and also a bank that's going to issue the trade finance okay so what I've got here is I've got two windows and I'm going to use those for the different profiles that we're going to log in as to complete the demo okay so what I'm going to do is I'm going to log into this demo application it's using the smart contracts that we just saw at the back end and therefore it can run as a decentralized application for today just to explain how I'm running it I'm running this on a sandbox ledger which is running locally on my laptop but I could take exactly the same code as it is and run it on any supported DLT without making any changes okay so the first thing I'm going to do is I'm going to log in as my phone manufacturer in the top window which is ultra phones okay and just to explain the UI that we can see here I've got some menus down right left hand side a couple that I'll draw your particular attention to I've got templates this shows me all of the all the smart contract templates that I've got available from which I'm able to create smart contracts and we'll see those in use as we go through the demo I've got contracts these are the actual instances of my contracts that are in existence and that I've got permission to see and interact with and we've also got filtered views down here for example these are empty at the moment but they well as we progress you will see them filling and they're just filtered views basically off the smart contract so the first thing we're going to do is we're going to create our supply chain by onboarding our subcontractors so what I'm going to do is I'm going to use this first smart contract which is basically representative of of me as as ultra phones and I'm going to create an onboarding invitation okay and just one argument for this I'm going to onboard my supply which is phone maker so what I'm actually doing here is I'm calling one of those choices one of those methods on the smart contract instance that we attempt that on the smart contract instance that we saw the template of earlier okay so that's going to call that choice and what that's done is behind the scenes that has gone and created this onboarding invitation okay if I look at that we can see it's got some information there about who the signatures are who's able to observe or see it and who the contractors are so far obviously just myself ultra phones and I've suck and try and suck and track phone maker okay so what I'm going to do now in the bottom half of the screen is I will sign in as phone maker and you can see that phone maker when I look at my contracts I can see both the contract role that's me but also the onboarding invitation that was created just a few seconds ago so phone maker let's say they're happy they're going to choose to accept that invitation and if as I do this if you watch the top screen what you'll see is that our onboarding invitation is archived and we create a new a new smart contract which is a contractual relationship and this you can see it has been signed by both parties and it specifies that we've currently got two contractors in the in the chain okay so the next thing I'm going to do is we're going to I'm going to leave that one so we can see the contractual relationship here let's say that phone maker now wants to use the contractual relationship and they are going to onboard a subcontractor and they're going to onboard alpha cases this performs a similar process to what we've seen previously I'll sign in as alpha cases you can see I've got the invitation I'm going to choose to accept that invitation and again if you watch the top window and I accept we'll see that the contractual relationship is now expanded and alpha cases is also now a member of that relationship okay so the next thing I'm going to do is I'm going to repeat the process to build up the rest of my supply chain okay so alpha cases it's going to onboard beta switches sign in as beta switches accept the invitation again watch the top window when I accept it there we go and then beta switches is going to use that contractual relationship to onboard the last subcontractor which is gamma copper I can see there's some questions coming up it's probably going to be easiest if we cover them at the end but please do feel free to post any questions into the chat as we progress so we're going to onboard gamma copper okay Andrea unmute yourself please and then I'll log in as gamma copper see the invitation I'll accept that invitation and so now I've built up my full supply chain okay so now that's complete let's say that our top level manufacturer ultra phones they decide that they want to certify their supply chain okay so that could be to meet some esg requirements they want to maybe they want to go and get verification from a third party organization like greenpeace or fair trade or the rainforest alliance or living wage or something like that okay so so what they can do is they can go ahead now and they can use the contract on the contractual relationship that they can say that they want to request certification and they're prompted to who they want to who create that who they want to go and do that certification exercise so let's say it's our external auditor and just while you're doing that just to kind of highlight here that if you have a supply chain background then you may know that you know setting up these supply chains can often be slow quite slow and complex and so this demo is kind of illustrating how you can do that digitally with smart contracts and it's also then an incentive here as we've seen the onboarding of suppliers to there's an incentive for them to onboard as it then makes it easier for them to get access to that trade finance so they're more likely to want to become part of this this workflow absolutely thanks Tom so we're going to request certification from our external auditor so i'll go ahead and do that then in the bottom window we'll sign in as the external auditor and a couple of things to draw your attention to on this you'll see that i see a different set of menu options as the external auditor and i also see a different set of contracts say compared to to some of the other participants like the ultra phones and that's because damwell applies permissions so that people only get to see the the smart contracts that they have permission to see okay in fact if they're on running on their own no they only even receive that sharded data if they've got permission to receive it so you can see that as as the external auditor i've been set a certification request i can look look into it i can see all the data that's associated with that including the list of organizations that i need to certify i can go off now and do my offline processes to make sure that these companies are meeting the the required standards and when i'm satisfied that's the case i can choose to certify the chain okay so again you can see in the top now that's archived the certification request contract and created a certification approval so as the supplier now as a manufacturer now i beg your pardon i can go in there and i can see all of the organizations that have been certified and obviously and i can see that's been signed by the external auditor okay so so i'm happy now that i've got a compliant supply chain and that they've been certified and i've got the evidence of that and again it's a digital representation of that process so it's done a lot faster and a lot quicker than maybe in traditional legacy paper based manual manual process of certification absolutely absolutely so the next thing we're going to do is we're going to start placing orders okay so we're going to start requesting fulfillment to do that i'm going to just grab this contract id because i'm going to associate the orders with this particular contractual relationship that the suppliers have so just go ahead and grab that obviously in a real ui you'd have a more sophisticated method of doing that but it shows you what's happening under the scenes so let's go ahead now and we're going to go and request fulfillment uh so as ultra phones at the top level i'm going to create a fulfillment request okay and i'm going to request that from um my phone maker and let's say it's phones one there's an id product id could be the same let's say i'm going to order 50 000 phones um a unit price of say 500 dollars obviously this this is simplified here you can collect whatever dates you'd need to in reality and i'm going to associate that with the contractual relationship that we had to find earlier okay so that'll go ahead now we'll submit that and what you can see on the contracts now is we've now created this new fulfillment request so what i'm going to do now in the bottom screen is we're logging as our um phone maker i can see that fulfillment request and i'm going to choose to accept that and you can see that's now resulted in an order so an important thing to note here is we we're going to create the orders now and cascade them down the supply chain the the system is built such that the permissioning and the security means that only the parties at either side of an order see the order it's not visible to the whole supply chain so whilst everyone gets to see the supply chain they're not able to see the individual orders those are kept confidential between and the two counter parties to each order okay so phone maker has now got that um got that order what they are now going to do is they're going to cascade that order down the supply chain so looking at the order here so much the mouse so it's 4996 not 50 000 anymore but that's fine um they're going to subcontract that order um and so let's say they're going to subtract that to alpha cases case one that's 50 000 again let's say maybe the cases are a hundred dollars and this pattern actually of seeing this kind of this repeating pattern that you're seeing of making a proposal and then having it accepted is a common pattern that you see a lot of within dammel basically dammel enforces the fact that you can't put somebody into an obligated position without their agreement so so this forces us to obtain consent from somebody before they're they're put in that obligated position so we're going to accept that okay and now we'll log out as phone maker we'll log in as alpha cases we can see that I've got a fulfillment request here I'm going to accept that and now we're going to see that we've got an order again this order now you can see is just between me phone maker and alpha cases and phone maker not visible to everybody else I can see the contractors in the supply chain but I they cannot see this actual contract um we're going to subcontract that as alpha cases we're going to subcontract that to beta switches so we're going to get 50 000 switches maybe at 50 dollars each submit that and then lastly we're going to go in and log in as beta switches accept that request take that order we're now going to subcontract that again to um gamma copper you might measure copper in but let's say there's 20 000 of those priced say 20 dollars we submit that and then lastly we're signing as gamma copper to the last accept and now we've completed the whole cascading of the order so if I go and look at this order from the bottom level beta switches so they can see this order is between beta switches and gamma copper you can see all the details of the order um and we can see who the contractors are in the supply chain although just to re-emphasize again those contracts are not able to see the details of this order this is confidential between myself and myself as gamma copper and beta switches okay so that's good now let's say that in order to fulfill this order gamma copper um wants to um make a trade finance request okay what they can do now is off the back of this order and the fact that it's got embedded within it the whole supply chain they can request a loan so let's say they're going to request a loan from the bank maybe 100 000 so go ahead now and submit that okay so now that's done we can now sign in as the bank and again you can see similar to the exxon order to the bank sees a different view they see different contracts as visible they can see the loan request here so it's from gamma copper if they can see who the contractors are in the supply chain you can see the amount and who's requested it in the currency so they can review that and then they can go through it and do that do their due diligence what other processes they want to do but because because they can see this supply chain and they have can have confidence that that the ultra phones is a is a is a reputable business that they're more inclined to to grant finance at favorable terms okay so they're going to go ahead and approve the loan and that could be an improvement in principle and then could hand off to the bank's payments existing systems at this point or it could even integrate via our daml api to to automate the payment so it could even want or to integrate it could even integrate with the bank system so you achieve the straight through payment but let's say they're happy with that so they'll go ahead and approve the loan so the full amount and then so finally if I log back in now as my gamma copper I can see that I have now got my loan approved and I can see the details of that and it's obviously from the bank so I've obtained the trade finance that that I want to obtain so that concludes the demo and on on their hand back to Tom. Thanks Ian. So thanks again Ian for for doing that so this is I suppose the the last slide that we have just before we move to to any questions that anyone has but basically it's just outlining kind of what are the benefits for the structure of trade finance using daml so it makes it easier to create supply chains by importing participants with straight through easy to use transparent workflows you get real-time notification and visibility of participants into parts or the entire workflow based on their eligibility sub transaction level privacy so the participants can only view contract details that they are entitled to see improved efficiency through processing trade finance requests for banks and participants increasing the addressable market for straight structure trade finance solutions and two tier two, tier three, supply of four banks and an immune requirement stamp and real-time record of what parts of the trade for the money. Yeah please everybody needs because we can we cannot hear Tom speaking go ahead Tom please. So thanks guys so yeah so so look just an overview in terms of the benefits of why use daml for for structure trade finance but I hope that everybody found that and that that that demo and the and the webinar useful so far and I think we're just coming up on time and here Andrea so so what I think probably makes sense is to maybe open up the floor to to some of the questions. Absolutely there are a few questions in the pipeline guys the first one comes from Shane DeConning and he's asking I'm interested in security is there a translation to a lower level smart contract language to all the road code that's generated. So I think you're immune. Can you hear me Tom? Hi Kanya can you hear me? Yeah yeah I can hear you. Just coming off mute yeah I'll try to take that for you Shane I think what your question is so is this kind of I guess what you're saying is are we translating the the daml language into the smart contract language of the ledger that we're operating on and the answer to that is no that's not quite the way it works so we passed the the transactions that that get defined within in daml as a as an opaque blob really to the lower level ledger so whilst we used the ledger to provide distribution sequencing finalization and notary type services we're not we're not translating all of the code into into the the lower level ledger language okay so so the business logic is all sitting in the in the daml layer and that's where the that's where the logic and the permissions are applied does that help yeah yeah that makes sense it's Shane perfect Ian and Tom this question from my friend Frank is asking what involves KYC processes are the e-signatures based on low to question especially under the let's say the perspective of the MLATR and CD the evolving illegal infrastructure so I'm guessing the question really is with with these the where we have somebody signing a contract would it be legally enforceable is that really the question yeah are the e-signature based on low yeah how do you structure the e-signatures are the based on low or only technical stuff so I think I mean Tom you may want to come in on this as well but my understanding of how this is what would work is that the the participants would have a legal agreement that committed them to honouring what was agreed on this system so it's not like if I give you a piece of paper and I say sign this then you you're committed at that point because you have physically signed that is recognised in law these signatures are not quite the same as that so I think if you wanted to have that level of enforcement you would have to have a separate agreement with the parties whereby they agreed that this would be enforceable but by default I don't believe it would be. So Ian the second part of the question actually do you integrate into ERP systems for what orders are generated? We certainly can do that so one of the things that Dan will does very nicely is it generates some very easy to use APIs there's two APIs available in fact so there's a ledger API which is quite low level and there's a higher level easier to use JSON API as well so yes we have lots of customers who integrate with lots of different line of business systems it's relatively straightforward to you do using that API so you could you certainly could integrate to integrate with existing ERP systems. Nice thank you Ian. There's a question from Mr is asking had you considered using Dan all as a build time all layer the dense late student underlying platform run time to the better leverages that platforms pictured he's asking would that not create better secretion of concerns? It's a very good question. Yeah that's a very technical one actually. Yeah I mean so I'm not the deepest techie here with the greatest depth of knowledge with Dan will but my understanding is obviously that has been considered at some point in the lifetime of Dan as it's evolved and I think the reality is that just doing that is is too complicated then in a way it makes it harder to separate the concerns because if you imagine the number of ledgers that we'd have to support and trying to match our abstract Dan will language and being able to translate the abstract Dan will language into the ledger specific implementations of every supported ledger will be exceedingly hard to do so I think in a way you know the architecture that we've got is better where you you're abstracting that away and you're saying we'll manage the business logic within the Dan will run time and we'll use the ledger more as that infrastructure layer as I say providing the distribution sequencing finalization and naturalization type services but not have it we're not trying to leverage the different smart contract languages some of those support because they're all different with different capabilities and different features you'd end up you'd end up with Dan all being constrained to only support the kind of the lowest lowest common denominator if you like of those languages between them whereas where with the architecture I've got we've got we've got a lot more freedom to be able to to be able to to implement the functionality that we want so yes I'm sure it's been considered but I don't think it's would be the a good architecture choice for us to go go to thanks Ian there's another question I'm known actually because I cannot see who made the question how easy is the onboarding process for someone that will restart the supply chain contract Dan will how we are assured this is secured in the contract chain and is there a limit to participants that can be part of say supply chain contract oh I'm not with you sorry you want to onboard Dan will yeah yeah we want to onboard Dan will Nikita that's Nikita actually the name was at the end yeah yeah that's that's fine um Tom dropped me to say that one as well go ahead yeah cool so there's several questions there so so let's unpack that how easy is the onboarding process for somebody who's part of the supply chain so I mean what we've shown you here is a demo um what Dan will does is it implements your business logic for you so so you need to decide what you want your onboarding process to be and I think really kind of like how easy or hard that onboarding process is is down to a large extent to you to define because that's that's really comes down to business requirements once you've decided what that is then it is relatively easy to implement that logic in daml because that's what daml does really well it's really good at implementing business logic okay is that is that you have is that okay Nikita to answer your question thank you yes yes that that helps I'll move on to the next bit though um how are we assured that data is secured in the contract chain so so what we are doing here is daml is providing that runtime where the where the business logic is them and where where the um the functionality that I've been showing you today and the language that I've shown you today runs um in terms of how the data is secured in the underlying chain that's really a feature of the the chain that you choose to to build this on so nothing nothing really fundamentally changes there if you um if you were to base this on sort of hyper ledger then you would benefit from the security that's in the hyper ledger chain okay so that's that really comes down to choosing an an infrastructure provider and a dlt that meets your security requirements okay and then sorry sorry sorry andre there was one more part Peter's question is there a limit to the number of participants that can be um part of a supply chain contract the answer is no not really I mean this would scale here we've got people like stock exchanges using using daml um you hundreds of thousands or millions of transactions going through so no you could make this arbitrarily complex no worries you're very welcome Peter yeah uh there is the question that I was referring to and can you speak to performance of the blockchain systems with application built with daml any risk states in terms of tps will be helpful yes um so funnily enough I've been looking at this the very thing this week um as I said we've got major enterprise clients using this so so the likes of banks and stock exchanges um putting through considerable volumes of transactions um I know that we have certainly I know we have in terms of tps I have seen certainly above 10 000 transactions per second in one example now that was that was sufficient for the client's requirements I'm sure you could architect a solution to go it's considerably higher than that if you needed to do so okay you're very welcome jay I think there is not a question from Sheen yes would it be possible to perform some kind of revocation or overriding on cases like non-fulfillment or change of contractual parties yeah absolutely Sheen's great question actually um the way you would do that is that's just business logic right so um if you wanted to define that within your business logic so maybe have a revocation choice on your um on your fulfillment request or on your order or something like that then absolutely you could just you would just build that into your daml because that's just business logic um you just write it into the code and we do um with some other examples and some other customers we work with very much have that that kind of thing good good yeah perfect uh look uh I would love to take questions I mean to give you answers uh and I would love to have your opinion in the in that how one can get started with daml what blockchain can daml uh run on and how you so we steal team or blockchain to run them on can you give us a few hints you know just the kickstart points sure tom do you want to take the start of that one so thanks for for all those answers here um very helpful uh yeah so to get started with um with daml daml is open source um you can go on daml.com download rstk for free um and start creating your applications with daml um and you know typically that's the best way to get started there is a very um vibrant and diverse um developer community as well um that you can access um through discuss.daml I think discuss.daml.com yeah or on the from the daml.com website just go to community.com exactly and and and so that's you know for for people interested in in starting to use daml that's that that there would be a great um first step. Yeah and people are very welcome to post questions on to that community as well it's very active and it's a great place actually to get help if you just want to download the sdk and you're struggling with anything then feel free to use that community. Yeah uh just now the theme guys uh I was wondering how about the data who owns the data uh and the network of course great question do you do you want me to take that one go for it so that's really up to you so we have different different models that you can operate so you can you can operate this in a fairly centralized way if you want where you can I mean you can actually take this if you want to and and just deploy it all within your own your own environment your own network and it is purely yours um you can open that out to allow external parties to come in and access you can host nodes on behalf of external parties or you can create a completely decentralized network with with external parties where each party owns one or more nodes or or several parties may choose to own a node together um but there is no no overall owner of the network if you want to do that um so that's really really up to you again that's largely a that's largely determined by the underlying infrastructure that you choose to build this on okay so I think there's one more question actually Tom which was what um what ledges does this run on say or our supported ledges you had that in the slide actually I think I did yeah um let me go back uh okay well that's pretty cool it's probably worth checking down on .com as well because it's always changing there's always new ones being added right yeah so okay so if you can see my screen there that's just a cross section of some of the um the enterprise blockchain's distributed ledgers and centralized databases that we um connect to um their list is changing all the time so you know as Ian says keep keep it on down with .com to um to make sure that that you're you keep abreast of that but you know most of the leading distributed ledgers um we can connect to yeah in fact if you google um Dan was supported ledges it's the first first result that comes up so uh I would love to leave them to the attendance once again to see whether they have any more questions and for the question that you Ian and Tom anybody else would love to make question I think we're looking pretty good so that's the one I guess from Shane yeah any plan to integrate with the public blockchain in the future is good one very good question we thought someone asked Tom do you want to answer that I don't want you to take that uh you go for it yeah sure so uh yeah it's a great question Shane it's a question that I'm unsurprisingly I'm sure you you'd expect us to be asked a lot um we have a community edition of Ethereum driver at the moment so so that integration is there um we are also actually working on a different connector as well which is a um which will enable us to kind of bridge between our networks and public networks as well so yes there are some developments going on there but it's very much driven by client need as well I don't know if you want to add any more on that one Tom uh no I think you've got it covered there Ian thanks it's the same thanks great stuff Shane you're very welcome yeah uh Ian uh I don't know you can answer this one how do you manage changes to smart contract model once you're live ah great question um it's actually I love putting you in difficulties that no I like this is a question we also get asked by a lot actually in fact it's a question that I asked when I when I started it I did just the asset as well um if you think about a change to your set of smart contracts is really um business logic so it's actually easy to do because you create a template for a smart contract which is an upgrade contract and it can take you it can take your old contracts and create upgraded versions of them so um it's actually it's really slick the way it happens you you basically create upgraded templates and you you you apply that to the chain to the ledger and you allow um allow them to what you you can choose the manner by which they will upgrade your existing smart contract so you you use the tooling itself to kind of like almost upgrade itself if that makes sense but it's uh yeah it's it's it's relatively easy to do and it's it's quite powerful technique so you use smart con you have kind of an upgrade smart contracts do you imagine you can have different versions of you maybe have got invite supply of v1 and invite supply v2 and and you can pass the v1 into v2 and it will create a v2 that kind of thing thank you and right anybody else who love to make questions let me see whatever in the chat no further questions i think we're exceeding time and yeah i think uh rick would you like to make questions to the to the speakers have one more question and david has asked has a contract ever failed yeah of course contracts can fail um one of the things i didn't say with dammel that perhaps is worth mentioning though is that yeah things can go wrong of course you business logic could fail there could be you know something could fail in the in the infrastructure layer um but one of the nice things about dammel is is all of the business logic that i encapsulate within a choice is guaranteed to be atomic so really the everything will pass or everything will fail so the same as you get with the atomic transactions in the database it's atomic so yeah if you get a failure then you'll get an entire failure of a transaction so yes things can go wrong but the system handles that very robustly can we select a deployment underlying sorry guys it's going on it's going on um jay says can we select a deployment underlying framework should we make this the last question because we are out of time um if anyone does have any more questions i'm sure if they send them through to andrea he'll be very happy to forward them on to us would that be okay andrea no it is okay go on um just answer this last question with them i think we should close the session no worries at all uh can we select deployment underlying framework as different participants in the network um not well that's something that we are almost that is something that we're kind of working on at the moment if you visit canton.io um that's some technology that we're working on which basically would allow interconnections between different um networks so right now if you if you go to dammel.com and download your sdk then the code you what you would build there you would run on one ledger but we are working on the ability to interconnect different networks as well um so yes jay that is that is going to be um something that's just about there now and it's what something is there now and it's something we'll be developing further in in the next year so yes you're very welcome jay okay can you hear me yes sir yeah can you hear me in yes perfect i was uh bidding you bye to everybody and i was uh thanking you and time for this insightful presentation it was great to have you both here and hope to see you again we're going to join forces in one week stay all well and keep in contact have a great evening guys thank you very much andre and thanks for the opportunity bye and a great evening thanks everybody bye tom