FastProcessor fix prevents wasm trace hangs
The release fixes FastProcessor::execute_and_build_trace_sync aborting when compiling targets that use a full std but cannot spawn threads (e.g., wasm32-unknown-unknown). Previously, a failed thread spawn panicked under panic=abort, which trapped the module and left an in-browser “prove” step hanging without an error. The FastProcessor builder thread is now spawned fallibly. If thread spawning is refused, the trace is built sequentially instead, avoiding the silent hang and improving reliability of in-browser proving.
Neutral
This update is a software reliability fix for FastProcessor’s execution/trace building in WebAssembly contexts. It does not directly affect on-chain tokenomics, protocol parameters, or liquidity. For crypto traders, the main relevance is operational: if an in-browser proving workflow previously hung on wasm32 targets, users and teams could face stalled proof generation, which can indirectly affect product availability or downstream applications. However, the change is corrective rather than feature-expanding, so broader market stability is unlikely to be meaningfully impacted. In the short term, developers relying on wasm proving pipelines may see fewer failures and faster incident recovery, reducing support load. In the long term, improved determinism and error visibility in proving systems can lower friction for tooling and integrations—an effect that tends to be gradual and more “neutral-to-slightly-positive” for ecosystem confidence, but not enough to drive clear bullish or bearish price signals.