DECENTRALIZED COMPUTE LAYER · POWERED BY KASPA

Turning idle GPUs & CPUs
into verifiable compute power

KASCompute is a dedicated compute layer built on top of Kaspa’s BlockDAG. Providers contribute hardware, clients submit workloads — settlement and verification are anchored on Kaspa.

Read Whitepaper Open Testnet Dashboard

Kaspa BlockDAG Proof-of-Compute GPU & CPU Providers

Kaspa
BlockDAG

Compute
nodes

Clients

Tasks

Global compute anchored on Kaspa

Protocol overview

What is KASCompute?

A dedicated compute layer that converts idle hardware into a coordinated, verifiable and economically aligned network — secured by Kaspa.

Decentralized by construction

No central operator. Independent nodes join permissionlessly and are rewarded based on measurable work, not promises.

Anchored to Kaspa

Kaspa’s BlockDAG enables high-frequency commitments, low-latency settlement and a clear security model for compute verification.

Built for real workloads

From AI inference and simulations to rendering and batch jobs — KASCompute is designed to handle practical, verifiable workloads.

Flow

How KASCompute works

A clean separation of concerns: clients submit jobs, nodes execute, Kaspa finalizes commitments.

Task submission
Clients submit compute jobs via an off-chain API, specifying constraints and pricing.
Scheduling & matching
The coordinator matches tasks with suitable GPU/CPU providers based on capacity and reputation.
Isolated execution
Nodes run tasks in sandboxed environments and collect execution traces.
Proof-of-Compute
Traces are reduced into commitments that can be aggregated and verified.
Kaspa anchoring
Commitments are periodically aggregated into Merkle roots and anchored into Kaspa.
Settlement
Once anchored, rewards are released and clients can verify the complete compute path.

Architecture at a glance

L1: Kaspa BlockDAG (roots, settlement)
L2: KASCompute coordinator, PoC controller
Edge: GPU/CPU provider nodes
Clients: dApps, protocols, enterprises

Compute remains off-chain. Trust is enforced on-chain through anchoring and verifiable proofs.

90% PoC emission

VERIFICATION

Proof-of-Compute (PoC)

KASCompute separates execution from settlement: nodes execute workloads off-chain while proofs and rewards are enforced on Kaspa’s BlockDAG.

Execution traces generate commitments.
Commitments aggregate into Merkle roots.
Roots are anchored on Kaspa, forming compute epochs.
Clients can audit tasks from Kaspa root → trace.

Client task

Payload, constraints, metadata submitted to KASCompute.

Coordinator

Matches tasks to nodes based on load, capacity and pricing.

Execution nodes

Isolated runtimes execute workloads and emit traces.

PoC controller

Reduces traces into commitments and aggregates them.

Kaspa settlement

Merkle roots anchored on Kaspa, defining compute epochs.

Economics

KCT Tokenomics

KCT is the native asset of the KASCompute network: it compensates providers, secures anchoring and captures value from long-term usage.

Supply & emission

Total supply: 10 B KCT
PoC mining: 9 B KCT
Treasury & ecosystem: 1 B KCT
Emission horizon: ~14 years
Decay: ~1% monthly reduction

Value flow

Clients pay for compute in KCT or bridged assets.
Providers earn KCT for verifiable PoC contributions.
Treasury supports development, audits and ecosystem grants.
Post-mining, value shifts to fee capture and staking models.

Distribution snapshot

90/10

Proof-of-Compute emission — 90%
Treasury & ecosystem — 10%

Execution

Roadmap

High-level milestones aligned with the KASCompute whitepaper for 2025–2026.

2025 Testnet & PoC foundation

Core Proof-of-Compute engine, node prototype, Kaspa anchoring pipeline and public testnet dashboard.

2026 Network expansion

Iterative improvements to node software, expanded participation, refined emission parameters and deeper Kaspa integration.

For a detailed breakdown beyond these milestones, refer to the official whitepaper.

Live metrics

Live testnet dashboard

Monitor active nodes, PoC rewards and emission curves in real time.

KASCompute Testnet

Specification

Whitepaper

The canonical reference for KASCompute: PoC model, token emission, security assumptions and roadmap.

Formal definition of Proof-of-Compute.
Emission schedule and post-mining value model.
Kaspa anchoring design and threat model.
Network evolution and ecosystem plans.

Open whitepaper (PDF)

Aligned with Kaspa

As Kaspa evolves (e.g. quantum-safe primitives, programmability), KASCompute is positioned to inherit and extend those guarantees at the compute layer.

Community