Register capability
The browser reports a small capability profile such as logical processors and supported web features. ScubaRC does not inspect personal files.
Built to test governed participation.
Help test governed browser compute infrastructure with a synthetic Alpha workload. Your device receives one bounded work unit, computes locally in the browser, and returns a constrained result receipt for verification.
No arbitrary file uploads. No shell access. No access to your personal files. Stop by closing the page.
Founding cohort
A live test of community-powered research infrastructure.
—browser enrollments (Surf + compute)
—devices registered
—reported logical CPU threads
—verified result receipts
—reported runtime · accepted results
Loading saved activity…
These are cumulative database totals, not a count of people online. Surf and compute share browser enrollment; returning on the same browser does not add a new enrollment. Reported CPU threads describe registered capability, not donated processing time.
Each accepted result adds a receipt. Runtime is reported by the browser and is not an independently measured compute donation. This tiny synthetic task can finish in milliseconds. Opening the page or clicking a link does not count as completed work; repeated clicks do not prove unique participants.
Contribute now
Run one safe Alpha work unit.
The Alpha uses a fixed browser workload. It does not download arbitrary executable code. You choose when to start, and computation ends when the work unit completes or you stop the page.
Your computer is contributing.
Preparing bounded work…
How it works
Compute is contributed. Authority is not.
Receive bounded work
The task governor issues a constrained Work Envelope with a work ID, fixed task type, input, resource limit, and expiration.
Return a receipt
The node returns a small structured result. The server validates the receipt before counting it as a verified Alpha work unit.
The current Alpha
A temporary browser compute node
When you explicitly contribute, your browser becomes a temporary browser compute node for one bounded work unit. Genesis Alpha is testing the infrastructure and participation model, not claiming scientific discovery.
What your browser reports
The enrollment payload includes a limited capability profile: device class (mobile or desktop), platform, logical processors, WebAssembly support, WebGPU availability, and the browser user-agent string (up to 300 characters). These are browser reports, not a trusted hardware inventory. Reporting WebGPU availability does not mean this workload uses the GPU.
This capability report does not grant ScubaRC shell access, arbitrary code execution authority, access to personal files or desktop applications, or camera/microphone access. The Community Compute application does not upload your personal files or grant remote-control/shell access.
The server chooses allowed work
The server governor assigns a work envelope with a work_id, fixed work_type, bounded inputs (an integer seed and iteration count), an iteration resource limit, expires_at for assignment validity, and a max_result_bytes limit. Volunteer devices do not choose authoritative research tasks and are not trusted with research-state authority. The server checks the assignment and result before acceptance.
What runs locally today
The current Alpha workload, mix32_v1, is a synthetic deterministic test workload, not a scientific research calculation. It runs locally inside a browser Web Worker. The Alpha does not download arbitrary task code from the server: compute-worker.js contains the fixed implementation, accepts only the approved work_type, and validates integer inputs and bounded iterations. The present worker iteration maximum is 5,000,000; the governor currently issues smaller workloads, capped at 1,500,000 iterations.
Participation is voluntary. Closing/stopping the page ends participation; a work unit also stops when it completes. No compute work completion is required to play Commonwealth Surf.
Results are candidates for verification
The browser returns a constrained result containing work_id, result, runtime_ms and client_version, together with node_id. Its pseudonymous node credential authenticates the request. The server checks the assignment and compares the result with its expected deterministic value before issuing a receipt and counting a verified Alpha work unit. A returned result is not authoritative simply because a volunteer device produced it.
What the application sends
Application payloads include the limited browser capability profile; optional display name, locality and Virginia participation information deliberately entered by the participant; consent and human-verification information; work/result metadata; runtime/client information; and authenticated pseudonymous-node requests. Optional locality and Virginia participation are for internal/aggregate research measurement, not a public Surf player label. Players from any state may play and appear on the leaderboard. Normal connection metadata may still be observed by underlying network infrastructure.
What we are testing
- Can browsers enroll as temporary nodes?
- Can the governor assign bounded work?
- Can heterogeneous consumer hardware execute it reliably?
- Can returned work be verified before acceptance?
- Can invalid, disconnected or malicious results be rejected?
- Can participation be measured without granting volunteer nodes authority?
The security model
VOLUNTEER DEVICE != TRUSTED DEVICE
RETURNED RESULT != AUTHORITATIVE RESULT
COMPUTE CONTRIBUTED != AUTHORITY GRANTED
The design assumes a volunteer browser can fail, disconnect, return incorrect data, or behave maliciously. Authentication identifies a pseudonymous node; it does not make the device or its output trustworthy.
What could come later
If this infrastructure proves reliable, separately approved future experiments could investigate appropriate public-data, highly parallel workloads: simulation sweeps, parameter searches, Monte Carlo work, numerical analysis, model evaluation, and other decomposable, independently verifiable workloads. These are future possibilities, not workloads operating now. Real scientific workloads require separate security, privacy, and scientific-validation gates.
This is a research infrastructure demonstration.
Community Compute Alpha is intentionally constrained to harmless synthetic test work. It does not process classified, CUI, medical, private, or other sensitive research data. Volunteer devices are treated as untrusted execution nodes; returned results are candidates until independently verified. The Alpha validates participation, execution, verification and governance. Real sensitive or scientific expansion requires separate security, privacy and scientific-validation gates.