Enable an o1js browser prover on a cross-origin-isolated page
A browser-based Mina prover can load its JavaScript bundle successfully and then fail when its worker needs shared memory. Diagnose the browser environment on the actual deployment URL.
Inspect the document response
Serve the proving page over a secure context with the documented opener and embedder policies. Inspect the final HTML response after redirects, then inspect window.crossOriginIsolated and availability of SharedArrayBuffer in the browser. Headers attached only to the Wasm file do not set the page's top-level isolation policy.
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Embedder-Policy: require-corp
Run a real proof in the worker
Check worker, script and Wasm requests for cross-origin policy failures and configure their sources accordingly. Use a small known circuit to generate and verify a proof in the deployed build. A successful local build or wallet connection alone does not exercise the shared-memory prover path.