Story 3 starts — Princeton’s millisecond transmon qubit

1:08:30uh last month being like, "Hey, are you the class of 2014?" I was like, "Yeah, fine, fine, fine, fine, fine." Here. >> As long as I get the claim that I was the one who came up with this quantum breakthrough. So, so talk to help me understand like what >> cuz we talk about quantum quite a bit actually. So, we do. So, this is it has to be actually a big deal. Yes. >> For you to put it in. >> It is. It is. It is a big deal. Yeah. So, quantum computers, right? The promise is to break encryption, simulate materials, you get a better portfolio for your financial stocks because it's going to like figure out the best way to do things. And all of that relies on actually making a quantum computer, right? And making a quantum computer as of now, it's still a hardware problem.

1:09:13>> Okay. >> Okay. Okay. >> It is still a hardware problem. A quantum computer, let me just go through briefly what a quantum computer is. Okay. It uses a cubit instead of a classical bit. So a classical bit is your transistor that is in a state of either I'm going to let current through or I'm going to block current. So that's my zero and one. A cubit can be in a superp position of two states. It can be in a zero and a one. And it can be in a linear combination of something in between. The other thing that's different about a cubit versus a classical bit is a classical bit, one transistor doesn't really talk to another until it's like really told to, right? It's like maybe

1:09:54one one transistor flips its sign based on the state of another transistor. And that's an explicit sort of thing that we're doing within the algorithm of whatever we're implementing. But in a cubit, the power of the cubits is that they can be entangled to one another. They are not independent, right? So one cubit can be in a superp position of zeros and ones. Another cubit right next to it can be in in a superp position of zeros and ones and so on and so forth. And I can get access to an exponentially large number of states in my memory without actually having to explicitly encode each one of them. Right? As a