Philip Mataras Podcast Transcript
Philip Mataras joins host Brian Thomas on The Digital Executive Podcast.
Brian Thomas: Welcome to Coruzant Technologies, home of the Digital Executive Podcast.
Welcome to the Digital Executive. Today’s guest is Philip Mataras. Philip Mataras is the founder and CEO of AR.IO, the first permanent cloud network offering a groundbreaking suite of decentralized web services designed to transform how we store, share, and manage data online. Under Philip’s leadership, AR.IO has harnessed the unique capabilities of the Arweave Perma Web, delivering an immutable, province driven and economically sustainable model for businesses and individuals seeking unparalleled reliability and security.
Unlike traditional cloud infrastructure, AR.IO’s approach combines decentralized storage, access domain services, and hosting solutions, empowering users with transparent fail proof and efficient data management capabilities with a professional background steeped in emerging technologies. Philip has always been driven by a passion for innovation and a commitment to reshaping digital ecosystems for the better.
His vision for a more open, trustworthy internet has guided him to champion the commerce potential of blockchain-based tools, open source collaboration, and user-centric design.
Well, good afternoon, Phil. Welcome to the show!
Phil Mataras: Hey, good afternoon Brian. Pleasure to be here.
Brian Thomas: Absolutely, brother. I appreciate you making the time. And today we get to talk a little bit about blockchain anyway and the AR.IO network. So lemme jump right into your first question, Phil, if you don’t mind, could you share the journey that led you to found AR.IO Network and your vision for the company’s role in the future of data storage?
Phil Mataras: Yeah, I could definitely talk about my journey. It’s been maybe, gosh, coming up to five years now, being a founder and entrepreneur and, you know, looking at my background, I was in enterprise it, working at a big four company doing enterprise architecture, solution architecture, a lot of things in, in the cloud and on premises and a lot of system design and infrastructure design.
And maybe in, gosh, I think it was 2017 or so, I had. Gotten the blockchain bug, you know, the decentralization bug went down the rabbit hole. It was a, a Ethereum specifically that caught my eye, this concept of like a world computer. I was like, wow, that’s, that’s pretty cool. And, you know, no one can control it.
And, and all of those properties of, of a blockchain. And in early 2018 I had discovered Arweave, which is a blockchain built for storing data permanently. And it had this concept of pay one store forever. And that’s really what got me hooked. I was like, wow, that’s, you know, very different than every other kind of subscription based storage platform.
So kinda the years went by in 2020, you know, coronavirus hit and in those years between 2017 and 2020, I like really went deep in the Arweave ecosystem. I became part of a dao. I of course learned more about Bitcoin, Ethereum, blockchain, all of those things. And yeah, summer of 2020 is when I was like, Hey, time for change.
Time to really become an entrepreneur. And I started with this idea, or this app called R Drive, which was a very simple, easy to use Dropbox like app, but stored your data permanently on R we, I. Whether public or private. So really simple to explain like my mom could use it, um, which is very different than my career, right?
Which was difficult to understand, you know, enterprise IT stuff. So I really wanted to do something that was retail consumer focused. And yeah, summer 2020 is when I quit my job and, you know, as part of a, an incubator in the Arweave ecosystem and received some very small angel funding to continue to work on the app.
And it was really in. Maybe it was late 2021. The NFT craze had, you know, really taken off in that summer. Um, and our weave had it seen a huge explosion in growth. And even though our drive, you know, successful and, you know, we were getting uptake in usage and, you know, deploying all kinds of new things there.
We saw a bigger opportunity on the infrastructure side on Arweave, and that was because, you know, even though the RWE network itself, the hard drive, right, that’s replicating the data around the world, even though that was decentralized and had a strong distribution of nodes, there’s only one access point to get your data in and out.
And we saw an opportunity there to. Basically take that single access point or that gateway and turn it into a decentralized network of cloud services that upload your data, download them, download it, cache it, provide an index, querying a domain name system. You know, a lot of these things that you would typically see maybe in an AWS.
And you know, that idea kind of turned into the AR.IO network. And yeah, it’s been a, a long road. We just launched our main net a few weeks ago, so it’s, it’s, it’s been quite the journey over the last four years going from R Drive to, to AR.IO and it kind of came back around again. Went from something that was like retail, easy to explain R Drive app to AR.IO network Cloud services.
Definitely more technical developer focused, but yeah, a platform that could support the next generation of apps on the internet. And yeah, really excited about it these days.
Brian Thomas: That’s awesome. Thank you. I appreciate that. And I love the backstory. Usually there’s a backstory in the first question, but to your technology background probably influenced, uh, 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 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 AR.IO leverages rws technology to provide decentralized permit data storage, and what advantages this offers to users?
So I called RWE before, like the, the hard drive. So it stores your data for incredibly long periods of time. And you know, no one can sensor 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 RWE network.
Anything that we index is indexed off of the RWE network. So that enables developers or apps like R Drive 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 our weave. If you’ve uploaded, uh, 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, uh, in your browser. In this case, you go to a, a friendly name like maybe Brian, and it goes to your blog that’s hosted on the AR.IO network and all of those names, that registry is stored permanently on r we, um, the registry of gateways. In the network is stored permanently on our weave.
So whether it’s the services that you as a developer could use, all kind of settles that data on our weave immutably and permanently, or the way that the network functions itself, like the inner core protocols in the network also leverage our weave. So it’s very, very synergistic relationship. You know, 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 the 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 RWE is an open permissionless system, AR.IO 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 R Drive as an app could go away. Our drive, the team, us. The team building R Drive, we could go away, but the R Drive application is hosted on the AR.IO network.
As long as AR.IO and RWE are around the R Drive 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 our weave and surfaced through the REO 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 again, gives some advantages to users on top of the whole, yeah, you can’t get de platformed or censored, and I know that’s maybe not applicable to every user. I’m not particularly worried about maybe getting de platformed 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.
Phil Mataras: 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 our weave. 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 incentivized participation within the RO network? That’s a really good question. You know, sometimes the token pieces are kind of hard to fully understand and, you know, token ons 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, and things like that, right?
So the AR.IO 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, what 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 a company, it goes to a protocol which then directly pays the people servicing the name. So it’s different than, than maybe some other. Name systems out there. Um, and that’s the, the first service that we really launched with that has a payment.
Um, 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 AR.IO token, I think it’s a minimum stake of maybe 10,000 AR.IO 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, I. 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 are 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 AR.IO 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 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.
Brian Thomas: 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 AR.IO 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 AR.IO in the next few years and how do you envision the evolution of decentralized permanent data storage?
Phil Mataras: 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 wanna make sure that you either have. Penalties or ways to verify that to ultimately protect the users, I think is, is what we’re, 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.ar.io or brian dot permi gate.io or brian.ar 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 uh, some bad transactions ’cause they went to a web app that had a hacked version. So we think tools like this and the paired with the fact that on the AR.IO 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. 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 main net, we’re gonna be trying to do things to inspire new developers, builders teams, to leverage our name system and, and our network, et cetera, for building new applications and platforms.
’cause really the long term. Long term vision is to just create, I guess now this is more three, five, 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, 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 yeah, 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 19 hundreds, 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, uh, in our case, a new internet or a, a synergistic internet that.
Yeah, preserves free speech, preserves data and, uh, ensures Yeah, your stuff just doesn’t go away. So that’s kind of, yeah. The, the grand scheme, I guess, or the, where we see this maybe evolving on the real long term.
Brian Thomas: 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, 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.
Phil Mataras: Definitely Brian. Thank you very much. Take care.
Brian Thomas: Bye for now.
Philip Mataras Podcast Transcript. Listen to the audio on the guest’s Podcast Page.
