01 · KRONEX NETWORK

Infrastructure without boundaries.

Kronex is a privacy-first programmable network for compute, liquidity and digital infrastructure.

A decentralized marketplace where users, applications and autonomous agents can access computational resources, financial services and infrastructure through a single open network.

PRIVATE BY DESIGN · OPEN BY DEFAULT · PROGRAMMABLE FOR ANYONE


TESTNET IS LIVE · MINING WORKS TODAY — kHEAVYHASH + MERGED SHA256d · SCRYPT · KAWPOW · EQUIHASH · THE MARKETPLACE IS IN DEVELOPMENT

Compute providers Privacy & verification Financial providers Network nodes

Mining is live Testnet

The chain is mined today. Two ways, both at once.

kHeavyHash seals every block. Work already done for four other proof-of-work chains can commit to Kronex as well and be paid for it — without giving up the parent-chain reward.

Direct · kHeavyHash

Same pre-image as Kaspa

GMiner, lolMiner, BzMiner, IceRiver and Goldshell hardware mine Kronex with no firmware change. Only the source of work differs.

  • kHeavyHash
  • krnx_getWork
  • krnx_submitWork

Merged · four parent chains

Paid on top of the parent reward

Work for Bitcoin Cash, Litecoin, Ravencoin or Zcash commits to Kronex through a workshare — a self-verifying proof bound into the block's pre-image.

  • SHA256d
  • Scrypt
  • KawPoW
  • Equihash

Pools · four methods

Your miners need no changes

An ordinary parent-chain header from a Kronex node; a share back; a KRNX reward to the address the pool names. Clients in Go, Rust, Node.js and Python.

  • krnx_getBlockTemplate
  • krnx_submit…Block

Mining on KronexPool integration ↗

02 · WHAT IS KRONEX?

A blockchain for the infrastructure economy

Kronex is a decentralized blockchain designed to coordinate markets for digital infrastructure.

Instead of limiting blockchain utility to transferring tokens, Kronex is designed to connect users who need resources and services with independent providers capable of delivering them.

The network can coordinate

  • AI computation
  • GPU resources
  • decentralized gateways
  • privacy services
  • liquidity
  • escrow
  • OTC execution
  • market making
  • Proof-of-Work hashpower
  • future digital resource markets
  1. Discovery find providers able to deliver the resource
  2. Order state the requirement, price and deadline
  3. Execution the provider performs the work
  4. Verification delivery is measured, not assumed
  5. Settlement payment follows verified delivery

Fig. 01 — the common layer

Kronex provides the common layer for these five steps.

03 · OUR NORTH STAR

Make digital infrastructure open, private and programmable.

Computational resources, liquidity and infrastructure are increasingly important components of the digital economy.

Today they remain fragmented across centralized clouds, exchanges, mining marketplaces, brokers, payment processors and specialized service providers.

Kronex aims to create an open coordination layer where these resources can be accessed directly through programmable markets.

Turn infrastructure into an open market.

Today
cloud
exchange
mining marketplace
broker
payment processor
specialist provider
Kronex
cloudexchangemining marketplacebrokerpayment processorspecialist provider
Kronex coordination layer
Fig. 02 — fragmented / coordinated

04 · THE THREE PILLARSplanned

Privacy. Compute. Financial infrastructure.

Privacy

Digital infrastructure should not require exposing every transaction, business relationship or computational request to the world.

Kronex is designed around privacy as a fundamental network capability.

Planned privacy infrastructure:

  • private transactions
  • confidential orders
  • private RFQ markets
  • selective disclosure
  • private provider interactions
  • confidential business settlement
  • privacy-preserving proofs
  • zero-knowledge technology

Users should be able to choose what information becomes public and what remains private.

Privacy layer →

Compute

Kronex creates an open marketplace for computational resources.

Applications, companies, developers and autonomous agents will be able to request computing capacity from independent providers.

Compute markets may include:

  • AI inference
  • GPU computation
  • AI agent workloads
  • model execution
  • rendering
  • ZK proving
  • batch processing
  • Proof-of-Work computation
  • specialized computing hardware

Providers monetize unused or dedicated hardware. Buyers access compute without relying on a single centralized infrastructure operator.

ORDER SELECTED Compute markets →

Financial infrastructure

