You hold your identity
Your identity comes from a wallet key you keep, not from an account an application issues to you.
In Nexus today: wallet-derived identity
Web3 infrastructure designed to serve everyone, for generations.
Sakviti is a Layer 1 network where people hold their own digital identity, decide what applications may do, and can check what happened for themselves. Fees from real use, not new token issuance, pay the operators who run it.
- Design target
- 10B+ participantsThe scale every core design is reviewed against
- Design target
- 100-year horizonFor verifiable history, upgrades, and economics
- Design direction
- Paid for by useFixed supply, with no recurring block subsidy
- Current stage
- TestnetNext milestone: the public testnet
01 Why it matters
Your digital life shouldn't depend on one company's decisions.
Accounts get locked, purchases disappear, and services shut down, because a few companies run the infrastructure most people use. Sakviti is shared infrastructure with public rules, where the people using the network hold their own keys.
Read our essays on why this mattersApplications ask first
Apps request permissions limited by service, action, spending, and time. You can review every grant and revoke it at any time.
In Nexus today: grant review and revocation
Verify instead of trust
Network actions settle on a shared record that participants can check for themselves, instead of trusting one operator's database.
In the testnet today: the shared record
02 How it works
One shared base, with services and apps built above it.
Sakviti separates the network everyone agrees on from the services and applications that use it. Each layer has one job. Here is where each one stands on the testnet.
-
Layer 4
Applications
Nexus, the gateway, plus reference apps that make the stack usable.
Nexus and reference apps in development
-
Layer 3
Hydra
Compute, memory, storage, and networking for applications built on decentralized resources.
Running; production workloads in testing
-
Layer 2
Infrastructure services
Messaging, identity, payments, and storage, each with a bounded role.
Messaging and payments running; identity and storage in progress
-
Layer 1
Base network
The shared record everyone agrees on, and the fee rules that pay for it.
Core running on the testnet
03 Economy
Paid for by use, not by new tokens.
Material network actions carry protocol fees, and protocol rules route those fees to the operators who provide the capacity people use. Total supply is fixed, with no recurring block subsidy, so the network grows on real demand.
-
Use
People pay for useful actions
Transfers, storage, processing, state keep-alive, and resource uploads each have a protocol fee path.
-
Operate
Operators are paid by rule
Useful-work providers receive defined compensation from the fee flow, set by the protocol rather than negotiated.
-
Grow
Demand shapes capacity
More real use brings more fee flow, and more reason to add the capacity people rely on.
Earned, not issued
Operators are paid from what people spend on real use, not from new tokens, so the network's capacity follows its usefulness. On the testnet, fees are paid in test tokens that have no monetary value.
How fees are split today
Fees go to block producers and shared-record creators, routing pools, escrow, and a launch burn target. Any unburned remainder returns to escrow.
04 Global scale
Designed for the whole world, and for the long run.
Every core protocol, consensus, routing, storage, and economic design is reviewed against two assumptions at once. The goal is to reject designs that only work while a network is small, young, or centrally run.
10,000,000,000+participants Sakviti may one day serve
100+ yearsof staying live, relevant, and independently verifiable
-
Bounded local work
Validation, routing, and queries avoid global scans and network-wide broadcasts, so each node's work stays bounded as participation grows.
-
History that stays provable
Live nodes may prune, while critical history keeps an archive, proof, or checkpoint path for future audits and disputes.
-
Versioned from the start
Wire formats, state, and service versions carry explicit versioning and migration plans, so the network can evolve without a coordinated restart.
-
Replaceable cryptography
Keys, signatures, and hashes need rotation paths, including migration to post-quantum schemes, before they become urgent.
-
Economics measured in decades
Fees, burns, rewards, and collateral are evaluated across decades and longer, not only under launch conditions.
-
Survives turnover and outages
Designs must keep working as operators, institutions, and jurisdictions change, and define how regions recover after long outages.
05 Nexus
Nexus is the way in.
Nexus runs in the browser. It is where people create a test wallet, see the identity applications use, open apps, and review or revoke what those apps may do. This is the current build.
-
Nexus gateway
Enter and inspect
Onboard, review permissions, use services, and inspect the evidence available from the testnet.
-
Coo Lite
A focused public-text app
Anyone can read. During the testnet, posting opens to an invited group first.
-
Reference workloads
Wardgrove and Leaderboard
Wardgrove runs durable application state on the network. Leaderboard checks a certified result from another app.
06 Status
Where Sakviti stands today.
Every milestone ships with its evidence, and access opens as each one is proven.
Read the latest update-
Now
Testnet
Working today
- 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
-
Next
Public testnet
In progress
- 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
-
Then
Wider access
Opening in stages
Each stage opens once its security, scale, and reliability work is proven.
07 Updates
Follow the build.
Get every development update.
Shipped changes, verification results, and progress toward the public testnet, posted on the blog and on X.