 Hello, everyone. Welcome to the July 2018 update for Project Gogan. I'm your project manager, Gerard Moroni. So the agenda for today is to just remind you what Gogan's about, what have we done in the last month, feedback from you, and important dates. So the goal of Gogan is to deliver smart contracts for the Carolina platform. And coming out of this project, what we're going to be delivering will be a computational layer where you run smart contracts, as well as tools, training, and documentation to help you use the technology that we're going to deliver. So the last month we've been doing a lot of work on prototypes and models for the sidechains, chimeric ledgers, and multi-currency. And this is the next step after research before we go into code. And one of the benefits of doing this is it provides additional evidence and proof for the academic submissions that we're going to be making for these important research areas. For Plutus, we've managed to further simplify the design of Plutus core, language, and increased confidence in its safety and security by mathematical proofs. We largely completed the Haskell library for processing Plutus core together with a reference virtual machine. We've also refined innovative proposals that would bring powerful and secure smart contracts to UTXO ledgers. For Marlowe, the results of the first phase of Marlowe development have been accepted for a peer review paper, and we're delighted about that. We started to formalize the behavior of Marlowe using fear-improvers, and have completed first results verifying the correct behavior with respect to contract termination. We improved the performance of the decision procedure by re-implementing in SMT-Z3 rather than ILP. For Yelly, we've launched our testnet, and we've spent a lot of time on this testnet to provide really detailed and comprehensive documentation and materials going to help you to understand the technology and how to use it. And that has included us going to Oxford in the UK to meet with the runtime verification team and record a series of interviews and presentations about the technologies surrounding Yelly. So we're hoping that you'll enjoy that on the testnet. In addition to that, the team at runtime verification have been working with us on things like the LLVM backend, the Plutus 2.0 Yelly compiler, as well as gas model improvements for the LLVM itself. For end users and external developers, we have a product manager who's joined the team, and he's focusing heavily on how to best deliver an outcome that will benefit the end users of the smart contracts and the external developers. So we want to create great technology. We want to make sure that we create the right great technology for the people who we want to use it. That's very important to our work and something we're focusing heavily on right now. In terms of integration, we've baselined our architecture on integration design, and like I said, we've been creating the models and prototypes for the Chimeric ledger and multi-currency, and the sidechains will follow into your course. And as I said, the outcome of that will be something that we can use when we go to start making changes to the code itself. For technical document and education, like I mentioned, we've been focusing heavily on providing additional content and training for you for the LE testnet, and that's based on our experience for KAVM where you asked for more. So we've listened to and hopefully what we've delivered is something that you will enjoy and find informative, and if there's something else that you want to have us deliver, then we're more than happy to do so. For quality assurance, we've been expanding how we test things, and we're hoping that's going to give you a much better experience, but if you do find any problems, please feel free to let us know we're more than happy to help. For marketing and external communications, we've been focusing heavily on promoting LE and the testnet in multiple channels. We've done a press release, and we're now in the process of starting our post-launch campaign, and I'll talk a bit more about that later on. So feedback from you, you're very happy with the quick turnaround we had to website changes and bulk fixes for KAVM, so we're going to make sure that we maintain that high standard. You asked for information about the status of testnets, so we started off with something very fundamental and simple, which is a red amber green status for each testnet, which you can now see on the testnet site. That will tell you if the testnet is up and running, if it's stopped, or maybe it's slow because of high volume of traffic. We've built an education machine for LE, and we're hoping that's going to make, as I said, the experience of using LE and the LE testnet better. We're in the process of completing work now that will allow you to connect to the LE testnet using Web3JS and WebSockets, so we're hoping that's going to make the experience of using the testnets and understanding what you can do with it a little bit easier for you. We've already listened to what you said in the last week, and we're hearing that you enjoy using the testnet, but you want more tutorials on LE, so we're thinking about that. There's been questions about cross-chain smart contract calls, which I'll be discussing with the team next week, as well as proofs. So proofs for smart contracts are very, very important, and we're going to look at how we can provide you with some more information about what that means and how it works. And then, like I said a bit earlier, our marketing and external comp scenes are starting to campaign to create greater awareness and to get more feedback from you as a community about LE itself. So what's that going to mean? Well, it's going to mean things like meetups, live chats, hackathons, and a lot of other things to engage with you, so we're really looking forward to that. So important dates. Well, on the 28th of May, we launched a KAVM testnet, when we said we would. On the 30th of July, we launched the LE testnet, again, when we said we would, and you can see the location there where the testnets can be found. And we'd love to hear from you, so please take some time to check out the site. And if you have any problems, there's a location where you can find out how to send a support request. We'd be happy to help. So we have two testnets now demonstrating the smart contracting capability we're going to provide for the account-based ledger. We have more tests coming up, and I don't want to tell you right now what that's going to be exactly, because I want you to come back. So there will be a testnet number three, and then just all I can say is stay tuned and you'll find out more soon. That's about all for now. We're at a very important stage now with Gogan in terms of what we've delivered. We've got two testnets out there with virtual machines where you can start to really start to experience what kind of smart contracting capability we're going to make available to you. The next few months we're going to see more testnets and an acceleration of the process of integrating parts of the work that's been done so far into Cardano Core. And I'll let you know more about that next month. But also next month what I'm going to start doing is bringing somebody from the team in to talk with us here to find out more about what they do, how they work, and how we deliver technologies here at IOHK. So I'm hoping that will give you more of an insight into how IOHK works and the whole process of creating technology. So thanks so much for your time, and looking forward to talking to you again next month. Bye-bye.