Infrastructure markets require more than payments.

Kronex is designed to support decentralized financial service providers directly within its economy.

Provider markets include:

  • Escrow Providers
  • OTC Providers
  • Market Makers
  • liquidity providers
  • settlement providers
  • payment routing
  • asset conversion

These services allow independent participants to transact without requiring one centralized intermediary.

05 · WHY KRONEX?

More than transactions

Traditional blockchains primarily coordinate ownership and token transfers. Kronex expands this model by coordinating services and resources.

Programmable
Applications can request infrastructure programmatically.
Private
Users can access confidential transaction and service layers.
Open
Anyone can participate as a buyer, provider or developer.
Provider-driven
Infrastructure comes from independent network participants.
Multi-market
Different resource and financial markets can operate over the same settlement network.
Verifiable
Where possible, services can be measured and settled based on actual delivery.
Composable
Compute, liquidity, escrow and settlement can interact within a single transaction flow.
Fig. 03 — composability

06 · THE KRONEX MARKETPLACE

One network. Multiple markets.

Kronex is designed as an infrastructure marketplace rather than a marketplace for one specific resource. The network can support multiple specialized markets operating simultaneously.

AI Compute Market

Request computational resources for AI workloads.

Possible workloads:

  • inference
  • agent execution
  • model serving
  • batch processing
  • embeddings
  • data processing
  • specialized GPU tasks

Users define the workload and required resources. Providers compete to execute it.

07 · CONVERT ASSETS INTO RESOURCES

From digital assets directly to infrastructure.

One of the long-term Kronex objectives is to remove unnecessary steps between holding an asset and purchasing a digital resource.

Today
Asset
Exchange
Another asset
Marketplace
Provider
Liquidity routing
Kronex
Asset
Resource
Fig. 04 — today / Kronex
  • USDT → GPU compute
  • BTC → AI inference
  • KRNX → ZK proving
  • SOL → hashpower

Supported liquidity providers handle conversion while the user interacts with a single order.

08 · PROGRAMMABLE ORDERS

Infrastructure as an on-chain primitive.

Orders can contain execution requirements instead of simply transferring value. This transforms an ordinary transaction into a programmable infrastructure request.

ILLUSTRATIVE ORDER — SCHEMA NOT FINAL

09 · AI + KRONEX

Infrastructure for autonomous software

AI agents increasingly need access to external resources: computation, APIs, payments, data, storage, liquidity and execution infrastructure. Kronex aims to make these resources accessible through programmable markets.

discover infrastructure
request a quote
fund an order
purchase computation
verify execution
pay providers
repeat

Fig. 05 — autonomous order cycle

Illustrative trace

> agent.discover({ resource: "ai-inference", region: "eu" }) 3 providers matched > agent.quote(provider: 0x2a91…8e03, max: 12.00 USDT) quote 9.40 USDT · deadline 15m > agent.fund(escrow) locked 9.40 USDT > agent.execute() workload dispatched > agent.verify(receipt) receipt valid > agent.settle() provider paid · 9.40 USDT > loop()

Infrastructure that software can buy.

Kronex markets are designed to be usable not only by people but by applications and autonomous agents. No manual negotiation is required. This creates an economy where software can become an active participant rather than merely a user-controlled interface.

AI agents & M2M →

10 · PRIVACY LAYERplanned

Privacy is infrastructure.

Public blockchains expose an enormous amount of information. For individuals this can reveal financial activity.

For companies it can reveal

  • suppliers
  • customers
  • transaction sizes
  • infrastructure spending
  • trading strategies
  • business relationships
  • computational workloads

Standard transparent blockchain activity.

Illustrative order — schema not final
buyer 0x7f4c…c419
provider 0x2a91…8e03
resource ai-inference
quantity 1,000,000 tokens
amount 9.40 USDT
settlement escrow · on verified delivery
Fig. 06 — disclosure modes

The objective is not anonymity at all costs. The objective is user-controlled information disclosure.

Markets do not need to expose every order. Kronex plans to explore confidential infrastructure markets where information such as order size, requested resource, offered price, counterparty and settlement amount does not necessarily need to become publicly visible.

Potential applications Research

  • private AI compute orders
  • private OTC trades
  • private liquidity requests
  • private infrastructure contracts
  • confidential enterprise transactions

