How Loom works

Compute becomes useful
when results can be trusted.

Loom is a browser-first GPU execution design. It separates local computation, result verification, and public settlement so each layer can be measured independently.

01 / Inspect

Know the available path.

The client requests a high-performance WebGPU adapter and reads only browser-exposed capability data. NVIDIA, AMD, Intel, and Apple devices share the same run interface. WebGL2 provides a limited fallback where WebGPU is unavailable.

02 / Execute

Run with explicit consent.

The operator chooses a 15, 30, or 60 minute session and approves sustained GPU load. The run can continue behind another browser tab, but the Mine page must remain open. Closing or navigating away interrupts it.

03 / Verify

Do not trust a self-reported score.

A production coordinator must issue signed, short-lived leases with committed inputs and hidden challenges. Deterministic results can be replayed on verifier-controlled hardware before any reward is accepted.

04 / Settle

Commit covered claims.

Accepted entries can be grouped into epochs. A Solana claim program can hold vault assets, publish a Merkle root, prevent duplicate claims, and transfer only liabilities already covered by the treasury.

Hardware paths

One network interface.
One reward asset.

NVDAxNVIDIAEligible for NVDAxNVDAxAMDEligible for NVDAxNVDAxIntelEligible for NVDAxNVDAxAppleEligible for NVDAx

Questions

How the network is designed to work.

Do bigger holders earn more?+

Mining-pass tiers are based on the $LOOM value recorded when a 24-hour pass is issued: $30 for 1x, $300 for 1.25x, and $3,000 for 1.5x. The required threshold is checked again at lease start and completion. Tokens are not locked or staked, and a higher balance applies only after requesting a new pass.

What is a job?+

A buyer pays for bounded GPU work such as an inference response or a set of rendered frames. After the Solana payment is finalized, Loom can place the work in the queue and assign fragments to compatible mining sessions. Only verified output completes the job and enters reward accounting.

Is this actually mining?+

It is not proof-of-work mining like Bitcoin. A production session runs useful GPU workloads for at least 15 minutes under a signed lease. Rewards come from funded treasury inventory rather than newly minted tokens.

What do runners receive?+

NVDAx is the only planned runner reward. Every eligible verifier-accepted run maps to NVDAx regardless of the GPU vendor reported by the browser.

Where do rewards come from?+

The treasury can be funded by paid jobs, disclosed protocol funding, and transparent treasury acquisitions. An epoch can promise only assets already held in the corresponding token vault.

Why launch through Stonk?+

Stonk is the intended launch and trading venue for $LOOM. The verified token page will be linked directly after the mint is configured. Launching the token does not activate runner rewards by itself; paid jobs, verifier acceptance, and funded xStock vaults remain required.

Why does the treasury hold about 10% of supply?+

The disclosed protocol treasury allocation is approximately 100,000,000 $LOOM. Its purpose is to support covered runner rewards, network incentives, and protocol continuity while buyer-funded compute demand develops. It does not guarantee yield or a reward rate. Until multisig custody and a public movement policy are active, holders should treat the allocation as controlled—not locked—supply.

Is it safe for the computer?+

The runner uses browser WebGPU or a limited WebGL2 fallback and installs nothing. It can sustain high GPU load, increase power use, and spin up fans, so every run requires explicit consent and can be stopped at any time.

Does Loom know the exact GPU?+

Not always. Browsers intentionally restrict hardware identity. Loom displays only the vendor, architecture, or model information the browser exposes and treats uncertain identities as unknown until server verification.

How are false runs rejected?+

Production runs require a signed mining pass and a wallet-bound, one-use lease. The server issues an unpredictable challenge every minute, enforces its arrival window, requires advancing workload telemetry, and calculates the reward from server-observed duration. Missing, early, late, duplicated, or replayed checkpoints are rejected. This verifies continuous protocol participation; ordinary browsers still cannot provide cryptographic GPU attestation.

Why is $LOOM required?+

$LOOM gates production mining passes and their tier multiplier. The one-minute public trial remains available without a pass and publishes with a no-reward label, but it never enters a reward epoch.

Is this investment advice?+

No. Loom is an early-stage compute protocol. Token and xStock prices can move, treasury inventory can change, and no reward amount is guaranteed.

Current boundary

Sessions can be verified.
Claims require covered epochs.

Production runs use wallet-bound, single-use leases, server time, and one unpredictable checkpoint per minute. This verifies continuous protocol participation but is not cryptographic GPU attestation. Verified runs accrue nominal liabilities; no claim becomes payable until the NVDAx vault covers the epoch and the finalized Merkle root is published on Solana.

Enter Loom ->Read blueprint ->