 So we advise our clients that they should really consider middleware when looking at blockchain. The reason for that is that blockchain by itself is not a total solution. Blockchain is finding its place as part of overall solutions and when you're automating workflows. So what you need is you need something that sits above the blockchain database that enables the total end-to-end workflow. Which means that you're going to have data that you don't want to put on the blockchain, such as personal data. In fact, we did a paper on that on GDPR and the intersection of blockchain that is available on our website, but you need to make sure that certain data doesn't reside on the blockchain because the blockchain is immutable. Social information is one of the elements you probably, in most cases, don't want to put on the blockchain, especially with the regulations that are coming down, such as GDPR. And there's other data that you're going to find that maybe you don't want to exchange via a blockchain throughout your supply chain. But you want that information linked and available as part of your workflow, your business process. Or you should put that data within traditional databases. It might link to your website. So you need to figure out a total solution as you're developing your use case solution that includes blockchain, but it also includes a lot of the traditional elements. I would add one more thing about blockchain automation is its business automation. A lot of our members have made the mistake of saying, IT department, go evaluate blockchain. That's not the best place for blockchain. Blockchain requires your technologist, but it's a business process, business transformational tool that really needs to be driven at the business level, not the technology level.