DLT Network

In development

Menu

Development status

What exists today, and what comes next

DLT Network is in development and is not deployed on devnet or mainnet. Implemented means built, tested and run end to end on a local Solana network. No dates are published.

Capabilities

What the software does

The same capability statement the DLT app shows, with its limits.

  • Provider & node registryOn-chain identity, status and node key versionsImplemented · local network
  • Compute offers & reservationsPrice, capacity and availability read from the marketplace programImplemented · local network
  • USDC escrow & refundsProgram-held escrow; cancellation before expiry, refunds afterImplemented · local network
  • Execution on provider nodesLocal demo agent · isolated CPU containers · one workload programImplemented · limited
  • Proof-of-Compute V1Deterministic recomputation by a single DLT verifierImplemented · limited
  • Challenge, dispute & settlementChallenge window, one dispute per job, single-key resolver, exact payoutImplemented · limited
  • Hardware attestationNot implemented — no TEE or GPU attestation is claimedNot available
  • Indexer, history & reputationPlanned for M7Planned
  • Tokenized capacityPlanned for M9 — non-transferable pilot firstPlanned
  • Public network (devnet / mainnet)Not deployed — this build targets a local development networkNot available

Deployment gates

Before anything goes public

Each step to a public network has its own gate.

  • DevnetRequires a threshold resolver, a devnet build with production challenge windows, and durable artifact retention.Gated
  • Public provider onboardingRequires a provider resource policy and the provider console.Planned
  • MainnetRequires an external audit, penetration test and legal review (M11).Not launched

Roadmap

Built milestone by milestone, with evidence for each

Milestones are completed in order. Each one closes only with tests, on-chain evidence and an independent review where money or security is involved.

  1. M0

    Reproducible foundation

    Monorepo, toolchains, CI and a local Solana validator.

    Complete · local network
  2. M1

    Provider identity + node registry

    Provider onboarding, node keys, rotation and suspension.

    Complete · local network
  3. M2

    Marketplace offer + USDC escrow

    Offers, jobs and program-held escrow.

    Complete · local network
  4. M3

    Real execution agent

    Provider agent runs committed workloads in isolation and signs receipts.

    Complete · local network
  5. M4

    Proof-of-Compute v1

    Signed receipts, challenge nonce and deterministic recomputation.

    Complete · local network
  6. M5

    Settlement + refund

    Challenge window, disputes, exactly-once payout and refunds.

    Complete · local network
  7. M6

    Production-grade web vertical slice

    Buyer app, provider console, explorer and this site.

    In progress
  8. M7

    Indexer + reputation + observability

    Event history, provider reliability metrics, audit trail.

    Planned
  9. M8

    Security hardening

    Threat-model closure, fuzzing, key management, abuse controls.

    Planned
  10. M9

    Tokenized capacity pilot

    Non-transferable capacity credits tied to verified provider capacity.

    Planned
  11. M10

    Devnet release candidate

    Load, failure drills, runbooks and incident response.

    Planned
  12. M11

    External audit + mainnet readiness

    Independent audit, penetration test, legal review, key ceremony.

    Planned

Tokenized capacity (M9) starts as a non-transferable pilot. Settlement today is in USDC, and no DLT token exists.

Read the known limits