Privacy layer →

11 · FINANCIAL PROVIDERSplanned

Liquidity, escrow and execution as network services.

Escrow Providers

Settlement without blind trust.

Two unknown parties should not need to trust each other before doing business. Kronex plans to support independent Escrow Providers capable of securing transactions between buyers and service providers. Funds can be locked and released according to predefined settlement conditions.

Possible applications

  • compute orders
  • infrastructure contracts
  • OTC transactions
  • large resource purchases
  • milestone-based payments
Buyer
Locked funds
Condition check
Provider
Fig. 07 — escrowed settlement

Funds are locked before execution and released against the condition, with a milestone variant for staged delivery.

Market Maker Providers

Liquidity as a network service.

Market Makers can provide liquidity between assets and Kronex resource markets. This makes it possible for users to access infrastructure without manually acquiring a specific settlement asset first. Liquidity itself becomes a provider market.

Market Makers compete based on

  • price
  • spread
  • depth
  • availability
  • execution quality
Asset A Compute order Market makers Liquidity routing
Fig. 08 — liquidity routing

OTC Providers

Infrastructure for large transactions.

Large orders often require different execution mechanisms from ordinary public markets. Escrow and privacy layers can be combined with OTC execution.

Kronex plans to support OTC Providers for

  • large asset conversions
  • large compute agreements
  • private RFQs
  • institutional infrastructure contracts
  • large hashpower orders
  • negotiated execution
Large order Settlement Public market OTC provider
Fig. 09 — negotiated execution

12 · GATEWAY NETWORKplanned

Connect Kronex to infrastructure beyond Kronex.

Gateways provide bridges between the Kronex marketplace and external infrastructure.

A Gateway Provider may

  1. 01accept Kronex orders
  2. 02translate them into external protocols
  3. 03route workloads
  4. 04monitor execution
  5. 05measure delivery
  6. 06return results
  7. 07generate execution receipts
Kronex AI infrastructure GPU clusters mining protocols external APIs storage networks RPC providers other blockchains
Fig. 10 — gateway topology

Gateways allow Kronex to coordinate resources without requiring every external protocol to become part of Kronex consensus.

13 · VERIFIED SERVICESresearch

Pay for what was delivered.

A decentralized infrastructure marketplace requires more than matching buyers and sellers. The network also needs mechanisms for determining what actually happened. Kronex aims to develop verification mechanisms appropriate to each service market.

MarketSettled against
Computecompleted workload / verified result
Hashpoweraccepted computational work
Storageproof of stored data
Gatewayverified request delivery
AIexecution receipt / result verification

Verified Illustrative

order          0x9c31…a70f
provider       0x2a91…8e03
work delivered 1,000,000 tokens · ai-inference
proof          execution-receipt · verified
settled        9.40 USDT

Fig. 11 — execution receipt

The verification model can differ by market while settlement remains coordinated through Kronex.

14 · PROVIDER ECONOMY

Anyone can provide infrastructure.

The Kronex economy is built around specialized providers. Additional provider classes can be introduced as the network expands.

Compute Provider
Provides CPU, GPU or specialized computation.
AI Provider
Provides models, inference or AI execution.
Hashpower Provider
Provides Proof-of-Work computation.
Gateway Provider
Connects Kronex orders with external infrastructure.
Escrow Provider
Secures transactions.
Market Maker
Provides liquidity.
OTC Provider
Executes large or specialized transactions.

Performance becomes measurable.

Price alone should not determine which provider receives an order. The Kronex marketplace can build provider reputation using measurable information.

  • uptime
  • successful executions
  • response time
  • delivery accuracy
  • dispute history
  • collateral
  • order volume
  • execution quality

Provider explorer No data — marketplace not built

ProviderClassRegionUptimeExecutionsMedian responseCollateralDisputesReputation

Become a provider →

Compete on service, not access.

Kronex aims to avoid permanently privileged infrastructure operators. Providers should compete according to measurable characteristics.

  • Price
  • Performance
  • Reliability
  • Reputation
  • Collateral
  • Latency
  • Privacy
  • Capacity

A competitive provider economy makes the network stronger as participation grows.

Become a ProviderProvider economics →

15 · BUILT FOR DEVELOPERS

