#238 Dominic Williams Reveals His Vision for the Internet Computer (ICP)

32:16And you're given the illusion that this code is synchronous, but it's not. it's actually asynchronous. And I can call your function and I'll get a result. But we're actually running in parallel and you're on one subnet and I'm on another subnet kind of thing. And an actor has private state. And in this case, the software logic runs in its own persistent memory. And I don't want to get too technical again, but on the internet computer logic and data is kind of the same thing so it's just state and instead of having a database and files you just define your programming abstractions like this is a variable like you know for example define a blog post as you know title content likes comments or whatever right and then you just define your blog as like you know something along the lines of var blog log equals array of posts, right?

33:13And it all just lives in persistent memory. And that's a paradigm called orthogonal persistence. That's another big innovation that you see on the internet computer. We've been trying to completely reimagine software in a more modern, effective form. And that actually turns out to be very important as well for working with AI when AI builds completely solo. You know, in the self-writing computer, or self-writing internet, I'm sorry.

33:42You talk about talking to a chatbot that will code a piece of software. Where does the chatbot reside? Well, so the self-writing internet's a general concept, and we're obviously developing technology that we feel enables our own version. There's a platform called Caffeine. You can't log in yet, but it's a caffeine.ai. And that is actually chatbot large language model agnostic. So in principle, any large language model could be used.

34:25And in fact, we'll probably give people a choice. That being said, number one, we are tweaking these models and fine-tuning them for the specific task at hand and so they can better use the technology, special technologies involved. And that bot could be something like a fine-tuned version of, you know, GPT-4-0, or it could be something like DeepSeq 3 or even R1, depending on needs, that's running on the internet computer itself. At the moment, the internet computer runs custom AIs. And although the capabilities are scaling pretty rapidly with people working to extend internet computer protocol to scale back the limits, currently you can run a neural network that does facial recognition very easily.

35:24You can run people already running DeepSeq, but with a very small number of parameters. Later this year, you probably get up to like, I don't know, maybe 16 billion parameters, something like that. But oftentimes for coding tasks, you want larger models. Because for example, you want them to be multilingual, because this is self-writing internet, it's a paradigm for the world. People need to be able to instruct the AI in their natural, their own native language. And the internet computer will support something called AI workers, which are kind of like, it's AI inference that's been made deterministic, that's running in replicated forms.

36:06So you can be sure it's tamper-proof. You know, that would be an alternative. So it could be, you know, on the one hand, it could be GPT-40. On the other hand, it could be DeepSeat running on the internet computer in a deterministic tamper-proof form. And there might be, you know, different, or there will be different you know, considerations like, you know, cost, um, that kind of thing. Yeah. Let's stop for a sec. So you, you said there are people running a scaled down version of DeepSeek on the, okay. So, uh, is, is, is, are the, uh, is the source code for DeepSeek and the weights divided up by function or into units and then the units are distributed or is the entire model replicated across all the nodes?

37:12I'm just trying to figure out where... Yeah, so, I mean, currently, when people are running custom AI, that it's on, you know, subnets dedicated to application logic. So it's replicated 13x. And I mentioned that probably 13x is overkill. And in the future, you can imagine subnets with lower levels of replication, but without getting technical details, the internet, there are other changes. While it's easy to create a subnet with low levels of replication, even 4X replication, there are security concerns. So there'll be some other work that's involved in updating the network so that it can handle like lower security, lower resilience subnets.

37:59But I think in the future, people might choose to run AI at like 4X or 7X replication with lower security privileges. But at the moment, it's running 13X. and generally I haven't looked into how they're doing it, but I'd imagine it's just a few canisters. A single unit of software can have up to 500 gig of persistent memory associated with it currently. But the current framework is 32-bit. It's actually, as we kind of speak, I see internet computer protocols being upgraded to support 64-bit WebAssembly, WASM compute, And so the 32-bit environment creates some limitations, and that's why you've got these models with relatively tiny numbers of parameters.

38:52But 64 bits coming as we speak, and the amount of sort of main memory, if you like, that you don't see in a canister, which can be used to store cache weights and so on, is going to be rapidly scaling. But having said that, I don't think that's suitable for self-writing internet. Self-writing internet is a mass market, will be a mass market phenomenon, and you need like AI to run much more efficiently. So I think it will actually run on these like standard models that are running on these things called AI workers within the network. That's something that's coming this year. So you'll see like different models being used in the self-writing internet.

