Experimental testnet · Test tokens have no monetary value

A Layer 1 for decentralized infrastructure, designed around real demand.

Sakviti is a base network designed to help developers, operators, and users build and use decentralized infrastructure with clear demand, fees, and proof.

See the proof applications Read the development update

The base network: A working core, built in Rust
Your window in: The Nexus app, running in your browser
Proof today: The Nexus gateway and reference applications in development

Nexus dashboard showing network, wallet, messaging, and application entry points — A real Nexus screen from the development build, showing the gateway into the base network, services, and applications.

Why the base network exists

The fee economy connects useful work to infrastructure capacity.

Material network actions carry protocol fees. The design aims to make demand visible in the economics of the shared network, while staying honest about the early phase: low activity can mean near-zero operator income.

People pay for useful actions

Transfers, storage, processing, state keep-alive, and resource uploads all have protocol fee paths.

Providers follow protocol rules

Useful-work providers receive defined compensation from the fee flow. The design does not promise income when demand is low.

Demand shapes incentives

Higher demand can create stronger fee flow and better incentives for the infrastructure capacity that people use.

See the current fee-flow boundary

The current reference maps fees to block producers and shared-record creators, routing pools, escrow, and a launch burn target. Any unburned remainder is recycled to escrow. This is implemented fee behavior, not a promise of profitability.

Layered architecture

Four parts, one infrastructure stack.

Sakviti separates the base network from the services and applications that use it. Each layer has a clear job, and each service is shown at its current testnet boundary rather than as a finished promise.

01Base networkShared agreement, shared record, and fee rulesCore running, hardening continues
02Infrastructure servicesMessaging, identity, payments, and storageMessaging first slice, identity read-only, payment paths active, storage foundation not production-ready
03Hydra computeCompute, memory, storage, and networking as a serviceActive service, production workload limits still under validation
04User-facing applicationsNexus and reference apps that make the stack usableCurrent testnet and reference applications

Users Applications

Nexus is the current gateway. Coo Lite, Wardgrove, and Leaderboard are reference applications in development.

Services Decentralized infrastructure

Messaging, identity, payments, storage, and Hydra each serve a bounded role.

Base Sakviti network

The shared record and fee economy provide the common foundation.

Hydra infrastructure service

Build applications on decentralized resources.

Hydra is an infrastructure service built over Sakviti. It provides compute, memory, storage or disk, and networking through a developer-oriented interface.

One service in the ecosystem

Hydra is not the consensus layer. The base network keeps the shared record; Hydra handles suitable resource work.

Use it when the workload fits

Third-party applications can use Hydra when their workloads are suitable for decentralized execution.

Limits stay visible

Not every cloud workload should or can run efficiently on Hydra. Capacity, cost, and service readiness remain validation goals.

Applications and Nexus proof

Applications prove the infrastructure stack in use.

Nexus is the user and developer gateway. Coo Lite, Wardgrove, and Leaderboard are reference applications in development that demonstrate the stack without defining the category.

Nexus wallet view showing balance, address, and application permission controls — Real Nexus screen, wallet and permission view

Nexus gateway

Enter and inspect

Onboard, review permissions, use services, and inspect the evidence available from the testnet.

Nexus Messages view showing a conversation list and route details — Real Nexus screen, messaging service view

Coo Lite

Read a focused app

Coo Lite is a public-text application in development. Its testnet plan keeps posting bounded to an invited group; reading is open to everyone.

Nexus App Store view showing service search and application discovery status — Real Nexus screen, application directory

Reference workloads

Wardgrove and Leaderboard

Wardgrove tests durable application state. Leaderboard shows a bounded result-proof flow. Both remain proof surfaces.

Technical evidence and current status

A working core, being validated before it opens up.

These are evidence-led checkpoints, not blanket claims about sustainability, scale, or security. Public access comes after the relevant validation work is complete.

Read the latest development evidence

Working nowRunning in development

The network's core engine, built in Rust
The shared record of everything that happens
Your wallet, messages, and apps in Nexus
Apps and encrypted messages moving over the network

Still validatingBefore wider access

Recovering cleanly if parts of the network fail
Keeping browser and identity flows secure
Handling storage, assets, and day-to-day operations
Testing scale and the fee economy under demand

Opening upGradual, not all at once

Public access follows security, scale, and reliability evidence, step by step, not overnight.

Verified progress

Development and network updates.

Engineering changes, platform status, and technical deep dives from the Sakviti team.