One Bug Fixes Most C Code Vulnerabilities | Tudor Achim2
MTS
October 31, 2026
Harmonic co-founder and CEO Tudor Achim discusses expanding their Aristotle formal verification system from math proofs to C code and chip design.
Tudor Achim
I think a lot of exploits in really security-sensitive code, like C code, chains together these things called memory exploits where the programmer allows for some behavior that was not intended, like writing to some memory you don't own or using some data after you technically had permission to use it, and then combining memory exploits with things like privilege escalation, other bad behavior.
If you can completely get rid of that first class of issues like memory safety issues, you actually limited a lot of vectors for hacks. So that's one way in which verifying your code can reduce your risk of security breaches.
Sophia
Everyone, welcome back to MTS. Today, we are joined by Tudor Achim, the co-founder and CEO of Harmonic, which this week expanded its Aristotle system for math proofs to verifying C code and chip designs. Tudor, welcome to MTS.
Tudor Achim
Hi. Nice to meet you. Thanks for having me.
Sophia
Great to have you on. I know you guys had a big week this week. You guys went viral as well, all on X. Tell us a little bit about what you guys announced.
Tudor Achim
Yeah. Aristotle, I think, to my knowledge, is the first product available that's generally available that can verify all sorts of C code, hardware designs at very large scales.
And we just think this is really important in this new generation of cybersecurity where it seems like everyone's getting hacked all the time because humans wrote a lot of code that had a lot of problems. So now you can kind of check it, make sure it's right. And the code you write in the future, you're really guaranteed to not have certain classes of issues that code of the past did. Yeah.
Sophia
So for people who are not familiar, what exactly is verifiability and why is that important in our code?
Tudor Achim
Yeah. When you verify code, you can think of it as stepping logically through it like you would in your head, but in a way you can check with the computer. So when you're a programmer, when programmers used to write code by hand, you'd have some idea of what the code assumes, and then you step through it in your head and you say, okay, well, if I had these assumptions of the input, then my code that I wrote, it can only do so many things, so I can prove something about the output and you do that in your head.
When you verify code with the computer, you do that same process except instead of all that logic living in a developer's head, the computer writes it out in the computer language and another computer program checks it. So code is verifiable if you can check the logic with the computer in that way.
Historically, a lot of code has not been verifiable. People had to create new languages to verify it like Lean, which I think is the best interactive theorem prover. But now, if you can compile existing software code to Lean, now all of a sudden the existing software code becomes verifiable as well, and that's exactly what Aristotle does.
Sophia
When things are more verifiable, explain how that prevents hacks.
Tudor Achim
Well, it doesn't prevent all hacks. So I think there's a meme on Twitter that verifying everything prevents all bugs. You can imagine verifying code just means that you're 100 percent sure the code does what it says it does. So if you formally verified some code like a web server, and then you run it with a configuration that says the password to it is password, you're going to get hacked no matter how verified that code is.
But it turns out a lot of exploits in really security-sensitive code like C code, chains together these things called memory exploits, where the programmer allows for some behavior that was not intended, like writing to some memory you don't own, or using some data after you technically had permission to use it, and then combining memory exploits with things like privilege escalation, other bad behavior. If you can completely get rid of that first class of issues like memory safety issues, you actually limited a lot of vectors for hacks. That's one way in which verifying your code can reduce your risk of security breaches.
Sophia
If we're thinking of a specific example, for example, the Binance theft, this is $6.3 billion is one of the probably the biggest crypto hack ever to date. Can Aristotle help out here? Is there anything that Aristotle could have done to roll it out and prevent this attack?
Tudor Achim
Well, I think that one happened yesterday, so I don't know if anyone knows exactly, outside of Binance knows exactly what happened there.
Read the other 16 minutes of this episode here.
$15 gets you this episode and 99 more. Credits never expire. After checkout, one link brings you back here to read it.
Not what you expected? Full refund within 14 days.
Thousands of transcripts fetched by people building searchable podcast archives
Fetch transcripts with code
The same credits work from a script or an AI agent. The demo key returns a sample episode in full, no card needed:
curl -H "x-api-key: pt_demo" \
https://spoken.md/transcripts/1000651996090Markdown with the speakers named, for your notes, your knowledge base, or anything that makes HTTP calls.
From $0.10 per transcript. No subscription. Credits never expire. Prices exclude VAT, added at checkout for EU customers. Not what you expected? Email us within 14 days with 20 or fewer credits used and we refund the pack in full.
Using your own key:
curl -H "x-api-key: YOUR_KEY" \
https://spoken.md/transcripts/1000798995786