Sometimes, the frontier is at a crypto conference. We’re returning from our adventures in Tel Aviv with nine exclusive interviews with some of the key players in the StarkNet space.
Wish you could make it to all the crypto conferences, but don't have the time? Don't worry, Bankless brings the frontier to you.
In this episode, we’re speaking with Omer Shlomovits, founder and CEO of Ingonyama, a next-generation semiconductor company, building specialized hardware for Zero-Knowledge Proofs. It’s not often that we talk hardware on Bankless, so when we do... it's time to pay attention.
------ 📣 MetaMask Learn https://bankless.cc/metamaskshow
------ 🚀 JOIN THE NATION: https://newsletter.banklesshq.com/subscribe
------ BANKLESS SPONSOR TOOLS:
🐙KRAKEN | MOST-TRUSTED CRYPTO EXCHANGE https://bankless.cc/kraken
🦄UNISWAP | ON-CHAIN MARKETPLACE https://bankless.cc/uniswap
⚖️ ARBITRUM | SCALING ETHEREUM https://bankless.cc/Arbitrum
🚁 EARNIFI | CLAIM YOUR UNCLAIMED AIRDROPS https://bankless.cc/earnifi
👻 PHANTOM | CROSS-CHAIN WALLET https://bankless.cc/phantom
------ Timestamps:
0:00 Intro 4:00 Ingonyama 7:45 Scaling and Privacy 11:00 Present and Future Computation 13:55 Hardware 19:49 Producing Chips 23:50 Get Involved
----- Resources:
Omer Shlomovits https://www.omershlomovits.com/
Ingonyama https://twitter.com/Ingo_zk
StarkNet https://starkware.co/starknet/
----- Not financial or tax advice. This channel is strictly educational and is not investment advice or a solicitation to buy or sell any assets or to make any financial decisions. This video is not tax advice. Talk to your accountant. Do your own research.
Disclosure. From time-to-time I may add links in this newsletter to products I use. I may receive commission if you make a purchase through one of these links. Additionally, the Bankless writers hold crypto assets. See our investment disclosures here: https://www.bankless.com/disclosures
No summary for this episode yet.
Welcome to Bankless, where we explore the frontier of internet money and internet finance. And sometimes, that frontier is at a conference. Like last weekend, we're over a thousand developers, founders, builders and investors, attended the StarCware sessions in Tel Aviv in order to participate in growing the StarCnet ecosystem. This is Bankless's StarCware session series, which are nine bite-sized episodes interviewing the founders, builders, and ecosystem developers of StarCnet. Every once in a while, in the crypto world, a conference happens, but not everyone is available to attend. Don't worry, Bankless has your back because I go to basically every conference that's out on the frontier.
And I bring an entire podcast studio into with me in order to make sure that the Bankless nation stays on the frontier of what's happening in crypto. In this interview, we are talking to Igno Yama, Omar from Igno Yama. Igno Yama is an interesting product where most things that we talk about on Bankless are on-chain. We're actually talking about hardware in this episode. ZK proofs are computationally intensive, especially for CPUs. So Igno Yama is working on building chips, which are just ASICs, first FGPAs, and then ASICs later, to help speed up the prooferset of ZK proofs. And so while ZK proofs are computationally intensive, we still want the ability for anyone to run those proofs.
So the bulk case for Igno Yama is to put a bunch of ZK proofer chips in all of the hardware and devices that we use in this world. Disclosure, Ryan and I are actual investors in to Igno Yama. So we have exposure to what Omar is building here. But the thesis is that self-sauver and ZK technologies are going to be so proliferated and we need ZK proofers to be equally as democratized and accessible so that individuals can confirm their own ZK proofs, the fact that ZK roll-ups and other ZK technology are valid. When we have chips that are specialized for this, we can extend this out to more and more people.
It's highly aligned with the bankless philosophy. So that's why we are investors. I hope you enjoyed this interview with Omar. But first a moment to talk to some of these fantastic sponsors that makes it so possible. Kraken has been around for almost as long as crypto itself. As crazy as crypto is, Kraken has remained a rock for its clients, building out a platform designed to stand the test of time. Kraken is all about proof, not promises, which is why they've pioneered a proof of reserves, a system that lets Kraken's customers verify for themselves the solvency and responsibility of the Kraken exchange.
And for this reason and many more, we've chosen Kraken as bankless's strategic sponsor for 2023. And once you're done using Kraken to get your dirty, fiat money into pristine crypto assets, perhaps you should check out Arbitrum, where so much of the frontier of crypto innovation is taking place. Arbitrum just announced their stylist initiative, which is their brand new programming environment that lets developers deploy apps using their favorite programming languages like Rust, C, C++ alongside regular old solidity EVM apps. That's can use any coding language they like, and it simultaneously drops layer 2 fees by order of magnitude.
It's a big deal. So many of your favorite TPI apps have already deployed to Arbitrum like Uniswap. But did you know that Uniswap isn't just for ERC20 tokens anymore? Uniswap is also an NFT aggregator too, to make sure that you are getting the best price on your NFC purchases. Uniswap gives NFT collectors and traders powerful tools, all from the cozy comfy Uniswap interface. By the way, it's also got a native fiat on ramp. It's also deployed on like every layer too, and it's got this nifty cool thing called a universal router that ensures that you always get the best price on your trades. Crypto protocols like Arbitrum and Uniswap are becoming super powerful.
So make sure that you're also using a wallet that's equally as powerful, or else you'll be missing out. If you're looking to upgrade your wall experience, check out Phantom, the number one wall of Solana, which has recently come to both Ethereum and Polygon. Phantom has native NFT support, giving you your own NFT gallery from inside the wallet. Phantom is both a browser extension and a mobile wallet, and is also the only wallet to span both the Solana and Ethereum ecosystems. Check it out at phantom.app, and now let's get into the interview. Bigthos Nation, once again we are here at the StarCware sessions in Tel Aviv, and I'm here with Omar of Ingo Yama, and Ingo Yama is doing something quite interesting that you might not be familiar with.
Omar, can you kind of walk us through why we need Ingo Yama? So like every successful technology in history, we can say that there are three pillars to this technology. We have the software, the algorithms, and the hardware. So zero knowledge, which is a core technology in our space. It's basically a cornerstone for trustless computing, which is what we need for decentralization. Such is just such a technology, and we want to make it successful. We want to make it mainstream. We want to make it at the hands of everybody. So out of these three pillars, basically what we do is we are taking care of the hardware.
And so this is the hardware lesson. Once upon a time, the bank notation will know, I got into the world of Ethereum through GPU mining. It's also the world of ASIC's proof of work. How does, and this is the same sort of subject matter, but as it relates to zero knowledge computation, how does this world, how is this world similar to the proof of work industry and how is it also different? Right. So dynamics can be very, they are similarities, but I think one step before we need to understand what exactly is the connection or what do we need hardware for zero knowledge. And specifically, you know, zero knowledge, it's been around like decades in academia.
And only recently, over the last three years, it's doing this transition into industry. And we chose, in the space, with represented by many companies, what we chose is to focus on very specific type of zero knowledge proofers. You might have heard about snacks, stocks, and companies such as zero knowledge all upside. And basically, they have some very interesting properties, this type of zero knowledge systems. One of them is that the proof is very small. And the other thing is that it's publicly very fiable, okay? So before we even go into explaining what zero knowledge is, and why do we need it?
Just in terms of like the analogy here, to prove a fork, what we see is that there is kind of like a trade off, because we gain all of this like very nice properties, but we need to pay somewhere. And where we need to pay is by computing this proof. So it roughly takes seven orders of money to the more than the computation itself to actually compute the proof. Once you have the proof, you have a lot of power, right? But to get to this point, you need to spend a lot of money and compute power. This is where the hardware can make a big difference. You know, it's still going to be seven orders of money to the more computation.
But the fact that what you feel in terms of the cost, and the time that it takes you, we aim to make it as simple as possible, obviously, but also as close as it's possible to the user experience and developer experience that we have by just running the computation. Now what it means is that, you know, as I said, trust us computing is zero knowledge can mean many things. There are definitely a few applications that we see today that are touching or trying to replace exactly the old mechanism of whole fork by something that's based on zero knowledge. There are huge advantages of doing so, but this is far from being the only use case.
So I think that right now we are talking about level that is way lower, somewhat lower than the actual proof of fork type of mining that we had in the space. But it's definitely involved. It has some kind of relations to it. For example, you can build something similar to a proof of fork mechanism based on zero knowledge. Of course, with many benefits, I can go over. So it's been part of the trajectory of much of Ethereum to actually get rid of hardware. Like we wanted proof of state because we don't want to have proof of work miners. But there's a dynamic here about zero knowledge computations, which also is part of the broad Ethereum roadmap where we want like ZK rollups with zero knowledge proofs and other reasons to apply zero knowledge technology to what we're doing here, which means that are we committing to some sort of hardware layer to the Ethereum future because of just the commitment to zero knowledge?
Yeah, so that's a good question. And I think that to understand it or to answer it first, I do need to explain why ZK zero knowledge is useful in the context of Ethereum. So let me just take two big ideas. One is scaling, the other is privacy. Now in scaling, what zero knowledge basically is doing is kind of compressing, right? I mean, it's just like trying to simplify it a bit. We try to compress many transactions that we just don't have enough room to put them on chain. So we put only the proof. And it's very viable computation. Everything should be fine. In a way, we are saving a lot of money by doing so, right?
The end goal is to have to have it in a full decentralized manner, right? So you don't want people to actually create this kind of market around this kind of dynamics where you actually need, it's open only for certain type of actors. You want to enable anybody to obviously verify a proof. This is like definitely super cheap and efficient. As I said, is the properties of these like snark stocks that we chose. But you also want the proving and computing the proof to be done basically by anyone, even commodity hardware or close to it, such as GPUs. So this is just when it comes to scaling, I don't think that we are committing in a way to a future where we actually need to pay more or to consume much more electricity.
I think it would save us much more than in terms of when we try to compare it to what we know until now. Privacy, this is an application. This is like another thing that we can gain that was not accessible to us before. Privacy at scale, privacy on chain, privacy as a layer two. I think it's kind of an application that the knowledge is bringing and of course you need to consider the cost of such an application. Personally, I think it's a rightful cause and would pay for a future that is really great. And it's worth to kind of put some effort into it in terms of computation. What I'm thinking, again, this hardware is going to be in your, I don't know, your iPhone.
So part of the chip would run ZK, it would be seamless, right? It would be very efficient and so on. So again, I don't think it's going to go into committing to where we were going for, where we were coming from and, you know, rolling in this proof of fork to proof of stake transition. So the idea that I have for the future of Ethereum and actually even baked into the Ethereum roadmap is to ZK the whole entire blockchain. But then there's like applications that can use ZK tough and there's other layer twos that can use ZK stuff. All of this, anytime a zero knowledge is executed upon, that's a computation that needs to be run.
Where are we today? Like, how is that computation being done today? And with the future that you have in mind, how will it be done in the future? Right. So, yeah, that's true. ZK is very powerful and it can find use cases in many places. And obviously all of the two ZK all-ups and I think also at some point, optimistic or optimistic all-ups would start using this technology to some extent. So we are talking, if you try to sketch like a graph of the number of proofs per unit of time. So what I think would see is that now it's going and it's keep going, which is very interesting and at some point, it will consume a lot of electricity.
As you said, any application that is being built on top of a roll-up eventually would require to verify it on chain and it means another proof that needs to run. Not only that, you want to often run the same proof more than once so that in case something happens to one of the poover, you have like a backup, right? So it can scale, definitely, there are other type of ideas that are counter to that scaling, which are, for example, kind of pecking more than one proof together. So because basically you are proving a computation, you can also proof another proof, right? So you can just take them up in some kind of a recursive manner.
And this kind of saves you a lot of the trouble. This is a lot of what we see today in Zika roll-ups, how they move, like Stalkwell, for example, moved into using recursion, which allows you not only to stack proofs one or two another and eventually end up just with one proof, it also makes these proofs way smaller, right? Because you can just like aggregate them together. And so this is kind of counter trend to the growing need in proofs, right? What will happen is that with the introduction of hardware, getting these proofs, going to be the threshold or the barrier to get these very complex proofs and computation, we just get lower and lower.
And usually, just like with other inventions, what it means is that there would be more and more use cases using these proofs. So I think that overall, we're just seeing increase in the number of proofs, but definitely it would be contained. And to be contained at the hardware level, it would be contained in the algorithmic level in a way that would be manageable and for us as a community, it would eventually be a net positive. So to use a metaphor, would you say it's fair to say that Ingoyama is trying to build the engines to run zero-knowledge computation, like you're building the combustion engine for zero-knowledge?
Yeah, kind of. I mean, we're building computers. You know, you can look at the traditional computer architecture and something is missing. I mean, something that, like, you know, a finite field arithmetic, some discreet math, like the stuff that are fundamental in the computer architecture is not really accelerated. It's not used in AI, network storage, acceleration, but it is needed in cryptography, even not just zero-knowledge, fullyomorphic encryption, and even, you know, lattices and such, like basically the basics of post-quantum cryptography, everything is built on the same math. We're just trying to bring a modern type of computer architecture that will support natively this type of computations.
So it's the idea that what you just said that we have this new thing in this world called zero-knowledge proofs. They're computationally intensive. Is a future state of the world? One where there is a new component, a new hardware component in perhaps every single device out there, my phone, my computer, my laptop, that is specialized to run a zero-knowledge proof. Is that kind of the future that we're looking at? Yeah, absolutely. I mean, and we also can tell, you know, it's going to start from more of the server side, like the data centers. This is where it's easier to kind of take an all-new computer architecture and just push it and then get some optimizations in running ZK Provers.
But you know, phones that are like very, the phone factor very small is going to be very hard. But let's say decentralized identity. This is something that we know, several like phone vendors, manufacturers are looking very deeply into. So this will require some of these functions, like so many people that are relevant to that border like ZK Provers computation, but they can also fit inside like chips that are being manufactured by others. Also, you know, when it comes to privacy, eventually you need it in your hand, you need full control. So it's definitely going to be like in every one of our hands, in phones and so on, yeah.
Yeah, so I know one of the big conversations that's going out here at the StarCware sessions is account abstraction and how account abstraction uses the secure enclave of a phone to store data to unlock, you know, assurances about a private key. And so there's already the conversation happening about how does our physical hardware impact the technology that we have in the virtual space, right, like even though we're all love to be in the metaverse, the physical nature of our hardware is still very, very important. And so maybe another to use another metaphor is like we have this secure enclave to store our private keys.
And that's a physical component of our devices that help us do our crypto things. And then what you're perhaps envisioning is that there's also going to be another additional part of a hardware that is meant to do zero knowledge computation to allow for zero knowledge computation to be done by the individual on their device. Is that all lined up with you? Yeah, I think it is. Like when I look at the future in a world where ZK is cheap, I mean, there's no reason why you cannot just verify any computation you do. I mean, the entire, everything you run on the phone, including communication with secure enclave and so on, can be very fibrous.
I do can also output the proof that the computation was done correctly. It's even more important once you outsource the computation to someone else, I don't know, to the cloud. I think it can be very fibrous and it should, right? So I think, yeah, I think we are talking about kind of a new modern type of architecture that will also include a component that is specialized for this type of cryptography. Yeah, and if we don't have this kind of research and this kind of like R&D effort that you're doing, then we probably ultimately outsource that proof generation to a third party, which is not exactly what we're going for in this world of self-sauver and like technology.
Is that a fair assumption? Yeah, it is. I mean, there's an ongoing research on how you can actually separate the compute intensive part from the privacy preserving part of the computation. It's not easy, there are a few ideas and it's, you know, right now it seems very far away. So I think definitely a way to go is to try and get everything done on the hardware locally and it's a future. It will take a lot of time, but we'll get there. Meanwhile, there are many use cases and applications that can still run only on data centers by minors and you know, some people and corporates that have access to this like to this like specialized hardware.
That's for sure. But yeah, we are going into the this like future where there's a six that are like different chips that can be used in any type of computing device and can bring you this technology to deliver that again, user experience, it's going to be completely seamless. You won't feel that you are computing a proof. So maybe we can really judge about how trustless and self-sauver in the world is with how many, how far your chips have proliferated across the world. I mean, it's one way to look at it. Again, remember that right now, even the all apps, the Ziki all apps, all of them are more less centralized.
So there are still far way to go. We still need to and you know, we are a hardware place. So we are long-term thinkers. This is how we are building the company. Yeah, I mean, at some point I do hope that many of us would have this freedom of just know, very fiable and private type of computer, privacy-preserving computation, very fiable computation, it will take time until it will get basically to be democratized and be by the hands of anybody, yeah. So the topic of hardware is not one that we've actually talked a lot about on bankless. And so this is probably striking the imaginations of a set of bankless listeners that doesn't previously get a bunch of attention.
Walk us through the roadmap for like how a chip actually gets produced and what is the roadmap for for Ignayama. Right, so the first thing to understand about us is that we are not religious about hardware. Meaning that you know, there are a few types of specialized hardware with differences. I can name a few FPGA's, GPU's and of course ASIC's like this like specialized chips. For us it's about finding where is the pain and then solving it and when I say solve it is about catering for the little guy again. We want to make the user experience seamless, that's the goal, that's the ideal. And what it means is that right now in terms of roadmap, we are doing a lot of R&D internally to kind of build our hardware and our IP to on everything.
What we want to do is basically run everything inside of this like specialized hardware. And then we try to feed the right solution to the right problem, right? So you can think about let's take Starcore, right, we are in a Starcore event, let's take Starcore for example. So for Starcore right now the poover is centralized, it's one problem, it's not the most important problem they have. They have also a problem with witness generation, with sequencer, they pay much more on getting the transaction on chain for fees than they pay on running the poover. So when we are talking with Starcore and we want to develop hardware, what we basically try to do at this point is just to move the bottleneck from the poover to somewhere else in the system.
Okay, now at some point these other places in the system would also have their bottleneck removed. The only bottleneck that I predict will remain would be the hardware for Zika Provers and maybe a bit beyond. But right now it's just about being efficient enough and cost effective enough to move this bottleneck someplace else in the system. That's one example. Obviously we have projects where we want to optimize on the throughput, right? One to one as many poofs at the same time and we don't really care about the cost, let's say. There are other projects where we care just about the phone factor.
We have a project by the way for five coin where it's mostly about just replacing GPUs with FPGAs that are tiny, right? It's like small, it fits a data center. So it really depends. Overall our vision is, and I think this is the long-term solution, is to have these dedicated chips. And to go to this place, we need a lot of, we first need to come up with an architectural. Something very similar to a GPU if you try to think about it, like many, many cores that run in parallel, but are suitable to the type of computation that you can see as the old knowledge. And once we have this figure out, remember that Zika and this public question many ask is, it's a fast moving space, like everything is kind of changing.
How do we de-risk it when we build something that is meant to last for many years to come? And one way that we try to do it is by basically building it in a programmable way. That's one thing and the other thing is to battle test it all the time, right? So every time there's a new Zika protocol primitive coming out for Macadini event, we try to kind of retake it and see if we can support it and to what extent. And then we fine tune our design. Hopefully we'll be able to go to a tape out, which is to your question, kind of the no return point, or you kind of say, okay, this goes and when it gets back, it's in silicone, then it goes into, I don't know, miners and whoever needs it.
So hopefully we'll be able to go to this tape out soon, meaning when I'm saying soon, it still means, like, you know, can be in a couple of years. And it's really going to depend on how this market is going to evolve. We first want to target all apps, Zika all apps. Therefore, we are very much dependent on their decentralization efforts. And we try our best also to help with what we can. Amir, if somebody is interested by what you are doing, what you've talked about here today, how can they join, how can they help, who do you need help from, or how can people get involved? Right. So at this point, we do mostly R&D.
My team, they are a bunch of very talented, equippedographers, mathematicians and hardware guys, like chip designers, architects and so on. We are trying to build an ecosystem in software. What we're going to do soon is going to open source, much of what we do. Hardware is traditionally a very close source type of environment. This is not good for our space. We try to break this narrative, we try to go and be and walk in the open, be transparent and also put some code and IP out there for people to use and play. Feedback is critical from developers mostly that are going to build on ZK. Any type of application, everything is applicable.
You can find us in Twitter, Ingo, ZK. We have a website, we launch not long ago in goniamma.com. We have a GitHub with all of our stuff open. We have a Discord that soon we're going to launch it officially. Right now, if you are working on some technical problem and want to join the Discord, meet the team. This is a very good place. Reach out to me and I'll be able to connect you with the team. Omar, thank you so much. Thank you.