>>60926959
>It's always very specific, the people that want internal data integrity for their internalsystems and to be able to verify logs and verify tamperproofness are not interested in making anything public. The people interested in makingthings public via onchain data, they're interested to some degree incross-chain, they're interested in the reach of the data, they're interested in markets because a lot of the data iseconomic in nature. The trust issue use cases are alwaysvery specific. They're very, very specific implementations. That's one of the things the Chainlink community and the people who implement Chainlink for these institutions beyond us usually do agood job at is they're able to take a very specific problem and think throughhow to solve that problem. And the problem might have many different parts of it. It might have a dataissue, might have a cross-chain issue, might have a compliance issue. And that's once again why Chainlink is inin my opinion so unique. And that if you have a data issue and a compliance issue and a cross-chain issue,you really can't solve it right now with any other system other than Chainlink. You can try and use three separatesystems that don't work with each other and don't want to work with each other or you can just go to go to a single platform. So, Chainlink has really become now closer to something like an AWS where you can show up and you enteran ecosystem of providers of primitives of building blocks of tools and serviceswhere you can solve your problem in a comprehensive way.