DCDistributed Compute Labgeneral compute fabric · phase 2

ANONYMOUS COMPUTE NODE

Here I am. This is what I can do. Send me work.

No signup, email, password, or payment account. This browser announces its measured capabilities, executes only approved workload modules, returns timing metadata, and earns VCU only for verified work.

Session runtime00:00:00No account required. Ready for the 24-hour experiment.
WorkerAnonymous browser workerCreated at start
Test groupungroupedref:
Wake LockunknownScreen persistence control
ConnectionNot connectedvisible page

Worker control

Ready to contribute

ready
Current activityWaiting to start
Approved module protocolv2 · parameter-only jobs

Device policy

How should this device run?

Verified Compute Units0VCU · not dollars
CPU throughputraw operations/sec
GPU throughputraw WebGPU ops/sec
Active / idle0s / 0s0 jobs · 0 late

Current capability

Handshake not run

CPU
SystemDetected at start
CPU score
GPU scoreUnavailable
Network
Concurrency
GPU adapterNot exposed

Experiment hypothesis

Can opening a website create a dependable compute fabric?

  • Current and historical CPU/GPU capability
  • Dispatch, compute, upload, and coordinator timing
  • Browser suspension, Wake Lock loss, and reconnects
  • Adaptive 2–10 second job sizing and dynamic deadlines
  • Verified work, VCU, and redundant-compute overhead

Security boundary: jobs select a versioned built-in module and supply parameters. The coordinator never transmits arbitrary executable code.