Build markets, applications and agents on Kronex.

Developers should be able to integrate Kronex infrastructure through open tools.

SDK — PLANNED · API SHAPE ILLUSTRATIVE
import { Kronex } from "@kronex/sdk";

const kronex = new Kronex({ rpc: "https://rpc.kronex.network" });

const order = await kronex.orders.create({
  resource:     "ai-inference",
  quantity:     { units: 1_000_000, metric: "tokens" },
  maxPrice:     { amount: "12.00", asset: "USDT" },
  deadline:     "15m",
  privacy:      "protected",
  verification: "execution-receipt",
  settlement:   { type: "escrow", release: "on-verified-delivery" },
});

for await (const event of order.stream()) {
  console.log(event.type, event.data);
}

Full RPC reference ↗

Planned developer infrastructure

  • SDK
  • APIs
  • RPC
  • provider APIs
  • order APIs
  • marketplace APIs
  • payment APIs
  • gateway framework
  • documentation
  • examples
  • open-source libraries

Possible applications

  • AI platforms
  • wallets
  • compute marketplaces
  • automated trading infrastructure
  • cloud applications
  • mining services
  • payment systems
  • autonomous agents

Build on Kronex

16 · NETWORK STATISTICS

Kronex Network

Once mainnet is operating, this section shows live metrics — actual network data rather than static marketing numbers.

Running on testnetData source — explorer-testnet.kronex.network · rpc.kronex.network · every figure checkable on /stats

  • Block height

    testnet
  • Average block time

    testnet
  • Transactions

    testnet
  • Addresses

    testnet
  • Network hashrate

    testnet · derived
  • KRNX supply

    source pending
  • Active nodes

    source pending
  • Active providers

    awaiting marketplace
  • Compute capacity

    awaiting marketplace
  • Marketplace volume

    awaiting marketplace
  • Active orders

    awaiting marketplace

All network statistics

17 · ROADMAP

Nine phases, in order.

Testnet Planned Research Encoded by dot shape and border, never by colour

  1. Phase 01

    Network Foundation

    Testnet

    establish a reliable decentralized settlement layer

    • blockchain core
    • nodes
    • transactions
    • network APIs
    • developer tooling
    • explorer
    • wallet
    Solid border — running on testnet · wallet is unmarked because it does not exist
  2. Phase 02

    Programmable Marketplace

    planned

    allow resources and services to be traded through Kronex

  3. Phase 03

    Privacy

    planned

    make privacy a native capability of the network

  4. Phase 04

    Compute & AI Market

    planned

    create an open marketplace for AI and computational infrastructure

  5. Phase 05

    Financial Provider Network

    planned

    enable independent financial services inside the Kronex economy

  6. Phase 06

    Gateway Network

    planned

    coordinate infrastructure across multiple networks and protocols

  7. Phase 07

    Hashpower Market

    planned

    create a programmable market for verifiable Proof-of-Work computation

  8. Phase 08

    Machine Economy

    planned

    allow software to independently purchase and provide digital infrastructure

  9. Phase 09

    Open Infrastructure Economy

    research

    develop Kronex into an open marketplace for digital infrastructure

Full roadmap →

18 · OPEN NETWORK

One network. Many participants.

Users
Access resources and services.
Developers
Build applications and integrations.
AI Agents
Programmatically consume infrastructure.
Infrastructure Providers
Supply compute and other resources.
Financial Providers
Supply liquidity, escrow and OTC execution.
Gateway Operators
Connect external infrastructure.
Researchers
Develop new privacy, verification and market mechanisms.

An open protocol should have an open evolution process.

Protocol development uses Kronex Improvement Proposals — KIPs. Community discussion and technical review precede major protocol changes.

  • consensus changes
  • privacy upgrades
  • marketplace protocols
  • token economics
  • provider standards
  • new resource markets
  • APIs
  • governance changes

The precise governance architecture should evolve alongside the network rather than being prematurely centralized into token voting.

KIP index — 0 published

Governance & KIPs →

19 · CLOSING

Infrastructure should be open.

  • Compute should be accessible.
  • Markets should be programmable.
  • Transactions should be private when users need them to be.
  • Providers should compete.
  • Software should be able to transact.

Kronex is building the network that connects them.

Explore Kronex Build on Kronex