B (4:58)

That's awesome. Thank you, I appreciate that. And I love the backstory. Usually there's a backstory in the first Question. But your technology background probably influenced where you went. You got bit by that bug to get into web3 blockchain, which is awesome. But I really like the big idea, really, that single access point that you saw that there was definitely a need there and turn that into, you know, like you said, a full service of cloud services. So I appreciate that. And Phil, can you explain how Rio leverages Arweave's technology to provide decentralized permanent data storage and what advantages this offers to users?

A (5:31)

So I called Arweave before, like the hard drive. So it stores your data for incredibly long periods of time and you know, no one can censor or take that down. It doesn't require any other payments for it. Right. So all of our services are built on top of that kind of basic primitive. So for example, if you upload data through our network, we distribute it onto the Arweave network. Anything that we index is indexed off of the Arweave network. So that enables developers or apps like ArchDrive for that matter, to easily be able to find your data on this hard drive. We have a name system that allows you to purchase domain names for any of the data that exists on Arweave. If you've uploaded, whether it's, you know, something simple like a PDF or a movie or a full website or app, our name system can map a friendly name to that. Just like how you wouldn't go to an IP address in your browser. In this case you go to a friendly name like maybe Brian and it goes to your blog that's hosted on the REO network. And all of those names, that registry is stored permanently on Arweave. The registry of gateways in the network is stored permanently on Arweave. So whether it's the services that you as a developer could use, all kind of settles that data on Arweave immutably and permanently or the way that the network functions itself like the inner core protocols of the network also leverage Arweave. So it's very, very synergistic relationship. We're really focused on that permanent data storage and all the things around it. Right. And what advantages does that offer to users? Well, it offers that one time payment for really long term storage, really long term immutable storage that can't be changed, that has a timestamp of when you uploaded it. So it's not just maybe like a hash of data. Right. It's, you know, you uploaded it at this time. Right. And it's tamper proof and it has this record of data provenance back to you the uploader, right. Which is all goes back to your cryptographic signature. So it's. You don't get those kinds of properties with S3. And even if you did, that would be one company controlling that. Whereas Arweave is an open permissionless system. Rio network for that matter, also open source permissionless systems. So as a user, you get those things and you really get this concept of like a credible exit from any given application on the network. Right. Like our drive as an app could go away. R Drive the team, us the team building our drive, we could go away, but the ArDrive application is hosted on the Rio network. As long as Rio and Arweave are around, the ArDrive app will continue to be served. Users can still leverage the app. And let's say another app comes along, it could leverage all of that same data that's been stored through our drive. Right. Because it's on this. It's all stored on Arweave and surfaced through the Ario network. So applications can access that same. Let's call it like an immutable data lake. So users really are not locked into any given platform that's built on our network. So it gives some advantages to users. On top of the whole, yeah, you can't get deplatformed or censored. And I know that's maybe not applicable to every user. I'm not particularly worried about maybe getting deplatformed in certain places, but I know that is a thing that happens around the world. And yeah, decentralized networks in general offer those kinds of assurances to their users where they, they do, they can continue to have a voice and can continue to use the service. So yeah, kind of a lot of advantages that the network offers.

B (8:59)

Great, thank you, I appreciate that, Phil. I really love this. Obviously I'm in the blockchain space as well, but just for the edification here of our audience, really like the fact that everything's leveraged, indexed on Arweave, you've created that simple DNS for easy access for the end user. Doesn't matter if you're a developer or just, you know, your grandmother, for example. But truly immutable storage forever. And that's what really like about blockchain. So, Phil, the RNO token is integral to your network's ecosystem. Could you elaborate on its utility and how it incentivize participation within the Rio network?

A (9:33)

That's a really good question. You know, sometimes the token pieces are kind of hard to fully understand and you know, tokenomics is definitely a really difficult subject area. But we felt that our ecosystem did need a token as a unit of value for purchasing services on the network, for staking in the network and things like that. Right. So the REO token, considered a utility token. Right. There's no governance aspects, part of it. Now you can use it to purchase names in the name system, whether that's a lease or a permanent purchase where you can own forever. Those purchases go into what we call a protocol balance, which is then used to pay the gateway operators who are resolving those names, servicing them, serving the data, doing all of those things. So you buy a name, it doesn't go to a DAO or, or company, it goes to a protocol which then directly pays the people servicing the name. So it's different than maybe some other name systems out there. And that's the first service that we really launched with that has a payment, so probably more to come in that area. The network's doing a lot of different services. They all don't have direct payments in it now. But the name system was the first one we launched. So now gateways, to join the network, they do need to stake the REO token. I think it's a minimum stake of maybe 10,000 Rio tokens. And, you know, they can go beyond that stake, of course. And basically what that does is that elevates their position in the, what we call the Gateway Address Registry or the gar. So the more stake you have, the higher you are in the car and the better chance you have to participate in the observation and incentive protocols that happen basically every day. So every day a portion of that protocol balance gets distributed to the gateways who are basically doing a good job. So if you're online, if you are resolving names, then you have a chance of getting the reward for that day. There's also a delegated staking component too, right? Not every person wants to operate a gateway. So if you are a user with RIO tokens, you can delegate them to a gateway for a share in their rewards. And yeah, so these staking and kind of service fees are really the two main utilities of the token right now. And. And yeah, we hope that it incentivizes the name system. And again, there's. We have ideas, thoughts, whatever, for how to implement future incentives for some of those other services that the network's currently performing.

