I don't love it, but I have to acknowledge that a frontier model building a feature that uses cryptography is going to have a better track record than the median human developer. The immediate practical problem with cryptography engineering has always been that there's a huge amount of detail you need to understand in order to get something right, but only a little bit to know to get something working. LLMs know all the details. They take shortcuts, but fuckups in mainstream cryptography features aren't really about shortcuts, they're about knowledge.
The most important thing to do with cryptography features is to stress test them ("spend $10 on verification for every $1 on implementation"), and that too has become a lot easier with frontier models.
> building a feature that uses cryptography is going to have a better track record than the median human developer.
Let’s say that’s true. That doesn’t mean that we won’t have a higher percentage of bad implementations because more people are rolling their own.