Theorem co-founder
@diagram_chaser reveals the one-line change that took verifying real-world HTTPS code from 4,000 millennia to seconds:
"The project that I worked on in my PhD was verifying the code that runs HTTPS in browsers like Chrome and Firefox."
"You plot this beautiful graph that is an exponential in the number of bits in the prime, where you're like, it takes a couple seconds on my tiny toy examples, and on real-world examples, it would take over 4,000 millennia."
"The thing that it's actually checking is that you wrote the same thing in two different ways. This should be very fast. It's doing the operations in the wrong order."
"So you tweak one line, and then it drops down to a couple seconds."
@theoremlabs