Brian Jordan (3:26)

Thank you. I appreciate that. We absolutely are seeing that proliferation, explosion of cloud usage just in the last five to ten years of explosive growth. But I appreciate you breaking that down for our audience and I agree. I think there's a lot of room for disruption and I know with decentralized cloud or community, cloud is kind of the route that you're going and we certainly support that. Sebastian, what were some of the biggest challenges you faced when designing the tokenomics and legal framework for impossible cloud and how did you overcome them?

Sebastian Pfeiffer (3:56)

Yeah, first of all, thanks for the support, Brian. So when designing this, there's essentially this different routes you can take, right? So I think the big problem is because it's still a, I would say relatively young industry in web3, things can get confusing very fast and actually change quite quickly.

Interviewer (4:16)

Right.

Sebastian Pfeiffer (4:17)

On top of that, because it's so young, you have all these hype projects. Some of them frankly, as we know, are scams, right? So you have to be careful and laws highly depend on the local regulation. So we said, when we set this project up, we said, okay, from the beginning, right? We are in it for the long run. From the beginning, let's have legal certainty. Anybody that's involved with the project should have legal certainty. We went for Switzerland.

Interviewer (4:46)

Why?

Sebastian Pfeiffer (4:47)

Yes, has, I would say globally speaking, strict rules, but they're very clear, right? There's been rulings and many, many past examples of projects to learn from. So that's why we said, okay, let's pick Switzerland because it's strict, right? Because there are clear rules that make it easy to navigate and anybody involved in a project. And the second reason why we went for this is because it's, I would almost say, a golden standard, right? So for you are compliant in Switzerland, there's a high likelihood you will be compliant in other regulations when you offer your product or are traded on exchanges that are based on those going to be likely compliant with those Local regulations as well.

Interviewer (5:28)

Right.

Sebastian Pfeiffer (5:29)

At the end of the day, what you want to make sure, and we want to make sure is that our token ICT is not an investment.

Interviewer (5:36)

Right.

Sebastian Pfeiffer (5:36)

So essentially there's three major token types.

Interviewer (5:39)

Right.

Sebastian Pfeiffer (5:39)

So there's a security payment, utility, and we wanted not to fall under that security.

Interviewer (5:45)

Why?

Sebastian Pfeiffer (5:45)

Because this is the most of the projects actually out there. This is the I project. Yeah. So actually you have to be very careful here because again, in Switzerland it's very strict. Once it's a security token, it essentially says that it promises future gain. And what we want to do is we want to create an ecosystem that's going to be able to, as I mentioned before.

Interviewer (6:07)

Right.

Sebastian Pfeiffer (6:08)

Disrupt the traditional cloud. That's what we try to build with our token, essentially an access token to this network.

Interviewer (6:14)

Right.

Sebastian Pfeiffer (6:15)

So instead of saying, okay, we are here to build a product that then fuels a token, we kind of flip it and we say, okay, let's use the token that fuels this ecosystem, which hopefully provides a meaningful alternative to these cloud products. Again, because we're here for the long run because we want to build trust in our system.

Brian Jordan (6:35)

Thank you. Really appreciate that. The industry, while blockchain essentially has been around for, gosh, almost 15 years, the industry is still in its infancy because we still have a lot of people that are slow to adopt. But what I really, I guess, resonated with me is everything that's changing daily in this industry. You did do the smart move and pick something that has some legal foundation. And of course you took that to the next level and picked Switzerland, which we know they have the most highest regulatory environment probably in the world. So really appreciate that. And I appreciate that you're moving into this space with some vigor, but also obviously being cautious around the legal side of things. Sebastian, in a landscape dominated by hyperscalers like AWS and Azure, what makes impossible cloud a compelling alternative for enterprises?

Sebastian Pfeiffer (7:23)

So I would say that there's a few reasons that could be considered here.

Interviewer (7:27)

Right?

Sebastian Pfeiffer (7:28)

So let's start with the risk management reasons.

Interviewer (7:31)

Right.

Sebastian Pfeiffer (7:32)

So with a lot of market share within these big players, like a side of politics, I just don't think it's a good idea to hand all these businesses essentially in the hands of these few providers. Because one day, who knows what happens? Let's say that provider doesn't like you anymore, then basically all your business operations are gone.

Interviewer (7:56)

Right.

Sebastian Pfeiffer (7:57)

That think from a risk management perspective, that's one. Then second, I think it's a systemic risk.

Interviewer (8:02)

Right?

Sebastian Pfeiffer (8:03)

So if that one provider has, let's say, a Technical outage. A lot of businesses are affected and this actually happens more often than we think. For instance, the my slack is down every once in a while, right? But that's just the service I use. I imagine there's many, many more services that build on AWS that are out that I don't even see. Then from a technological perspective, there's also reasons. So if you think of it as a bigger picture, centralization in a way slows innovation.

