If they don’t rearchitect it then eventually it won’t be able to validate. They resisted doing this forever, instead working toward mechanisms that weaken the security model by not validating. But now that we have shown that it’s a software issue and not a Bitcoin issue, they have been forced to face these design flaws. @neillm is right, someone will eventually do this work at some point. They are working on a technique that allows someone to download the uxto state produced by someone else, and assume valid faster by relying on this. But of course this presumes someone can actually produce it. And it assumes there’s a reasonably trustworthy source for it. Then they will eventually do the significant amount of work required to not only validate concurrently, but do so at full capacity. This means making the network stack asynchronous, and creating a massively concurrent store.