I thought I might just use this thread to also share my thoughts on this topic after reading the recent posts from Potuz, Ethlabs, Mike and Thomas. Definitely recommend reading all of them.
Very short summary: Potuz and Ethlabs want to go all in on PQ and only ship what’s really needed. Mike thinks rushing PQ is premature, but agrees that hardening the clients is super important. Thomas wants to parallelise and keep shipping non-PQ features like FOCIL.
I think pqai will come with all kinds of threats, and AI getting better at finding bugs is the one we already experience. The PQ changes alone are already a lot of new code: new signatures, leanVM, much bigger messages on the p2p layer, new key handling. Every line of that needs to be understood by someone, tested and hardened. That’s risky enough already, so I’d rather not add more features on top.
For people hunting bugs, it makes a big difference whether a fork is Frames or Frames + FOCIL. More code means more to understand and test, more interactions, and that doesn’t really parallelise. So I could see the PQ work being done as “slim” feature forks (Frames, leanVM, DC), with FOCIL coming back once we know what PQ consensus looks like.
The only things I’d ship alongside are hardening and simplifications. E.g. repricings that fix real mismatches: if we ship them without a gas limit increase, that’s basically hardening ![]()
I think in times where AI gets really good at breaking things, that kind of work will be very welcome.