 Yeah, my name is Harit Adaghan, CEO, co-founder of a company called Superbooks. We have a continuous integration and release management for blockchain applications, not only for the smart contracts, but for the blockchain applications as well. And one of the things I wanted to talk about today is the original topic is how can we reduce release anxiety for the blockchain domain, so aka release management for smart contracts. And I'm not talking on the tuning level, I'm talking on the day-off level. So first and foremost, like obviously, automate, automate, automate. So one of the most important parts when you want to reduce your anxiety when actually performing deployments to manage them to anything, like in blockchain, it's great to automate it as much as possible. The reason to do so is first and foremost, not only for your own sake, because you can repeat it anytime and it's always deterministic, but also because, for example, when you're dealing with auditors and all that, they can actually also audit your deployment strategy as well. So it's quite important to be able to alter your entire line, actually, not only your contracts and how you actually development, but also how you go at everything to manage them. So of course, one thing is, I'd actually run into a few people and talk to them about this, and especially when you look at companies nowadays, I don't know if many of you guys like them relate to this, but like what is usually the flow nowadays, what happens is like, okay, you might use some form of CI provider, Circles CI, GitLab and try this thing of this. And then that's great to be able to reach to testing. So usually what happens is people actually have their own pipelines and their own everything, build pipelines from like continuous delivery for business, and then when they need to actually deploy to maintenance, they actually just use remix, or they actually use locally deployments. And it's like, what the fuck, you should actually have immutability in your deployment, so you should actually build ones and then be able to promote your builds between different environments that's the one-on-one on DevOps, but it's not happening. And why it's not happening, and it's because one of the main reasons that CI issues have, like right now people don't use them, is because you need to expose your privacy. So one of the things that, as in Superblocks, so we actually created this full CI service and then release management for smart contracts. So as you can see, for example, this is a normal CI that you would actually have with some demo that you put into repository, and then you have different scripts that you can execute, especially important that is Docker and Docker, so I can actually build anything. But one of the interesting parts in here is like, okay, you can actually type your Docker builds, for example, when you're doing your CI part, with the, for example, the e-drop, give a registry image, and then a commit. So you can always trace it straight from your commits all the way through every different network that you're deploying to be able to make sure you have full traceability of your deployment. And not only that, as you can see also, for example, once we actually can use the image that we actually created in the CI process, you can also use that image, which is immutable, and you can have all your dependencies already resilient, so you don't need to do MPN install, for example, to be able to perform migrations, in this case, if you're using Truffle. So one of the things that includes everything together, and it's like, how the hell is that possible to be able to not expose your private keys? So one of the things that we actually created, and right now we are working towards having this for Truffle as well, is that you can actually provide a super provider in your Truffle configuration. And then what we do with this is to be able to set up a tunnel all the way from our runners to your browser, so we would actually queue out all the transactions that you need to sign, and then they would actually pop up in the dashboard of the CI, and then you'll be able to actually sign those transactions using metamask or ledger or anything, so we would actually never have to look at your private keys to be able to sign those transactions. And not only that, we actually will also extract all the artifacts that you're creating, all the ABI, all the contracts having deployed, and be able to trace all your deployments to make sure they're succeeded. So you would be able to see, as I say, your bills from CI all the way to the payment. And then finally, something looking like this. In this case, as I say, I hope I will come up. And then, of course, if you want to contact us and learn more about DevOps, and go to the integration board, specifically for closing, please contact me at the cargo or the super blocks, and thank you so much for listening.