39:36And people will often make choices based on considerations like, you know, cost and security and the ability of the model and things like that. What I will say is, you know, when we fine tune DeepSeek, we've been getting some really, really good results. You know, the best out of the box proprietary model is hands down Claude Sonnet for coding, but you can't fine tune it. You can fine tune for GPT-4O. And when we fine tune it, we can take it beyond Claude. But DeepSeq, it's quite a large model and we've been playing around with it, but the results we've been getting are very good. Yeah. So I'm correct that the model may be replicated in full across the nodes.

40:32Yeah. And to access the model, then you have to go through the blockchain. The blockchain either pulls together the different units and delivers. I mean, it's the interface between the user and the... Yeah. No, no. So that's the difference. So I think there's a lot of confusion in the space because people can't really get their head around the capabilities of the Internet Computer Network. The internet computer basically creates a single serverless cloud environment that is essentially running on a blockchain. And the reason this is hard for people to crock is that, you know, today there's no other blockchain in existence that can even store a phone photo, let alone store, you know, the hundreds of gigabytes of weights associated with a large language model and actually run a large language model.

41:31And so, you know, the confusion I think comes about that a lot of people talk about like, oh, we've got this decentralized cloud blockchain. And all they're doing really is creating a kind of tokenization and access controller. But people spin up Docker images, if you like, right, that you can run, you can acquire control of on payment of some tokens. And these Docker images sometimes, actually more often than not, actually just running on Amazon Web Services, but you're just creating like a tokenized interface to Amazon, but they can also run on people's home computers and stuff like that. I mean, the internet computers, like hundreds of people have been working on it for years, like very senior computer scientists.

42:20It's a whole different thing, traditional blockchain. Traditional blockchain is like token databases, You know, essentially, sometimes highly optimized, like Solana can process a large number of transactions a second, which have very little computer associated with them for things like meme coins. But the internet computer is a very different kind of beast. It's much more complicated, involves much deeper science and technology, and provides like a kind of network that is you know pretty unique and when you build on the internet computer you're building you know you're creating code that runs on the network itself right within this serverless cloud environment where the software is really a form of smart contracts and you know it's tamper proof, so you don't need to protect it using cybersecurity.

43:20And it's unstoppable and you can make it autonomous, which means that it can exist without a human or organizational owner and controller, either in unmodifiable form or under the control of a digital governance system. And the network is using this scheme I mentioned, deterministic decentralization, to ensure that the individual units of software are being run with the levels of security and resilience that they actually need in order to meet the guarantees that the network provides. And the Internet computer is envisaged and designed as an alternative to traditional IT. We're trying to reinvent compute.

44:03So, we want the world, currently software systems and the services and applications they create are really the foundations of modern society. I mean, there's 8 billion people on earth and they couldn't possibly be supported, kept alive without a very high degree of computerized automation. And also, things like social media are part of our everyday lives. It's how we live. And so we believe the computers are a societal foundation. and therefore it should be part of the internet itself, not part of closed proprietary private computing infrastructures. Or at least there should be an alternative and people can build on the internet rather than these closed proprietary private infrastructures like Amazon Web Services and Google Cloud.

45:00So that's our vision. The vision is that you're building on the internet. Now the internet can host software as well as connect it. And this software has new properties and capabilities, such as being tap-proof and unstoppable and optionally autonomous and so on. The whole thing is on the network. There's no traditional IT involved. It's not like a traditional blockchain that's just acting as a gatekeeper through tokenization and some very simple access control functionality to centralized traditional IT, whether that's a cloud or somebody's gaming computer in their basement, everything runs on the internet computer network itself.

45:40Right. And the nodes of the computer network are, as you said, distributed across geographies and jurisdictions and each node has a copy of the software, not just a unit. Within a subnet, yeah. So if your unit of software or the unit of software you're interacting with is going to be assigned to a subnet, and then that subnet comprises a bunch of node machines from different node providers installed in different data centers and different geographies and different jurisdictions. And that subnet is efficiently replicating the computing data of that software, but it's doing it using Byzantine fault-tolerant distributed computing techniques, which basically means that even if an adversary takes physical control of one of those node machines or some subset of those node machines, they cannot corrupt the data hosted by the subnet and they cannot interfere with its operations.

46:51And that's, of course, how you get it's the same as a blockchain in a sense. And that's how, you know, that's why running a Bitcoin node won't allow you to steal Bitcoin. Right. You're just part of a much bigger network and you'd need like half of the hashing power to more than half the caching power to corrupt it, at least in principle. So, you know, you get these guarantees. But, you know, the difference with, I think, the networks that got a cache or something like that you mentioned was, you know, what's happening there is like you've got a blockchain that has a ledger and has tokens. And that's really like giving people access control to these centralized computers, for example, a gaming PC in someone's basement or, you know, an Amazon Web Services instance, which ultimately, of course, is, you know, just running on some specific machine in Amazon Web Services data centers with a bit of virtualization going on.

