The main thread never loads WASM directly — it communicates with this
worker via MessageChannel RPC (see HashiverseWorkerRPC for the
message types). On startup the worker initialises WASM, spawns a pool
of HashiversePowWorker sub-workers for proof-of-work, then
signals readiness to the main thread.
Every method call on HashiverseClientWasmProxy in the main thread arrives
here as a { type: "call", method, args } message, is dispatched to
the WASM client, and the result (or error) is posted back.
Dedicated Web Worker that owns the HashiverseClientWasm instance.
The main thread never loads WASM directly — it communicates with this worker via
MessageChannelRPC (see HashiverseWorkerRPC for the message types). On startup the worker initialises WASM, spawns a pool of HashiversePowWorker sub-workers for proof-of-work, then signals readiness to the main thread.Every method call on HashiverseClientWasmProxy in the main thread arrives here as a
{ type: "call", method, args }message, is dispatched to the WASM client, and the result (or error) is posted back.