B (11:58)

Thank you, I appreciate that. That's really what I like about this is a lot of times people will, you know, build a token around that, you know, I know you built your RO token around your platform for staking, adding some value, obviously, incentivizing people to utilize and be rewarded for utilizing the system. So I appreciate that. And Phil, last question of the day. Looking ahead, what are your strategic priorities for REO in the next few years and how do you envision the evolution of decentralized permanent data storage?

A (12:26)

Huge question. Right. Every year I feel like my vision changes, especially two years ago compared to now. Stuff with AI. Right. Wasn't in the forefront. You know, maybe looking in the next year. You know, we definitely have, as I just mentioned, ideas on new kinds of incentives and new ways to use the token, whether that's for things around access or indexing or some of the other pieces of the network we want to improve, I should say we want to reduce the need to have to trust any particular gateway. So sure, there's incentives at play to ensure gateways are doing the right thing, but nodes really in any blockchain network could do the wrong thing. You want to make sure that you either have penalties or ways to verify that to ultimately protect users, I think is what we're trying to do. So, you know, we have, you know, this concept called the Wayfinder protocol, which both directs users to gateways so they don't have to know like which one to connect to, which domain name to use. All you should know is the transaction ID or that friendly name to get to your data. Right. The thought is we don't want any single reliance to any single location. So that would mean again, if your name is Brian, you shouldn't have to go to Brian, Arkansas IO or Brian Permagate IO Brian, Arkansas xyz. Just put in your browser, Brian. Right. And this protocol routes you to the most performant gateway and does other verification of what's being served. Right. And now this goes back to. There's a hack recently of, I think it was one of the exchanges and basically I think the team signed some bad transactions because they went to a web app that had a hacked version. So we think tools like this and paired with the fact that on the REO network all of the data is immutable and hashed and can be verified, I think could really provide more protections for people on the web. We have other. Yeah. Thoughts around just adoption in general. Right. It's not necessarily all about building new technology versus using existing technology. So now that we've launched our mainnet, we're going to be trying to do things to inspire new developers, builders, teams to leverage our name system and in our network, et cetera, for building new applications and platforms. Because really the long term, long term Vision is to just create. I guess now this is more 3, 5. Who knows how many years to get here, Brian. But to create basically an Internet that doesn't forget a permanent web that is immutable, that has that every piece of content is timestamped and tamper proof and has this rich set of metadata underneath it that you can kind of map build these different graphs over time. And AI could leverage it to learn whether it's leveraging the data that's been uploaded or the LLMs that have been uploaded, or any of the other inferences related to AI. We see it as a place for users to maintain their free speech on the Internet. Right. Like you look at what's happening today, things are getting deleted, whether on purpose or by accident. And you know, we're losing history, we're losing part of our society. And if you go far back, you know, early 1900s, right. Like you see what happens when we really get to this point of, you know, serious destruction of information and what that could do. So we really see like our platform and decentralized technology in general as really being a way to create, in our case, a new Internet or a synergistic Internet that, yeah, preserves free speech, preserves data and ensures, yeah, your stuff just doesn't go away. So that's kind of, yeah, the grand scheme, I guess, or the. Where we see this maybe evolving on the real long term.

B (16:06)

Great, thank you, Phil. I appreciate that. And yeah, I think everybody acknowledges that there's just been a lot going on over multiple decades in not just our government, but across the world and having a permanent record, as they say. Right. But I like the fact that you're focusing on ensuring that we can create this forever web, as I like to call it, and not having to rely on any particular gateway, having a more secure way to access your data without that fear of being compromised as well. So I really appreciate it. Such a great conversation today, Phil, and it was really a pleasure having you on and I look forward to speaking with you real soon.

A (16:41)

Definitely, Brian, thank you very much. Take care.

B (16:44)

Bye for now.