47:47This is very different. Like, you know, if you install some software on the Internet computer, it has no location. its location is cypher space. And the network dynamically decides where its data is and computation is replicated. So these subnets, by the way, I mean, the membership of these subnets is dynamic. Like the network can add new nodes as needed. It can remove failed nodes or remove them for other reasons. If a subnet is overloaded, it can actually split it into two subnets by spawning to divide the load dynamically. And so, if you ask like, where is this software that's been installed on the internet computer, or even where is this AI model that's been installed on the AI computer, on the internet computer?

48:37The answer is it's all over the world, right? And it's particular location is also dynamic. It can change based on what the protocol does, which has this thing called the network nervous system, which kind of centralized governance system that actually has automated control of the network and can add nodes to subnets, remove nodes, create new subnets, split subnets, that kind of thing. So really, what's the location of software and data on the internet computer? Cypher space. Yeah. And you have this, what's the incentive for the node operators? You have this concept of reverse gas. Yeah. Can you talk about that?

49:18Sure. So on a traditional blockchain, like Ethereum, when you interact with a smart contract, you have to pay some gas to pay for the computation. And gas on Ethereum is like fuel for computation. So with a traditional blockchain, every transaction is crafted manually by the user. So you have a wallet like MetaMask and you craft this transaction that will call into a smart contract. And when you craft that transaction, you specify how much you'll pay for the computation. And there's a kind of fee market. And so you add the gas as part of the transaction effectively. And then using the key that the wallet holds, you press send, it gets sent to the network and you get told when it's executed.

50:17So very clearly, if you have to manually create every function call to a small contract using your wallet, this can't be used as a basis for building a social network. You need small contracts that can not only run much more efficiently and scalably in many orders of magnitude, but that can do things like process HTTP to create interactive user experience. So you have to, you know, the whole thing is re-architected and re-imagined. On the Internet computer, there's a scheme called reverse gas. And that means that the software pays for its own computation. And it does so using something called cycles, which are analog to gas on Ethereum.

51:01And it's, you know, the best analogy is that it's like an electric car. So if you have a Tesla, you know, you plug it in to charge up the battery and you drive around as it drives around the battery gets depleted and you have to plug it in again or if you're on the move go to a super charging station or something like that right and um software on the internet computers um kind of similar you charge it up with these things called cycles um as it performs computations and stores data in its memory and so on it depletes these cycles um if it runs out of cycles it stops working um and you've got like three months to fill it up before it gets scavenged, right?

51:44But anybody can fill it up. Like, say you're a bit of software and I'm using you and you run out of cycles and stop working. I can send more cycles and you'll start working again. So the tokenomics works as follows. There are these things called ICP tokens, which are multi-purpose kind of utility token. They They play the role of cryptocurrency within the network. And they also allow you to participate in governance, like you can stake them to create a voting neuron within the network nervous system. But for the purposes of understanding the basic economics, number one, you can convert these ICP into cycles.

52:24And the network is aware of the value of ICP because it has Oracle functionality. And ICP tokens worth one XDR, an XDR is a standard drawing right of virtual currency defined by the IMF. I don't know what it's worth now, but last time I looked, it was like, you know,$1.40 or$1.50, right? And if you convert ICP tokens worth one XDR into cycles, you get a trillion cycles. And cycles give you a predictable amount of compute. So it's like electricity. So, it's like that you know that it's going to cost you so much to charge the battery of your electric car with this amount of electricity kind of thing.

53:11So, the computation on the network creates demand for ICP, ultimately, the ICP token, which is named after the protocol, Internet Computer Protocol, because people having to to convert ICP tokens into cycles to power their compute in the mode of an electric battery using the reverse gas model. On the other hand, the network, so that's deflationary. On the other hand, the network mints new ICP tokens to reward people, not directly, but reward people participating in governance who can generate ICP through a mechanism. And it also mints new ICP for these people running the node machines. But it's not like a traditional blockchain where they're sort of speculating.

