Irys: The AWS of Web3—A Network of Onchain Utilities | Josh Benaron - Irys

[Music] cool uh so to introduce myself I'm Josh founder CEO of Iris and I'm going to be talking about how iris is building the AWS o of web 3 so what is Iris so iris is a high performance data chain so layer one uh and the idea behind IRS is at its core it enables anyone and specifically developers to store large amounts of data on chains so traditional blockchains could only store very small amounts of data think you know gigabytes would cost you know millions of dollars on ethereum and salana and the goal behind IRS you can store large amounts of data think exobytes or more for a fraction of the cost and cheaper than traditional storage providers um and also cheaper than you know ethereum salano Etc um and the core unlock for us is we yes we are focused on storing large amounts of data we're also focused on this idea of building utilities which is that you don't just store large amounts of data you actually make use of that data and you are able to monetize that and you're able to compute on that data and the goal for IRS is how can we actually not just build a Data Network but also build a network where you can uh tap into these kind of broads set hundreds of of utilities on the Chain so this is kind of talking about uh the virous loop between you know the utilities and the value of the data so the analogy I use is people don't use S3 uh aw ss3 because S3 is an incredible product they use S3 because it's part of this very broad set of services that live on the Chain so if you're a developer you know there's S3 there's ec2 which is compute there's RDS which is a database and all of these things work together in a very kind of composable and seamless way and that's where aws's Mo functionally comes from it doesn't come from the fact that each one of those products are good which is true it comes from the fact that it all worked together very seamlessly and mapping this to Iris the goal is is that as we add more and more utilities to Iris the value of the data that you're storing increases over time so at the beginning developers are using IRS because they want to store large amounts of data on chain and then over time that changes to well now when you store your data in IRS you can monetize your data you can compute on your data etc etc so that's kind of the the high level of of kind of the the vision the vision for Iris so to talk more about like a tangible example and something that we're actually seeing within a r system so as I said the core service is that you can store large amounts of data on chain and it is both cheaper than traditional uh blockchains and also cheaper than traditional storage providers like S3 and other forms of blob storage um but to give an example of this uh set of utilities on the chain and how the composability works you can have and we actually have a team within our ecosystem for example that is building a onchain database where you can store large amounts of data on IRS but also bring that data into a a structured database and then we have another team that is focused on building a a data marketplace with one of the customers being a stability AI actually and the goal there is that okay now users and developers can store large amounts of data on IRS at a fraction of the cost they can inject that and bring that into a very structured uh database a structured data set which makes the data more useful and then you can monetize that structured data natively within Iris as well so you create this level of composability where one they're getting benefits from the the core service that is storing data um and then they're also able to use that data within within a onchain database and also uh monetize that data and actually acrew extra Revenue have an extra Revenue Source um from another application that lives uh within the ecosystem so the way this kind of works is that iris is an L1 right and there are two services that there are two main uh functions of Iris one is to store data as I've said a few times uh the other is actually to coordinate a lot of these resources and lot of these utilities that exist on the Chain so at its core Iris has uh is customer one where it enables you to store large amounts of data um but also we have tons of applications tens of different kind of utilities on the chain that enable you to do different things uh with your data so as I said we have a team focused on on selling your data we have a team that's focused on using that data in a more structured way within a database uh and then we also have another another example is we have a team building Edge comput so tapping into the gpus on the network how can you actually train a whole AI model on the data that you're storing uh uh on uh on IRS and the way that it works is we essentially integrate both storage and execution on the same chain meaning you can again store large amounts of data on chain but also have a verifiable execution layer on the Chain so you can have tokens uh you can have uh utilities and you can also bring the data that you're storing into smart contracts as well so why do people actually build on IRS and it does vary so we see kind of two sets of applications on IRS we have applications that simply want to store large amounts of data on IRS and also retrieve that data so we see those kind of applications across different ecosystems right so we work with teams uh in the world of dii uh on on ethereum we work with nft systems on on salano and eclipse and and other chains some social apps on bar chain uh and then we also do a lot of work around uh archiving chains and also a bunch of like different training infrastructure as well with decentralized training infrastructure on on on different chains so that's kind of one set of use cases where people are simply just wanting to store large amounts of data on chain for a fraction of the cost and then the the second reason that people uh actually use IRS is that you get to tap into the data that exists on the Chain so when you're thinking about why would you build one of these utilities on IRS opposed to on another chain the answer is pretty simple because there is so much data on IRS there's kind of this idea of uh to use investors terms like Dill flow this distribution where you can just by deploying an IRS you can already tap into one the data that exists on the Chain but two the utilities that already exist so to use the I'll stick with a database example to uh keep the or or even the yeah I'll use the monetization actually example uh to stick to be a little bit more consistent um the reason they would Deploy on something like IRS is that one there's a bunch of like data sets that exist on IRS that they can go and sell to stability AI Etc um but then there is also uh a bunch of like utilities think about the data space where they can into these like different services that kind of coexist with uh with their application on chain that they can drive more value from and and that's more of a a distribution play by being on the same chain they can tap into that kind of composability that uh occurs by being on that chain so keeping this one short um so in terms of what you can do today so some Builders you can uh go and build uh data applications you can start storing data retrieving large amounts of data there are no limits it's it's very cheap uh you can store data in both a temporary and a permanent way uh and then for people interested in building data utilities you can already Deploy on our Alpha test net so you can already deploy smart contracts you can do programmable data which is the idea of bringing data into smart contracts already um and all of this is documented uh within our docs which is docs. iris. XYZ but yeah feel free to ask me any questions afterwards if uh if you have any p