UDSKRIFT 🔗
WEBVTT
00:00:30.160 --> 00:00:32.000
Welcome to Entangled Things.
00:00:32.399 --> 00:00:34.000
Quantum Computing Podcast.
00:00:34.320 --> 00:00:36.880
Hosted by Patrick and Cyprian.
00:00:40.240 --> 00:00:42.159
Hey Cyprian, how are you doing?
00:00:42.640 --> 00:00:43.439
Hey, Patrick.
00:00:43.520 --> 00:00:44.079
I'm doing good.
00:00:44.240 --> 00:00:47.119
Looking forward for another great episode of Entangled Things.
00:00:47.439 --> 00:00:50.719
I mean, I look forward to all of our episodes, but I've been looking forward to this one for a while.
00:00:50.799 --> 00:00:52.719
So we're joined by Colton and Rick.
00:00:52.799 --> 00:00:55.840
Do you uh two mind introducing yourself to our audience?
00:00:56.240 --> 00:00:56.799
Not at all.
00:00:56.880 --> 00:00:58.719
Um my name is Colton Dillion.
00:00:58.799 --> 00:01:06.799
I'm the CEO at PostQuant Labs, and we are the development company behind Quip Network, which we hope will become the worldwide quantum computer.
00:01:06.959 --> 00:01:08.799
Um and I'll let Rick give his intro.
00:01:09.120 --> 00:01:17.359
And I'm Rick Carback or Richard Carback, and uh I'm a cryptographer, I'm the CTO, and now I do spend most of my days doing quantum algorithms.
00:01:17.840 --> 00:01:18.480
That's awesome.
00:01:18.560 --> 00:01:20.159
That's exactly what we want to talk about.
00:01:20.319 --> 00:01:28.560
So so I've I got to meet you guys at the conference in Boston, and I said that you know, we definitely have to have these people on our show.
00:01:28.799 --> 00:01:31.439
You guys, excuse me.
00:01:32.560 --> 00:01:40.319
You guys are kind of the intersection between the things that crypto brought us and what quent quantum is bringing us.
00:01:40.560 --> 00:01:41.359
Am I right in that?
00:01:41.920 --> 00:01:42.560
Absolutely.
00:01:42.799 --> 00:01:55.519
So uh, you know, when you work in distributed systems, it's really, really important to have really high quality cryptography, but also uh these incentives that get people to work together.
00:01:55.680 --> 00:02:13.919
We've been very lucky with uh sort of the existing internet, the HTTP internet that you use every day, that we've been able to create these distributed systems without a whole lot of additional incentives uh beyond just the incentives of being a data center or a data provider.
00:02:14.080 --> 00:02:28.719
Um but what we've realized over the years is that this has a centralizing tendency with data, where uh if you've ever used a Google product and Google killed the product, uh now you can't use that product and nobody has it anymore.
00:02:28.800 --> 00:02:32.080
The data is gone, you can't port it to a new service.
00:02:32.240 --> 00:02:42.240
If you ever played a video game that you loved and the server went down, and there are entire communities that are dedicated to reverse engineering this software so that they can keep playing.
00:02:42.400 --> 00:02:57.759
Um, and so over time we've realized that there's a certain
Load full transcript
important aspect to the internet, which is decentralization and openness, where uh you know anyone can observe the code, anyone can see how the data is structured, and they can build new products around that data.
00:02:58.000 --> 00:03:12.080
And so uh this has manifested as crypto, which a lot of people may have bad associations with because there are a lot of uh hijinks that that are associated with frontier technologies.
00:03:12.240 --> 00:03:22.879
Um but under the hood, that's really what it's all about is decentralization, is open source software, is trying to make these things that are maintainable and that uh everyone has a vote in.
00:03:23.120 --> 00:03:30.639
And so uh when we came into quantum, uh we saw that that's not really the ethos in quantum right now.
00:03:30.800 --> 00:03:39.840
There are a few open source projects like OpenCasm or QIR or uh, you know, the Munich Quantum Valley benchmarking initiative.
00:03:40.000 --> 00:03:44.400
All of these things are really great projects, but overall the stack is really quite closed source.
00:03:44.479 --> 00:03:50.000
It's very hard to get access to the proprietary technologies that these computers are built on.
00:03:50.080 --> 00:03:56.879
Um, and we think that's an impediment, that it prevents people from adopting the technology because it's really hard to customize it.
00:03:56.960 --> 00:04:03.520
It's really hard to insert your software into the stack and uh get a different result out of it.
00:04:03.759 --> 00:04:08.639
And so that really inspired us to think about how we can change that situation, right?
00:04:08.800 --> 00:04:12.479
There there are, we say there are four major problems with quantum computing.
00:04:12.719 --> 00:04:15.120
One is that the benchmarks are not super clear.
00:04:15.280 --> 00:04:20.319
Every quantum computing provider has a different benchmark that they're trying to accelerate.
00:04:20.480 --> 00:04:24.480
Um so you know, if you're IBM, you want operations per second.
00:04:24.560 --> 00:04:26.959
That's the thing that your machine looks really good at.
00:04:27.199 --> 00:04:35.120
If you are I on Q, you want qubit count and qubit connect connectivity and maybe qubit fidelity, so you can do deeper, deeper circuits.
00:04:35.279 --> 00:04:49.680
Um, and if you're D-Wave, you want to say, well, we only care about uh what is the problem that we're solving and is there commercial application, because they tend to have uh a lot more commercial applications that are deployed than some of these other providers.
00:04:50.000 --> 00:04:53.839
And uh so you know, we wanted to solve that problem.
00:04:54.000 --> 00:05:02.079
And there's this nice aspect of decentralized software where you can create these shared data sets and these uh shared solutions.
00:05:02.399 --> 00:05:14.480
Um sort of the second component is that these machines, you know, they have to be kept near absolute zero very frequently, either uh the entire machine or the area inside the machine, and so they're expensive to run.
00:05:14.639 --> 00:05:18.319
But the additional cost of serving a customer is very, very small.
00:05:18.480 --> 00:05:24.639
You're adding watts of energy uh, you know, to the whole system in order to do a computation.
00:05:24.879 --> 00:05:39.279
Um and so because of all of this uh challenge around understanding quantum, the largest cost of serving the compute isn't actually serving the compute, it's trying to educate your customer about how quantum works.
00:05:39.439 --> 00:05:42.079
Um exactly.
00:05:42.319 --> 00:05:55.199
And and so as a result, they have to contribute a lot of time to get you up to speed as a quantum operator, as somebody who understands quantum information science, who understands the specific machine that they're working on.
00:05:55.360 --> 00:06:00.079
And so they can't just open up their API because the odds that you'll get a good result are really low.
00:06:00.240 --> 00:06:16.240
So they only want to work with these big customers who can afford the consulting that comes along with these machines, uh, or otherwise, you know, give these small uh test times to people so that they can try and figure out uh how to use an individual platform.
00:06:16.480 --> 00:06:33.519
And so this is another component that we hope that we can sort of automate away by creating this open source network where anyone who is an expert in this stuff can build software for you and then give you an interface that uh, you know, you don't have to be a quantum PhD to understand.
00:06:33.680 --> 00:06:36.959
You can just hit an API like any other software.
00:06:37.120 --> 00:06:45.120
Um and then there's a bunch of stuff about talent pool, where you know, these people are, you know, working for proprietary companies or they're working for government.
00:06:45.199 --> 00:06:47.519
So all their work is confidential or top secret.
00:06:47.680 --> 00:06:50.480
And so there's not a lot of sharing of resources.
00:06:50.720 --> 00:06:58.959
Um, if you look out there, there's a lot of reduplication of effort, building all the same quantum algorithms for all the same applications.
00:06:59.120 --> 00:07:02.000
And the reason why is because everyone keeps it under lock and key.
00:07:02.160 --> 00:07:14.879
And so for all of these reasons and more, we think it's super important to get a bigger open source ecosystem in quantum and to uh hopefully make it easier for the average developer to get up to speed in using these systems.
00:07:15.279 --> 00:07:28.240
So if I understand correctly, you're also building, or you or the main thing you're building is an alternative to what I thought was going to happen, which is, oh, you're a company that can't afford a quantum computer yourself, which is most of us.
00:07:28.399 --> 00:07:30.639
And so you you have to use a cloud vendor.
00:07:30.800 --> 00:07:38.560
So either D-Wave or Microsoft or somebody puts their system online so you can consume it as a cloud
service.
00:07:38.800 --> 00:07:47.680
But what if I'm a hospital or a hospital group or a university group and I own a quantum computer and I'm not keeping it utilized?
00:07:47.920 --> 00:07:49.120
How do I resell?
00:07:49.279 --> 00:07:55.120
I think I can't call Microsoft and say, hey, do you can you resell some of my but this is a solution you guys have.
00:07:55.600 --> 00:07:56.160
Exactly.
00:07:56.399 --> 00:08:01.920
And and so that's part of the open source software is anyone can download the software and anyone can run it.
00:08:02.079 --> 00:08:07.519
So we are actually talking to uh, you know, uh the electric power board of Tennessee.
00:08:07.600 --> 00:08:10.879
They've acquired a uh IMQ computer.
00:08:11.040 --> 00:08:30.480
Um, and you know, they're interested in trying to make the time on that machine available to people uh because uh they have some experiments that they are committed to uh in terms of their work with uh Oak Ridge National Labs and some other consumers inside of that Chattanooga data center.
00:08:30.560 --> 00:08:34.240
Um but they largely don't know what it's gonna be used for day to day.
00:08:34.399 --> 00:08:36.720
And again, you have to keep these machines cool.
00:08:36.799 --> 00:08:38.559
So it's an expense.
00:08:38.720 --> 00:08:44.799
If you let it heat up, you're spending a day, maybe two days uh trying to cool it back down and then recalibrating the machine.
00:08:44.960 --> 00:08:46.879
In some cases, it's up to two months.
00:08:46.960 --> 00:08:52.159
Like if you go to AWS right now, a lot of the computers you can't actually use because they're being calibrated.
00:08:52.320 --> 00:09:01.039
Um and so what we do is we kind of fit into the cracks where if you have an SLA, if you have customers, great, serve those customers first.
00:09:01.120 --> 00:09:04.240
Um but we offer what's called a preemptible spot job.
00:09:04.399 --> 00:09:11.519
And so instead of reserving time in advance, you can bid for time on the machine against all the other people who don't have a contract.
00:09:11.600 --> 00:09:14.720
And whoever has the highest bid, they get served first.
00:09:14.879 --> 00:09:19.679
And if one of their customers comes along who has already paid for the time in advance, you get kicked off.
00:09:19.759 --> 00:09:21.759
Uh so you they can interrupt your job.
00:09:21.840 --> 00:09:22.080
Yeah.
00:09:22.320 --> 00:09:30.960
But we expect that over time we can make up in volume with all of the machines that aren't being used to make sure that your job gets served quickly.
00:09:31.120 --> 00:09:43.919
And over time, as people bid up the price of the machine, because you know, we expect that quantum computers are going to be able to break computational bottlenecks and do things that no other computer in the world can do in the same amount of time.
00:09:44.159 --> 00:09:46.000
And so that's gonna be really valuable.
00:09:46.240 --> 00:09:56.159
And uh, so what's the value to you of making sure that you get served first on that machine for a you know one-time opportunity that only comes along every six months?
00:09:56.559 --> 00:10:02.159
Do you want to take the risk on renting all of that time in advance, even though you're not gonna use 90% of it?
00:10:02.399 --> 00:10:06.399
Or do you want to bid for that time when that opportunity comes up?
00:10:06.559 --> 00:10:11.360
And you know, the value of that time will take up some percentage of the most valuable application.
00:10:11.519 --> 00:10:25.519
And to your point, if you already have compute or if you've rented compute and you're not using all of it, well, maybe you can resell it on the network by running our node software, putting in your API key, and then serving jobs with the compute that you're not using.
00:10:26.080 --> 00:10:32.399
What is the what is the unit of measurement uh against which the bidding is is is done?
00:10:32.559 --> 00:10:34.159
I'm curious to understand.
00:10:34.240 --> 00:10:38.879
Because you have to have a common denominator across multiple providers of capacity, right?
00:10:39.200 --> 00:10:41.039
Yeah, so think of it like oil, right?
00:10:41.200 --> 00:10:59.279
Oil has many different grades, uh, many different uh levels of processing, but ultimately, you know, we we create certain categories of it, like Brent Crude, and we put it on a market, and people bid against that category as sort of a uh standard for all oil.
00:10:59.440 --> 00:11:02.320
Um and so this is very much similar, right?
00:11:02.399 --> 00:11:11.360
We're commoditizing quantum compute as a commodity, and you can essentially bid based on the jobs that are meant to be done.
00:11:11.519 --> 00:11:20.399
So the network uh as is normal for what's called a proof-of-work network, you have to prove that you've done work at any given time.
00:11:20.480 --> 00:11:25.679
There's always a random problem waiting for you where you can prove that your computer is available.
00:11:25.759 --> 00:11:35.919
Um, because we don't want to reward people who are just like sending a message to the network saying, Oh yeah, we're available, and really their quantum computer isn't doing anything.
00:11:36.080 --> 00:11:42.960
So we require that you solve a very difficult problem that uh generally a quantum computer will tend to outperform on.
00:11:43.120 --> 00:11:47.519
And this is proof that your computer was available, that somebody could have requested a job for it.
00:11:47.679 --> 00:11:53.440
And so the network gives these computers uh compute credits just for being available.
00:11:53.600 --> 00:12:11.759
And then you, as a consumer, you can look at the library of open source solvers and you can say, hey, uh, you know, I've got a logistics company, I want to solve a combinatorial optimization problem around packing my boxes into a bunch of trucks and choosing how I'm going to route those boxes in order to maximize my profit.
00:12:12.000 --> 00:12:15.120
And uh that would be like an
application in the library.
00:12:15.279 --> 00:12:22.720
And if you request that, then there's a baseline cost, which is the uh you know, total chip space that we're taking up, right?
00:12:22.799 --> 00:12:27.679
And the total circuit depth uh that needs to be applied on that chip space.
00:12:27.840 --> 00:12:33.440
Um and then there's an additional cost, which is sort of the floating tip that you give to the operator.
00:12:33.600 --> 00:12:37.679
And so if you want to be served first, you increase the size of your tip.
00:12:37.840 --> 00:12:43.200
If you don't care if you're happy to wait for your answer, then you can give a very low tip.
00:12:43.279 --> 00:12:50.000
And when the network's not serving anyone, that operator's incentivized to serve your job anyway because they'll get the extra income from your bid.
00:12:50.320 --> 00:12:54.559
Is that priced in a coin, a quip coin, or is that in dollars?
00:12:54.960 --> 00:12:57.039
Yeah, so so both, right?
00:12:57.200 --> 00:13:10.639
Ultimately, that's the beautiful thing about cryptocurrency markets is that they have very, very liquid markets where there are people who are trying to arbitrage away the extra value of your token against every other asset on Earth.
00:13:10.879 --> 00:13:25.039
And that's only going to get better over time because now we're starting to bring traditional assets uh into the cryptocurrency ecosystems like Tesla Slap stock or SpaceX stock or uh whoever uh you might be interested in holding on-chain.
00:13:25.440 --> 00:13:31.600
And so there are people who are trying to arbitrage away these uh discrepancies in value.
00:13:31.840 --> 00:13:35.759
And uh so the quip token has to be a native currency.
00:13:35.840 --> 00:13:55.519
Uh, and the reason that is, is because if somebody tries to cheat the system and they live in China or they live in Vietnam or they live in India or they live in Argentina, as a US domicile, I'm gonna find it very difficult to sue them or to take them to court over the damage that they've done to the protocol.
00:13:55.679 --> 00:13:59.519
And so what we do is we create this compute credit that stands in for money.
00:13:59.759 --> 00:14:07.519
And uh, if you do something bad, then the protocol reserves the right to take away that token, take away those compute credits.
00:14:07.679 --> 00:14:16.320
And that's just an easy way to do dispute resolution across borders in a world where anyone can join the network and they may be a bad actor.
00:14:16.559 --> 00:14:30.639
Um, and so you know, it is everything's denominated in the compute credit, but that compute credit always has a very uh liquid floating price to US dollars or two euros or to whatever currency you're interested in trading from.
00:14:31.039 --> 00:14:36.879
I think our our expectation is your your interface is to, you know, it's a choose your own adventure interface.
00:14:37.120 --> 00:14:45.440
So if you only want to think about US dollars and you don't care about any
of this, it looks like US dollars, and I put my credit card in and everything is done for me.
00:14:46.240 --> 00:14:46.879
Cool.
00:14:47.279 --> 00:15:06.320
Yeah, I you you don't think about this when you buy oil at the gas pump, but there is a very complex ecosystem of futures and derivatives that are making sure that the gas station right there is only paying a certain amount for gas every year, and they're just charging you a floating price around whatever gas they can get on top of that.
00:15:06.480 --> 00:15:15.919
Um, and so you know, that's the wonderful thing about these very uh mature financial markets is it allows you to plan in advance what your needs are.
00:15:16.080 --> 00:15:25.360
So if you're a shipping company and you need to use a lot of oil, the fact that there's a conflict in the Strait of Hormuz doesn't blow up your business because you already bought all your oil in advance.
00:15:26.559 --> 00:15:33.039
Yeah, and there was a very uh active financial market to help you make the decisions about how much that costs.
00:15:33.200 --> 00:15:34.799
And so we're doing the exact same thing.
00:15:34.879 --> 00:15:43.759
It's just instead of the commodity being oil, which helps your ship get around the world, it's compute, which helps your business to make decisions that it needs to make every single day.
00:15:44.159 --> 00:16:00.000
So is is this I I know you guys are working on at least I've seen a lot of buzz about you helping secure Bitcoin wallets against ECC vulnerabilities that are expected closer on the horizon than RSA vulnerabilities per se.
00:16:00.480 --> 00:16:04.399
Is that that where a lot of the activity has started to manifest initially?
00:16:05.200 --> 00:16:16.720
So that was actually our original thesis was was we saw, you know, Rick can talk more about this, but he's been a cryptographer for two decades and uh specifically focused on the quantum resistance problem.
00:16:16.879 --> 00:16:27.120
And uh when we first got 11 years ago, I started focusing and did some early post-quantum cryptography research and work, and I said, okay, this is somewhat of a solvable problem.
00:16:27.200 --> 00:16:36.799
You're just gonna use a lot more resources to solve it, and then kind of you know put it down and moved on to other things that I thought were more pressing in terms of like privacy protecting technology, things like that.
00:16:36.960 --> 00:16:39.360
That's that's generally where where I like to play.
00:16:39.679 --> 00:16:40.000
Cool.
00:16:40.320 --> 00:16:44.240
Um and and uh things changed in the last three years, so that's all I'm gonna say.
00:16:45.519 --> 00:17:05.759
Completely shifted my entire uh uh career around because it became very evident that this is gonna happen uh probably within you know by 2030, but more likely, uh I think now we're thinking it might be earlier, and we're about to start entering a gray zone of the computers are plenty big enough, you know, they have enough qubits.
00:17:05.839 --> 00:17:10.559
It's just you know, the coherence isn't there or the air correction isn't there to break the crypto.
00:17:10.720 --> 00:17:13.359
So we just don't know, like, has someone figured any of these out?
00:17:13.519 --> 00:17:14.880
And that could happen privately.
00:17:15.039 --> 00:17:19.839
So um I suspect our our current estimate of that is is in March of 2028.
00:17:19.920 --> 00:17:21.279
We're gonna enter that gray zone.
00:17:21.440 --> 00:17:21.680
Yeah.
00:17:21.839 --> 00:17:29.519
Um, but it really depends on um or atomic and um I think INQ has the other computer that's coming out with the 10,000 qubits.
00:17:29.839 --> 00:17:30.960
Could be wrong on that one.
00:17:31.119 --> 00:17:31.200
Yeah.
00:17:31.440 --> 00:17:44.880
Um and yeah, so so that was originally what got us into this space was uh, you know, we've known in Bitcoin that uh cryptographically relevant quantum computers were going to be a problem for you know 10 years, 15 years.
00:17:45.039 --> 00:17:50.880
Uh I think Satoshi posted about it in 2011 saying, yeah, we're gonna have to upgrade the algorithms.
00:17:51.039 --> 00:17:58.880
Um and so when we saw the Google Willow announcement uh at the end of 2024, we said, hey, you know, maybe there's a scaling law.
00:17:58.960 --> 00:18:10.079
You know, they connected a bunch of chips together, and for every additional chip they connected, they were able to use exponentially fewer qubits on error correction and exponentially more to actually do computation.
00:18:10.240 --> 00:18:11.920
Um and we started looking into it.
00:18:12.000 --> 00:18:29.920
We put together a very dumb model at quantumdoomclock.com where we take all of the publicly available performance characteristics of these chips and we just plot out uh, you know, if all of these performance characteristics are growing exponentially, when should we expect to see a cryptographically relevant quantum computer?
00:18:30.079 --> 00:18:32.880
And it's a 10% chance by the middle of 2028.
00:18:33.039 --> 00:18:37.599
And uh, you know, European governments, the US government have all advanced their timelines.
00:18:37.680 --> 00:18:44.000
You know, in Europe now you have to have a plan for quantum resistance if you are a government agency uh by the end of the year.
00:18:44.160 --> 00:18:52.720
If if you are a US government contractor and you want a new software contract, by 2027, your software has to be quantum resistant.
00:18:52.880 --> 00:19:02.400
Um, but when we first started going out, we we created a very simple solution that doesn't require these networks, which you know are distributed.
00:19:02.559 --> 00:19:05.200
You have to get everyone to agree to upgrade together.
00:19:05.440 --> 00:19:10.559
Um, there wasn't a lot of consensus about whether this was even a problem a year and a half ago.
00:19:10.880 --> 00:19:16.160
And uh as we started having these conversations, we said to ourselves, well, how can we make this more
urgent?
00:19:16.319 --> 00:19:19.839
How can we show people that these computers are getting uh more powerful?
00:19:20.000 --> 00:19:41.279
And so we came up with this idea of doing a proof-of-work blockchain where the proof of work was the hidden subgroup problem, where you can uh basically convert any hidden subgroup problem, whether that's like a graph isomorphism problem or uh some other pattern finding problem factorization into an elliptic curve key discrete logarithm problem.
00:19:41.519 --> 00:19:45.920
And so you can show you, hey, we've published this public key that matches a problem.
00:19:46.079 --> 00:19:50.640
Can you find the private key that matches that public key and show that you've broken the key?
00:19:50.880 --> 00:20:02.799
And uh again, this can be applied to really useful forms of work, like saying, hey, does this data cluster over here look exactly like this data cluster over here, which turns out to be exponentially difficult.
00:20:03.039 --> 00:20:08.640
Um and uh in the process of doing that, we said, hey, this provides a few great features.
00:20:08.799 --> 00:20:10.079
One, it's a canary.
00:20:10.400 --> 00:20:16.000
It tells people how capable are quantum computers and when should you start to be worried that they might be able to break your key.
00:20:16.160 --> 00:20:18.960
But two, it brings together this cluster of quantum computers.
00:20:19.039 --> 00:20:23.440
And so what do you do with all of these quantum computers once they're all working on the same problems?
00:20:23.599 --> 00:20:29.839
And that really unlocked our imagination in terms of like, well, uh quantum networking is starting to come along.
00:20:29.920 --> 00:20:34.559
We've we've shared a GHZ state over kilometers between four different data centers.
00:20:34.640 --> 00:20:39.680
Uh so one data center emitted uh three states to three other data centers.
00:20:39.920 --> 00:20:49.440
And uh, you know, we were able to show that this was a reasonably uh probable thing that you could reliably get the outcome from.
00:20:49.599 --> 00:20:52.000
And so, how far away is quantum networking?
00:20:52.240 --> 00:21:04.240
Well, we believe that horizontal scaling is probably going to be the most important aspect of quantum computing once we figure out all of the problems between now and that ideal future where we have a quantum internet.
00:21:04.720 --> 00:21:17.680
Because, you know, famously, the most important aspect of quantum is that if you can find one more qubit, it doesn't matter how big the system is, if you can connect that qubit to the rest of your system, you've doubled your representational space.
00:21:17.839 --> 00:21:21.200
And so the power of your quantum computer is doubled.
00:21:21.519 --> 00:21:38.559
And so that's ultimately what we want to do is we want to be that protocol that helps people connect together, that punishes bad actors, that gets all these quantum computers cooperating to solve the hardest problems in the in the world, because there's no other system that is as large as this distributed network.
00:21:38.720 --> 00:21:44.079
And so it really will solve impossible problems that you can't do on any other machine.
00:21:45.119 --> 00:22:03.440
So, do you expect the the quick coin to be something we uh uh surprisingly, we have a lot of people who listen to the show for investment because they see the the wave of quantum being somewhat masked by the the hype of the AI wave, but when it arrives, Arrives, it's going to arrive and probably by the end of this decade, as you've said.
00:22:04.240 --> 00:22:10.960
Is the quick coin something people can buy, hold, and speculate with, or is that not something on the table?
00:22:11.359 --> 00:22:13.440
Yeah, so we don't encourage speculation.
00:22:13.519 --> 00:22:14.720
Uh, you know, all too.
00:22:15.279 --> 00:22:20.400
It it happens anyways, and people speculate on gold and oil and wheat and all of these things.
00:22:20.559 --> 00:22:25.200
Um, but it we do expect that quantum compute will only become more valuable.
00:22:25.359 --> 00:22:41.039
Um, you know, we've talked to some cloud providers where they feel that uh NISC systems, the noisy intermediate scale quantum systems that are available today, don't have a lot of demand uh, or the demand is very spotty just because they are noisy, it's hard to get a great result from them.
00:22:41.200 --> 00:22:48.799
But once we have fault tolerance systems, they expect that the line will never end, that there will always be people waiting in line to use the computer.
00:22:49.039 --> 00:23:04.720
And so uh if you expect that quantum compute is going to become more scarce over time and more difficult to acquire, and you're going to need that quantum compute, then absolutely you should purchase the token and make sure that you have some of the token on hand so you can access the compute when you need it.
00:23:04.799 --> 00:23:09.039
Um and we do expect that this will be available before the end of the year.
00:23:09.200 --> 00:23:10.559
Um, no promises.
00:23:10.640 --> 00:23:15.039
Uh we say in the crypto ecosystem that it's always soon, trademarked.
00:23:15.279 --> 00:23:19.039
Uh and so we are actively working right now.
00:23:19.279 --> 00:23:25.680
We have uh our smart contract programming language uh should be going live before the end of the month.
00:23:25.839 --> 00:23:41.759
So you'll be able to uh formulate uh optimization problems under a constraint programming language and we'll automatically convert that into whatever target quantum hardware needs to uh solve that uh optimization problem.
00:23:42.240 --> 00:23:43.920
If you're a programmer, you can access it now.
00:23:44.000 --> 00:23:49.920
We have a few people already filing tickets, and uh the response right now is yes, we know we're we're working on it.
00:23:50.079 --> 00:23:52.240
Um so it's all open source.
00:23:52.319 --> 00:23:55.920
You can go to github.com slash quip network uh and
check it out.
00:23:56.480 --> 00:24:01.599
There there is another ecosystem that has another trademark, which is within the next decade.
00:24:01.839 --> 00:24:04.880
Um that's AI or is that fusion?
00:24:05.200 --> 00:24:05.839
The fusion.
00:24:06.319 --> 00:24:06.880
Yeah.
00:24:07.680 --> 00:24:08.160
Yeah.
00:24:09.200 --> 00:24:15.599
And that that is the trouble with uh frontier technology, is is that it always feels just around the corner.
00:24:15.680 --> 00:24:23.920
And and that's what separates good VCs from bad VCs and lucky entrepreneurs from unlucky entrepreneurs is whether it really is around the corner.
00:24:24.240 --> 00:24:29.039
So so your your decentralized network uh is based on proof of work.
00:24:29.119 --> 00:24:30.240
Uh is that correct?
00:24:30.640 --> 00:24:30.960
Correct.
00:24:31.279 --> 00:24:32.160
So go ahead.
00:24:32.799 --> 00:24:40.319
That if my understanding is correct, then uh the the the quip coin is basically mined by solving those very difficult problems, right?
00:24:40.720 --> 00:24:41.599
Correct.
00:24:42.240 --> 00:24:45.519
So so it's proof of useful work, correct?
00:24:45.759 --> 00:24:46.160
Correct.
00:24:46.319 --> 00:24:53.440
So so the proof of work is not just you know grinding hashes to find a random number that's below a certain threshold.
00:24:53.599 --> 00:24:58.400
Uh our initial proof of work is solving uh icing models.
00:24:58.640 --> 00:25:05.119
And if you're familiar with icing models, they can be applied to quadratic unconstrained binary optimization.
00:25:05.359 --> 00:25:26.640
So if you have a bunch of uh features of a problem that trade off against each other, where if you choose more of this feature, it's really hard to get more of this feature, um, then you can formulate this for uh quantum annealers and gate-based quantum computers so that they can solve this uh with a little bit of edge over classical computers.
00:25:26.799 --> 00:25:41.440
We we find that with the D-Wave Advantage 2s that we have available on the network today, that uh if you face off an advantage two against 80H 100 GPUs, which are essentially watt equivalent, they'll consume the same amount of energy in the same amount of time.
00:25:41.519 --> 00:25:51.440
Uh the D Wave computer will deliver an answer about 30 times faster than the ADH100 GPUs, and it'll be a better answer about 92% of the time.
00:25:51.680 --> 00:26:00.000
Um and and so you know, there is an edge if you are using one of these machines versus using one of these large clusters.
00:26:00.160 --> 00:26:06.559
Now, your initial capex on the D-Wave machine is going to be higher than purchasing ADH100 GPUs right now.
00:26:06.640 --> 00:26:14.960
But even if you scale up the capex so that it's about equivalent, uh the GPUs win about 66% of the time versus the D-Wave Advantage too.
00:26:15.200 --> 00:26:22.160
And uh, even still, you won't be able to get the same level of quality of a solution as you can with the quantum computers.
00:26:22.400 --> 00:26:34.400
And so that's part of what we're trying to show with this network is these proofs of works really create this public benchmark where now you can see exactly how are all of these machines performing on these problems.
00:26:34.480 --> 00:26:46.240
And if they're useful proofs of work where you can substitute in a person's real problem for that proof, uh, then you can also show there's a public record of people having demand for this problem.
00:26:46.480 --> 00:26:52.480
And uh so it really helps to solve this benchmarking issue of what's the right benchmark to search for.
00:26:52.720 --> 00:26:55.279
And so over time we want to add more proofs of work.
00:26:55.440 --> 00:27:09.359
Like right now we're working on a random circuit sampling subnet, where essentially the network uh records that a random circuit was proposed and that you solved it in a short enough period of time to be certain that it's quantum.
00:27:09.599 --> 00:27:23.440
And so, because you have this network recording all of the events, it's very difficult to fool the entire network at once and to say cache a circuit because the circuit is being generated on the spot by the entropy over the whole network.
00:27:23.599 --> 00:27:36.960
And then once you've generated all of the quantum randomness, then the rest of the network will validate it and show that it fits uh the distribution, um the Porter Thomas distribution that is expected for a random a quantum random circuit sample.
00:27:37.200 --> 00:27:44.799
And so this is sort of the first use of gate-based platforms that uh, you know, you can't do this on classical computers.
00:27:44.960 --> 00:27:50.640
And uh we expect that there will be more proofs of work, including this the hidden subgroup uh proof of work.
00:27:50.799 --> 00:28:00.880
And eventually these will all come together in order to form this uh you know united difficulty function of all of the different proofs of work that have gone into the blockchain.
00:28:01.519 --> 00:28:13.039
So if if I want to solve a problem and I want to do it through through your network, then I have to be able to model my problem against your smart contract language, right?
00:28:13.839 --> 00:28:14.400
Uh yes.
00:28:14.559 --> 00:28:19.119
So so ultimately we are limited by what the virtual machine can represent.
00:28:19.359 --> 00:28:28.480
And uh then there's a surface language that goes over that virtual machine that we hope will uh you know make it easier for people who don't know the difference.
00:28:28.960 --> 00:28:30.480
You're touching on one of the strengths, right?
00:28:30.640 --> 00:28:37.680
So when you when you represent it in our in our stack, we have the ability to target multiple different machines at once.
00:28:37.920 --> 00:28:48.880
So you're writing your code once and you're able to uh very trivially check it against every available system on the on the platform and find the one that might perform best for you.
00:28:49.680 -->
00:29:01.279
One of the things that we've recently found is we've been we've you know we've been active on this useful proof of work for six months or so, and we we now have a large corpus of very hard-to-solve problems.
00:29:01.519 --> 00:29:09.359
And the question, and we still haven't finished the analysis, but the question is is the quantum computer better on certain problems than the classical computer?
00:29:09.519 --> 00:29:12.720
And we see differences, but we haven't been able to characterize them yet.
00:29:12.880 --> 00:29:21.920
And we have noticed a particular pattern uh with anticorrelation that the optimization uh annealers, the quantum annealers are very good at.
00:29:22.079 --> 00:29:25.599
So there's like lots of really interesting things falling out of the work we're doing already.
00:29:25.680 --> 00:29:28.640
And we're we're you know, we're literally in the middle of year one here.
00:29:28.720 --> 00:29:30.480
So things are going good.
00:29:30.799 --> 00:29:36.240
And and we've kept it constrained uh because you know, if you try and eat a whale at once, it's not gonna work.
00:29:36.319 --> 00:29:38.160
You gotta do it one bite at a time.
00:29:38.400 --> 00:30:01.119
Um, but a lot of the research that I'm doing is actually on a hybrid intermediate representation using interaction nets and the ZX calculus to uh sort of represent universal computation uh under one convergent uh paradigm, uh, where essentially you can switch between the classical and quantum realms by just giving the graph a wire color.
00:30:01.279 --> 00:30:04.559
Um and so, you know, this is some cool research.
00:30:04.640 --> 00:30:20.720
Uh in theory, we might be able to do like distributed compilation and uh, you know, pass around one intermediate representation as sort of a homoiconic uh representation of the underlying compute so that you don't have to transform in and out of these uh different IRs.
00:30:20.880 --> 00:30:26.319
Um but it it'll take some time to get that to maturity and then to get adoption for it.
00:30:26.559 --> 00:30:35.119
Um and so that's some cool research that should be coming out of this, which will make it so that anything is representable uh in the virtual machine.
00:30:35.279 --> 00:30:37.359
But uh yeah.
00:30:37.759 --> 00:30:40.640
That's actually kind of preempting my question that I had.
00:30:40.799 --> 00:30:49.599
Like given a lot of the problems are essentially going to solve going to be solved by a hybrid approach, right, between classical and and quantum.
00:30:49.680 --> 00:30:51.440
Like take sure, for example, right?
00:30:51.519 --> 00:30:58.880
Maybe the poster child example, where you use quantum for just uh uh a very specific problem, right?
00:30:59.200 --> 00:31:04.480
Um are you planning to also provide capabilities around like mixed capacities?
00:31:04.640 --> 00:31:09.759
Hey, you can solve this in with a quantum computer, you can solve this with classical.
00:31:09.920 --> 00:31:13.519
Is that
something that you folks are looking for, or are you just focused on quantum?
00:31:14.000 --> 00:31:19.599
Uh so absolutely, we believe that hybrid is the paradigm that will continue to outperform.
00:31:19.839 --> 00:31:29.920
Even if you have a fault-tolerant quantum computer, there's still the problem of transforming the data into something that the fault tolerant quantum computer can uh outperform.
00:31:30.400 --> 00:31:51.039
And so there will always be a component of the pipeline, which is looking at these large data sets, chopping them up, reducing each of those uh gadgets or each of those um subgraphs of the larger computation and uh optimizing it, and then virtualizing it and splitting it across circuits or serializing the circuits onto the same platform.
00:31:51.200 --> 00:32:06.160
Um and then once you've done all of that transformation, transformation, transforming the answer back out and making sure that any of the uh graph cuts or other transformations that you did before the circuit come back out of the result at the end.
00:32:06.400 --> 00:32:09.599
And so we absolutely expect that hybrid is here to stay.
00:32:09.680 --> 00:32:19.839
You know, you don't generally use GPUs as a single platform solver, they're combined with CPUs uh or they're combined with with other platforms to enable their power.
00:32:20.000 --> 00:32:23.920
Um and so the question is what are the trade-offs there, right?
00:32:24.079 --> 00:32:31.359
Um there's this really interesting space in quantum circuit land of like, do you want to optimize on T count or do you want to optimize on Tefoli gates?
00:32:31.440 --> 00:32:32.720
Like, how often do you want to measure?
00:32:32.880 --> 00:32:44.319
How often do you want to pull out uh an answer that you can then uh parallel process with uh classical compute while you're waiting for the rest of the quantum computation to come out.
00:32:44.480 --> 00:33:03.599
And so this is again what we hope becomes a utility for the network, is that it becomes really easy to see the difference in performance here, that um we've sort of separated out the computation layers so that uh if you're a quantum algorithm designer, you focus on the quantum algorithm and then you expose that API to all the classical developers.
00:33:03.759 --> 00:33:23.920
And if they want to build smart contracts on top of your quantum algorithm, then they can look at all the different applications and they can be the one who says, Oh, yeah, load up a bunch of boxes and I'll do a bin packing problem and then hand it off to the quantum computer, or load up a satisfiability problem, and uh I will uh change it from finance into something the quantum computer can operate on.
00:33:24.079 --> 00:33:32.720
And because you have this unified API, it makes it really, really easy for people who aren't quantum experts to continue to develop with you and to collaborate.
00:33:32.880 --> 00:33:49.599
Um, and that's really what we hope to bring to this industry
is uh one, that's sort of on-ramp for uh people who aren't familiar with quantum information systems, um, but two, that spirit of collaboration and composability that made web one and web two so successful.
00:33:50.000 --> 00:33:54.640
So folks are essentially commoditizing computing capacity.
00:33:54.960 --> 00:33:55.200
Exactly.
00:33:55.519 --> 00:33:56.000
That's the idea.
00:33:57.359 --> 00:34:01.839
It's commoditizing it, it's making it really easy to access and try it.
00:34:02.000 --> 00:34:08.400
And then it's trying to, when you buy the computer, make it still use, you know, make it make it possible to recoup some of that investment, right?
00:34:08.559 --> 00:34:09.679
Even if you can't use all of it.
00:34:10.079 --> 00:34:15.039
And this was uh, you know, a very rich space for NVIDIA to play in, right?
00:34:15.119 --> 00:34:18.000
Like before CUDA, GPUs were not commoditized.
00:34:18.079 --> 00:34:29.599
It was it was a very specialized uh space to uh that was mostly focused at ray tracing, focused at people who make uh video games and people who do uh visual effects.
00:34:29.760 --> 00:34:43.039
And then in 2007, NVIDIA released a software package called CUDA that made it really easy to work with graphics cards, where you didn't have to know about L1 and L2 cash or you know what the size of your scratch space on the GPU was.
00:34:43.199 --> 00:34:46.800
Um, you could just program uh like any other language.
00:34:46.960 --> 00:34:48.960
And this unlocked all these applications.
00:34:49.039 --> 00:34:53.519
Suddenly GPUs were used in finance, suddenly they were used in scientific computing.
00:34:53.679 --> 00:35:01.119
You know, seven years later was the first time that we split a AI training uh run across two GPUs.
00:35:01.280 --> 00:35:05.679
And so that was 2014, seven years after the production of CUDA.
00:35:05.840 --> 00:35:10.239
And now, 10 years after that, AI is the thing that nobody can stop talking about.
00:35:10.320 --> 00:35:13.519
It's the most important thing in the world to tech investors right now.
00:35:13.760 --> 00:35:31.360
And so we expect that quantum is going to be very similar, that once you make an idiom that is easy for classical programmers to develop on and to understand that it will blow up uh and blow out all of the applications of quantum and make it something that is used day to day in businesses around the world.
00:35:31.760 --> 00:35:32.639
Agreed.
00:35:33.280 --> 00:35:34.960
We've been at this for a little while.
00:35:35.119 --> 00:35:38.800
I think we could go on for another another hour at least.
00:35:38.880 --> 00:35:40.480
So we definitely want to get you guys in.
00:35:40.639 --> 00:35:42.400
But we do have to wrap up soon.
00:35:42.559 --> 00:35:49.360
I hate to be the one that throw cold water on the party, but what uh what what are the last things we need to talk about before we wrap up today?
00:35:49.679 --> 00:35:54.400
Yeah, I I mean the last things from my side is that
we are fully open source, right?
00:35:54.559 --> 00:35:56.159
We want to build a community.
00:35:56.239 --> 00:36:04.880
If you this interests you, if you are the type of person who likes tinkering with quantum algorithms or who likes tinkering with new technology, please come join us.
00:36:04.960 --> 00:36:11.199
Uh, you can go to links.quip.network uh and you can join our Discord, you can join our Telegram.
00:36:11.360 --> 00:36:12.480
Uh we have docs.
00:36:12.800 --> 00:36:16.400
Uh our GitHub is fully open source, so you can review all the technology.
00:36:16.559 --> 00:36:28.719
If you want to run a node on your computer at home, you can validate the outputs of the quantum computers and you can compete against them to benchmark them, and you can earn some quantum compute credits for doing that work.
00:36:28.960 --> 00:36:33.519
We're in testnet right now, so we expect to release the mainnet later this year.
00:36:33.599 --> 00:36:37.679
Um, and that's when the tokens will be on uh tradable markets.
00:36:37.760 --> 00:36:39.280
Uh, but right now it's all testnet.
00:36:39.440 --> 00:36:42.079
And if you're a researcher, uh please contact us.
00:36:42.159 --> 00:36:46.320
We can get you um some dev keys and we can get you up to speed.
00:36:46.480 --> 00:36:57.199
And uh we would love to collaborate on your research and introduce you to the rest of our community and make sure that you have access to these machines that are notoriously difficult to get access to unless you've got hundreds of thousands of dollars in budget.
00:36:58.000 --> 00:36:59.599
I think that was very well said.
00:36:59.679 --> 00:37:01.760
Um, and I think we should probably leave it there.
00:37:01.920 --> 00:37:06.800
We'll definitely be talking to you guys in the future if you're if this wasn't too excruciating of an experience.
00:37:07.039 --> 00:37:09.360
Um, but uh but thanks for joining us.
00:37:09.760 --> 00:37:10.719
An absolute pleasure.
00:37:10.880 --> 00:37:14.079
So uh would be more than happy to come back and thank you for having us on.
00:37:14.320 --> 00:37:15.119
Yeah, thank you very much.
00:37:15.280 --> 00:37:16.320
It's been a great talk.
00:37:16.400 --> 00:37:16.719
Thank you.
00:37:16.960 --> 00:37:17.519
Thanks, everybody.
00:37:17.679 --> 00:37:18.400
We'll see you next time.
00:37:18.480 --> 00:37:18.880
Goodbye.
00:37:19.119 --> 00:37:20.239
Bye, everyone.
00:37:22.000 --> 00:37:26.719
Cybercrime is one of the biggest threats to businesses of all sizes and industries.
00:37:26.880 --> 00:37:33.599
With almost half a million open cyber positions, the problem is compounded by the lack of available talent in the marketplace.
00:37:33.760 --> 00:37:44.400
At Pulsar Security, our elite team of highly credentialed experts collaborate with you to assess your current defenses and develop solutions tailored to your specific needs.
00:37:44.559 --> 00:37:53.119
With services ranging from cybersecurity education to advanced penetration testing and red teaming, you can start reducing your risks today.
00:37:53.280 --> 00:37:58.880
Visit pulsarsecurity.com and let's secure your digital future together.