54:08The governance system of the network is setting expected costs for purchasing node machine hardware, co-locating it, operating it, paying for the bandwidth and so on. And the network decides that they should get a certain return over four years. And then ICP is being issued in varying amounts, depending on its current price, in order to cover the, you know, or to remunerate the node providers. And of course, if you think about it, this is completely necessary because node providers you don't have fixed costs. You know, they have to, like a node machine costs you about$20 ,000 to build and some of them are operating quite large numbers of them.

55:01You have to co-locate it. So you have to have contracts with data centers. They're consuming bandwidth. Again, you've got to have a bandwidth contract. So in order to have a stable network, the network remunerates them in a predictable way. And then the network also modulates the remuneration available in different areas of the world, not only with respect to differing costs, but also to create incentives to deploy these node machines in different parts of the world. Because the network relies on decentralization, just like the internet. So, for example, compute might be a bit more expensive in Singapore, but initially at some point the network was not only willing to pay that, but a bit more to incentivize people to deploy these machines in Singapore and data centers.

55:58But if you look at the dashboard of the internet computer, you'll see there's no machines installed in data centers all over the world, like this one in South Africa. There's a data center in South Africa hosting node machines now. There's one in Panama or something. So they're all over the world. And the network nervous system, which is setting these kind of policies with respect to how much financial re-ineration you receive in real terms, is not only making sure that these node providers can run these machines in a stable way, but also creating these financial incentives to maximize the decentralization of the network, which in turn enables it to create, you know, tamper-proof, unstoppable, host tamper-proof, unstoppable software to reduce cost because it needs geographical and jurisdictional decentralization.

56:53Yeah. How many node machines do you have right now? And is there a sort of a critical mass that you need to make this viable? And how does someone use the internet computer? Well, like if I wanted to use it, what do I do? So I think there are like 1500 of these machines around the world at the moment. Actually, not all of them are used. Most of them are just kept in a pool. And so that if there's a spike in demand, there's some kind of safety buffer that allows the network to scale up quickly. But to use the internet computer simple, you just interact with it over the internet. And that might sound mysterious.

57:43How can that be? How can that work? Because the software is not in one place, it's in lots of places. Well, the network incorporates these subnets, but actually there's a sort of perimeter called boundary nodes.

58:01And these, you know, and default domain names, so each unit of software actually has its own kind of URL, right? And when you interact with the internet computer, dynamic DNS will connect you, first of all, I think, to a boundary node that's nearest to you, so you get the lowest possible latency. And then the... I'm oversimplifying here, but the boundary node then will forward your request and the response that results from your request to the replica in the subnet hosting the software you're interacting with. That's kind of nearest to you in terms of minimum latency, right?

58:49And so, you know, it's the domain name system and the routing of the boundary nodes perform determine which individual replica you're interacting with. But of course, your compute, when you submit a function call that changes memory called an update call, of course, it's replicated across all nodes. But sometimes you just want to perform a query that doesn't need to modify memory and so on. And that's done quickly by this kind of routing based on latency. But of course there are other considerations too, because individual replica inside a subnet node might be down, be faulty in some way. There are load balancing issues.

59:31It doesn't make any sense if you've got something hosted on a subnet and let's say this piece of software is very popular in South Korea, right? and it turns out the subnet's got like one node in South Korea. Yeah, of course, that's going to produce the lowest response time for kind of query computation. But if all that massive load just goes to one replica in the subnet that's in South Korea, then it could get overloaded. So you have to have some clever logic that will at some point begin distributing these requests to other replicas in the subnet. and you have to have things like, you know, DOS protections and rate limiting for individual IP addresses that might make requests.

1:00:18And so, you know, in actual fact, behind the scenes, it gets pretty complicated, but at a high level, that's how it works, yeah. Yeah, and so is there a URL that people access to? So I think that, I don't know if by heart, but, So by the way, when you've got a piece of software on the internet computer, there are standard bits of software you can just load a website into. So if you go to internetcomputer.com, which is the website for the internet computer that we maintain, that website is actually hosted on the internet computer. And so you can map your own custom URL, your own custom domain name to your software on the internet computer.

1:01:04But with respect to uploading that software, you know, there's a developer kit called DFX. And, you know, when you create software that's going to be installed on the Internet computer, there's some magic going on behind the scenes. It's interacting with various URLs. And then, you know, through that process, your software will get an ID. And this will kind of determine, like, future URLs you interact with and things like that. But that's all hidden. The user experience is just this thing called the Internet Computer. It's part of the Internet. You don't have to worry about how that works. If you've got an Internet connection and you've got the software developer kit, you can deploy code on it.

