SNJU is building a decentralized coordination layer for AI compute. It is designed to let independent capacity, builders, and communities meet through verifiable network rules.

AI compute should behave like shared infrastructure.

The largest AI workloads increasingly depend on scarce, geographically uneven capacity. SNJU proposes a different coordination model: make diverse compute resources discoverable, taskable, and accountable without requiring one operator to own the entire network.

01Open participation
02Verifiable work
03Clear protocol utility

From request to accountable execution.

SNJU is designed as a coordination loop, not a simple marketplace listing. Each step gives participants a clear responsibility and a record that the next step can inspect.

Request

Describe the workload

Builders express compute needs in a task format that can be evaluated by participating providers.

Match

Discover capacity

Providers surface compatible hardware, availability, and execution conditions through network-defined signals.

Execute

Run with receipts

Work is intended to produce structured evidence so that results and obligations can be examined.

Settle

Close the loop

Protocol rules can coordinate settlement and future reputation inputs without relying on opaque manual reconciliation.

SNJU aligns the network around useful work.

The token is framed as protocol utility for participating in and governing a decentralized compute coordination system. It is not presented as a financial promise.

Coordination

Supports task lifecycle actions and network-level coordination where protocol rules require a shared unit.

Verification

Can underpin challenge, review, and accountability flows that help make reported work more inspectable.

Governance

Provides a basis for community participation in protocol parameters, upgrades, and public standards.

Task flow explorer

WORKLOAD PATH

Inference routing

Routes a compatible request toward capacity with stated runtime conditions, then records an execution receipt for later inspection.

A network built by distinct contributors.

SNJU is designed around roles with different incentives and responsibilities. No single role should need to be the gatekeeper for every workload or decision.

CAPACITY

Operators

Make independently owned compute available under transparent participation rules and runtime commitments.

DEMAND

Builders

Bring inference, training, and evaluation workloads that can use distributed capacity without surrendering the workflow to a single provider.

STEWARDSHIP

Community

Helps shape standards, governance processes, verification expectations, and the conditions for healthy participation.

Building the conditions for a durable network.

The roadmap describes design priorities rather than a delivery guarantee. Sequence and timing may change as the protocol is tested and reviewed.

Foundation

Define the workload model, operator participation requirements, and the evidence expected from task execution.

Coordination

Develop matching, task lifecycle, and receipt concepts that can connect builders with heterogeneous compute capacity.

Verification

Refine review and challenge mechanisms that make execution claims easier for network participants to inspect.

Governance

Establish a transparent path for community input on evolving parameters, standards, and protocol upgrades.

Read the architecture before you form a view.

The SNJU whitepaper explains the problem framing, proposed protocol layers, participant roles, governance approach, and risks of decentralized AI compute coordination.

Open the SNJU whitepaper