Participate

Help build the next phase of Scalar.

Register interest as a compute operator, validator, developer, researcher, or observer. Share how you would contribute to future controlled testing.

Interest registration open
Three paths

How could you participate in Scalar?

Build on it, contribute compute, or check other people's work. Each path is gated by the current testnet stage — nothing here is a sign-up for something that is live today.

Path 01 · For application developers

Build

Connect an application, send Scalar bounded jobs, and get back results you can actually inspect — with evidence, a Braid trace, and eligible artifacts for reuse.

The public gateway is unavailable. There is no API signup and no keys are issued.

Public gateway · unavailable
1Connect application2Submit bounded job3Receive result4Inspect evidence5Trace Braid6Reuse eligible artifacts

Intended developer flow

Path 02 · For hardware operators

Compute

A Useful-Work Miner runs real jobs instead of arbitrary puzzles. Its hardware takes eligible work, executes it, and returns evidence that must survive independent validation before anything counts.

GPU
CPU
RAM
Storage

No earnings are shown because none exist. Any future compensation model would be published as a simulation first.

Economics · future / simulated
1Hardware2Eligible job3Execution4Evidence5Proof6Validation

From hardware to validated contribution

Path 03 · For independent checkers

Validate

Validators independently re-check work against its acceptance criteria. The system only works if the roles stay strictly apart.

  • A miner cannot validate its own work.
  • A validator cannot edit worker output — it can only accept, dispute or flag it.

Agreement between validators is evidence, not objective truth.

Tokenless testnet · controlled
Minerproduces outputValidatorchecks, never editsMINER CANNOT VALIDATE OWN WORKVALIDATOR CANNOT EDIT WORKER OUTPUT

Strict role separation

Network participation roadmap

The network opens one stage at a time.

Each stage opens only when the one before it holds up. There are no dates, because the gate is evidence, not a calendar.

  1. 01 · You are here
    Controlled

    Phronesis-operated machines, tokenless, narrow job classes.

  2. 02
    Qualified providers

    Vetted outside operators run workers under supervision.

  3. 03
    Independent operator

    Operators run nodes on their own infrastructure.

  4. 04
    Federated

    Multiple organisations coordinate validation and routing.

  5. 05
    Broader network

    Wider participation, once validation holds under real pressure.

What to expect

  • ·Registration creates no entitlement to tokens, allocations, or rewards.
  • ·Registration is not an application and carries no queue position.
  • ·Registration does not guarantee contact, selection, or broader public testing.
  • ·Test network state may be reset during development.

Most useful to us right now

People who have built distributed systems, validation or verification infrastructure — and are willing to explain precisely why part of this design will not work.

Participation creates no right to future Scalar tokens, allocations or rewards. No token is offered, sold or distributed. Testnet state may be reset.

Anti-fraud

Verify official availability

No token, sale, presale, allocation, airdrop, or whitelist is available. Review the project disclosures before acting on any third-party claim.