1:01:51If you want to go to the Internet Computer website, you just type in internetcomputer.org, and it's served off the Internet Computer. That first open Internet service I mentioned, OpenChat, It's very cool. And you just type in oc.app, I think. And that's mapping behind the scenes to some underlying network resident software URL. But you as a user don't even know. I mean, what has actually been one of the problems we've experienced is that people don't know when something's on the internet computer. And in this world of Web3, there was this kind of slight subversion of the meaning of on-chain. So people will say, oh, look, the social media service or this whatever is on Solana, it's on Ethereum, right?

1:02:47It's on-chain. And Coinbase has this tagline, on-chain is new online. And people, when they hear that, they think those things are running on the blockchain. But it doesn't mean that at all. It's like a subversion of the original language I used as far as back as 2015, 2016. What it means for them is that it's built on Amazon Web Services or Google Cloud or something. And it's on-chain because it has an associated token. Like, it's a bit like, you know, I have tokens and so I'm on-chain kind of thing. The problem is, you know, we did surveys and it's like more than 95 % of people when they hear this language.

1:03:25And I'm talking about crypto journalists, mainstream journalists, crypto investors, mainstream investors, developers, DGNs. When people hear this language like, oh, this is built on blockchain XYZ, they think that blockchain XYZ is really like the Internet computer. And in actual fact, it's nothing like that at all. It's just it's a token database and it's holding an associated token for this completely centralized thing running on cloud service. But the thing is like, you know, and then people can interact with OpenChat, OC.app, and it's this highly interactive kind of, you know, social network chat service that is completely autonomous, runs under the control of a decentralized governance system.

1:04:09Like the community actually runs its own community, runs the service itself. There's no back doors, like there's no back door at all. And it's coming off the internet computer and you can make it, use it as a progressive web app. And the problem is that people see that and it's like, well, that's Web 2 functionality, right? And they don't understand the difference. That thing is running on the internet computer on a decentralized network.

1:04:39And this other thing that's also described as being built on a blockchain, they have a different meaning for on-chain. What they mean is it's built, it's completely centralized and run by developers on a cloud infrastructure, but it has an associated token that's on the blockchain that really functions as a decentralized token database. And these are very, very different things, but the use of that language, this on-chain language has confused the hell out of people. Nobody understands. And when you try to explain, hey, this blockchain, you can't even store a phone photo on it. It's really just designed for DeFi and tokens, maybe like access control, like this, a cash thing.

1:05:22Like people look at you like you're from Mars. They just can't grok it because the language originally, like on-chain, it's like saying on cloud, right? If someone says it's on cloud, well, you know it's built on cloud. So on-chain should mean it's built on-chain, but that's not how they mean it. They mean it like centralized, built on Amazon Web Services or Google Cloud or something like that. And there's an associated token. And then you try to explain that, and it's really tough. And, you know, when we say on chain or on the network, you know, it's the real, it's the literal, but we don't know what to do because I mean, I was, you know, really early pioneer of this kind of stuff.

1:06:03And, you know, I probably have people trying to fully on chain and stuff like that. And now this language that we had in like early days has completely changed. But the problem is it's not clear anymore. Like how do you, you know, the context of the internet computer, what language do you use now to explain the difference? We're kind of like completely just stuck. And, you know, we found that even like, you know, I'd spoken to like managing editors of very major mainstream publications, managing editors of crypto. I had one shocking interview where someone connected us. And after about 20 minutes, I've been explaining this vision of extending the internet.

1:06:47So not only does it connect software, it hosts software, and this new kind of software is tamper-proof and unstoppable and all these amazing things, and you can create open internet service. And I could see the guy was looking bad tempered. So I paused. I do talk too much. It's true. I paused and looked at him. And he had a real scowl on his face, and he shrugged his shoulder. And he said, so what's new? And I said, what do you mean, what's new? He said, well, Ethereum and Solana, they're decentralized clouds too. So what's new? And it was like, I realized like the people like this language has confused people.

1:07:23And I let's be honest, it probably was designed to confuse people. Right. And it was an overloading of the language that didn't need to be made. Like on-chain had a very clear meaning. Like why did on-chain have to change to mean some kind of centralized thing under the control of a bunch developers that has an associated token. It doesn't make any sense. But the language is so pervasive and it's supported by all the venture capital backers of these projects that have an associated token, all the crypto press, all the crypto industry research, which of course tends to be

1:08:00sometimes supporting vested interests and so on.

