Title: Two questions — WASM fallback + workerName config
Two issues on a consent-first deployment:
1. WASM always falls back to JS
Console shows WebAssembly failed, using JS fallback in every environment tested, including HTTPS with correct COOP/COEP headers and crossOriginIsolated === true. RandomX WASM works fine in other libraries on the same setup, so the issue is specific to webminer's WASM loading.
- What's required to activate the WASM path?
- Is there a debug mode that shows why WASM init fails?
2. workerName / session ID
The public config only exposes pool, wallet, throttle. I need a unique worker name per session for pool-side attribution. Currently using wallet.session_id as a workaround — is this the intended pattern, or is there a proper workerName field?
Happy to share benchmark data if useful.
Title: Two questions — WASM fallback + workerName config
Two issues on a consent-first deployment:
1. WASM always falls back to JS
Console shows
WebAssembly failed, using JS fallbackin every environment tested, including HTTPS with correct COOP/COEP headers andcrossOriginIsolated === true. RandomX WASM works fine in other libraries on the same setup, so the issue is specific to webminer's WASM loading.2. workerName / session ID
The public config only exposes
pool,wallet,throttle. I need a unique worker name per session for pool-side attribution. Currently usingwallet.session_idas a workaround — is this the intended pattern, or is there a properworkerNamefield?Happy to share benchmark data if useful.