Interviewer (8:30)

Why?

Sebastian Pfeiffer (8:31)

Because it limits participation as a decentralized project. And by making it composable and open, we invite anyone to contribute, right? So we live kind of this DNA of there's always smarter people outside a company than within. And by inviting all these smart people to contribute to this ecosystem and to be share benefit from it, we envision that we can actually be more innovative than centralized providers. Then you have architectural reasons, right? So you have edge performance. For instance. Again, take AWS, they have maybe 30 data centers around the world. What we envision to do here and what we set out to do from an architectural perspective is set the system up in a way that it allows not 30 but hundreds of nodes around the world. What this enables is significantly reduces latency and depending on your other that can actually play a crucial role for your business because you have that edge performance. Additionally, it's all of this is community owned, so I wouldn't underestimate this as well. Again, there's no single entity or individual in the middle playing a role here. It's all community owners, which makes it, I would say, resilient to any structural challenges. And I do want to emphasize that all of this, right, all of these advantages should come without any potential performance sacrifices. I keep iterating on this fact because I think that there's a lot of Web3 projects out there with really great smart people, great visions. However, they lack the typical performance that the average user is used to. And then they have to kind of see, okay, do I want to sacrifice here and for all these other advantages or should I have whatever I have now just something better, right? And that's what we set out to say, okay? We offer all these advantages and do not sacrifice whatsoever on performance. So depending on where you are, as mentioned with edge performance, you're actually more performant than AWS when for instance, using our services.

Brian Jordan (10:33)

Thank you, that's very helpful. You know you highlighted the pros and cons, right? With some of the big providers out there, from a risk management perspective, really all your eggs are in one basket. And you talked about systemic Risk, you know, having downtime for tens of thousands of customers at a time when there's an outage, obviously the technological risk and limiting that participation with these providers. But with you, alternatively, you invite some great minds into this space for some really good innovation. And then of course, because it's decentralized and it's located around the world, that edge performance with the added resiliency and speed is just a plus. So really appreciate that helps me, it helps our audience today. And Sebastian, last question of the day. Can you walk us through how token based incentive systems are used in impossible cloud to align interests across contributors, users and partners?

Sebastian Pfeiffer (11:22)

Again, here we come from the lens of the product slash demand first. Now at a possible cloud network, we set out to design this ecosystem in a way that it's demand centric. So demand in a sense, there's real customers using it today. So what are these kind of customers that are already using our ecosystem?

Interviewer (11:42)

What do they want?

Sebastian Pfeiffer (11:43)

They want reliable services. So that's what we started when designing our tokenomics, right? So anybody that onboards hardware to our protocol to this ecosystem, yes, there is kind of a, you can envision it as a base fee, right? They do get their bills paid, but they get a dynamic incentivization depending on utilization. Right. So why did we do this? In the long run, this will incentivize good reliable hardware that it's actually being used to thrive, kind of quote unquote, weed out the hardware that's not as good, not as much in demand. So that's basically what we as a mantra set out to have only the best performing hardware in the ecosystem, again based on utilization. Second thing I believe is we have this what we call paper node system, right? It's essentially validating and putting a transparency layer on top of it. So anybody can run these nodes and what they do is they show, okay, this hardware and the service is coming at these quality criterions are they actually fulfilled? And this is basically transparency layer on top. Both of those combined will over time provide a resilient ecosystem that's demand driven. Again, really, really important because we as a project stated, okay, we have to solve a problem first and if the demand is there, we scale according to that demand.

Brian Jordan (13:07)

Thank you so much, I appreciate that. And I just love this model, really. Do we support blockchain? Obviously we're built on Blockchain this publication and love to have folks that are in this space, but you're taking it to a whole new level and I really love that you've designed this ecosystem so it's demand centric. Customers obviously want reliability but what I really like is you're incentivizing your community with these dynamic incentives based on usage. Right? But that transparency layer that you're putting there through these hypernodes I think is also awesome because you're letting the customers kind of like get in and test drive and see what's under the hood. Again. Love this stuff. I can't believe how we're taking Web3 Blockchain DeFi to the next level with people like you in the world. So I really appreciate that Sebastian.

Sebastian Pfeiffer (13:54)

Appreciate it Brian.

Brian Jordan (13:55)

Absolutely. It was certainly a pleasure having you on today and I look forward to speaking with you real soon.

Sebastian Pfeiffer (14:00)

Amazing Brian. Thanks again for having me. And yeah, I'd love for the audience if you're into our project for free to get in touch. We're always looking for people to contribute to this growing ecosystem and make cloud finally decentral.

Brian Jordan (14:12)

Bye for now.