1:08:05People can't believe it. And it's fooled everybody. This is the incredible thing. Even people who are managing editors of crypto, huge international publications have been completely misled and confused by this terminology of on-chain, this overloading and change to mean having an associated token. So it's very tough for us because what language can we use to explain this very fundamental and important difference? I mean, these are completely different things, right? And similarly, the other one we had, a lot of it is this kind of idea of decentralized cloud. For us, what we mean when we say decentralized cloud is like the cloud itself is decentralized.

1:08:54And it doesn't have, when you're putting software into this serverless decentralized cloud, or an AI model or whatever it is, it doesn't have a location. It's in cypher space. and you're guaranteed that the logic will run as written against the correct data. It's tamper-proof, immune to cyber tech. Nobody has backdoor access to it. It's unstoppable. You can make it autonomous and a bunch of other stuff, right? But other people, when they talk about a centralized cloud, what they really mean is that there's a blockchain with some kind of tokenization and access control that gains you access to the cloud computing that's completely centralized, right?

1:09:33It's running on someone's gaming PC or it's an Amazon Web Services instance that someone is connected to the blockchain. But when someone says decentralized cloud, what you imagine is that the compute is decentralized, not that there's a blockchain gating access to centralized compute. Because centralized compute can be switched off. It can be corrupted by whoever's running it and got the keys to it. It's certainly not tamper-proof. It's certainly not unstoppable. It can't be autonomous because autonomy implies no human or organizational control, like just controlled by logic. And so, you know, we do struggle, like we really do struggle.

1:10:08And I think the other piece is just like, you know, people, well, how is it even possible? And, you know, I mean, it's a technical area. I mean, we discussed deterministic decentralization and how deterministic decentralization enables you to run with less replication, run this host, the software with less replication while still delivering on security and resilience guarantees. But, you know, there's a lot more to it than that. And of course, when you're talking about something like the internet computer, it's non-trivial. We have hundreds of people we work. I think at this point, very significantly, more than 1 ,000 person years of R &D has been dedicated to the effort and we've been going for years.

1:10:49And that's just, again, very different. Like, you know, you get different results if you're willing to invest that much in R &D than if you're just copy-pasting an existing blockchain and making some tweaks and rebranding it. But it's, again, very, very difficult because of the noise in Web3 to actually communicate to people the profound nature of the differences. Yeah. And you mentioned, for people that want to explore this, you mentioned two URLs. You said internetcomputer.com and internetcomputer.org. Are those aliases for the same? No, just internetcomputer.org is a website and you can get a lot of resources like developer resources and things like that.

1:11:33And then there's a new one. I think it's just a deck at the moment. So people are interested in the self-writing internet. You can find that icp.ai, but I think it's just deck.icp.ai at the moment. But actually, there's a great URL to get started. It's internetcomputer.org slash library. And if you go to internetcomputer.org slash library, you can find all kinds of things. You can find in a nutshell primers, like short introductory documents. You can find decks covering like the base network, but also things like self-writing internet. I think there's about 20, if people want it, there's about 20, you know, academic papers out there that talk about some of the underlying, you know, not only the overall architecture employed, but also some of the underlying mathematics, which is actually very beautiful and interesting, but sometimes quite complicated.

1:12:30Yeah. Okay. So internetcomputer.org slash library. That's where people should go. Great place to start. Yeah. I'm past the point of looking for jobs, but I'm not past the point of looking for people to hire. And when I need to do that, I turn to Indeed. Imagine you just realized your business needed to hire someone yesterday. How can you find amazing candidates fast? Easy. Just use Indeed. When it comes to hiring, Indeed is all you need. You can stop struggling to get your job posts seen on other job sites because Indeed's sponsored jobs help you stand out and hire fast. With sponsored jobs, your post jumps to the top of the page for your relevant candidates so you can reach the people you want faster.

1:13:29And it makes a huge difference. According to Indeed data, sponsored jobs posted directly on Indeed have 45 % more applications than non-sponsored jobs. Plus, with Indeed sponsored jobs, there's no monthly subscriptions, no long-term contracts, and you pay only for results. How fast is Indeed? In the minute I've been talking to you, 23 hires were made on Indeed, according to Indeed data worldwide. There's no need to wait any longer. Speed up your hiring right now with Indeed, and listeners of this show will get a$75 sponsored job credit to get your jobs more visibility. Go to Indeed.com slash Eye on AI.

1:14:20Eye on AI, as always, all run together, E-Y-E-O-N-A-I. That's indeed.com slash eye on AI right now. And support our show by saying you heard about Indeed on this podcast. Indeed.com slash eye on AI for a$75 sponsored job credit. Terms and conditions apply. Hiring indeed is all you need.