 Hello everybody, my name is Julien Atta, I'm a research engineer at the Orange Company and I'm a blockchain enthusiast. First of all I will explain why we've chose to build a reference model and how we build this model before explaining exactly how it works and what we hope to do right now and in the future with this model. When we look at the state of the art, we see that most of the papers focused on blockchain technology modelling, especially on the technical aspect, both the features of it or sometimes the businesses that are maybe a good opportunity for a blockchain. But not so many people focus on what the actors can, what role can the actors place inside this business and we decided to have a look at it. If we look at classical applications that are off-chain, we have an ecosystem with hosting companies, developers, build tools, language and if we look at what role a company is playing inside this ecosystem, we could also understand its business model. In blockchain, there is not many work on it and so we decided inside a DLT system to understand what role a company could play and often it will permit to answer to the question should I mind, should I be a validate, should I validate some transaction, should I construct my own blockchain, should I join a public blockchain, should I join a consortium. So to build the model, we have done an analysis of nine different DLTs, like the Bitcoin of course, but also AOC, Ethereum, LISC, Perliger, Qwinterparty and we focus on the lifecycle of decentralized application. The model is, so in the center we have the decentralized application and at the top of it, we have the DLTCAD owner and we see that there is strong link between the of course DLTCAD owner, the one who creates the protocol and the one who builds the tools to develop application, those who will own the tools and those who will validate. The DLTCAD owner, for instance it could be Ethereum or any other foundation that produce the protocol, provide the virtual machine, the assembly language and so on. And it's very important because, and we'll see it's often a foundation or it's a big company often, it maintains the code and also it is the one who could manage incentives for the funders, so it is the one who establish trust inside the blockchain. We then have the validator instance and of course it's a key role because it validates transaction, it could be done using any algorithm, proof of work, proof of stake or any other mechanism. And we have a DAP instance. We've really focused on the technical aspect inside our model, we do not include all the off-chain aspects that could go with DAPs and we focus on the byte code that is holding inside the application and of course it depends always on the validator to be published. The byte code for those that are maybe not information is the code that is able to be interpreted, to be executed by a computer, so by our blockchain in this case. So, for example, EPSC on EOS or Uniswap or in terms that are famous application. We then have the utility provider in order in our ecosystem to build an application we need to have the tools to do it. For instance, we have Parity for Ethereum which is famous and that is done by the Parity Foundation but you also have the tools made directly by the Ethereum foundation or also as there is the TIO that is an application developer and that needed his own tools that develop also has a KASM tool for EOS because he wanted to have his own tool to develop his product. So I think it is like in common development we see the kind of the same role that are played by actors for those that build tools, those that develop and those that own the application. I took the example as DAP owner of Société Générale which is a French bank that recently published some DAP on the Ethereum public network but there is plenty of DAP owner, of course, and it is also the business owner. And of course in our model the DAP consumer that is the end user of the application, it could execute function, it could read the results inside our chain and it could also be, it's not necessarily human, it could also be another DAP or an off-chain application. So as a resume, we can see that most of the time foundation are behind the protocol and so we find foundation as DLT code owner and often the first tools provided to work on a blockchain are made by also the same actor, I mean the DLT code owner, but on the majority of them, anyone has developed code and has developed tools to work on it. There is a huge difference really in the DLT we have looked at, it's that part of them are consortium blockchain and in consortium blockchain it's always the company that is behind. So it asks the question of the centralization of power inside the blockchain whereas in foundation this question is less efficient of course. In conclusion what this model will be used for is to be a tool for practitioners who want to choose a role on the business model for the solution. And we are currently trying to implement it inside a simulation using multi-agent in order to ask two simple questions, which DLT is suitable for my DAP because of course if you publish on multiple chain you will have costs associated to it. And we want to measure if this cost is superior to the profit, to the benefits you will have with your application and also because some chain and we are thinking of a small chain for the moment that are nearly to be created or that we would like to create could be weak or could not stay long in the time and maybe we could diminish the risk of losing our application by publishing it on multiple DLT so this is the current question we are trying to answer with it. Thank you for your attention and I'll be pleased to answer to your question.