UniNet
Contact

Architecture

One network, seven layers.

Identity, private networking, execution, assets, payments and governance - as layers of one network, not six vendor relationships.

The substrate

Everything resolves against one record.

Identity, network and execution share the state layer that holds assets, payments and governance.

UniNet resolves into three planes: Identity, containing identity, agents and roles; Network, containing UNP, routing and domains; and Execution, containing containers, contracts and compute. All three planes resolve against a single shared sovereign state layer, which carries assets, payments and governance.

The layers

Seven layers, ordered by dependency.

Each layer builds only on the ones before it.

  1. 01NexusThe root registry every identity, chain, operator and service resolves against.Root layerAvailableDocs
  2. 02UniNet IdentityA key the entity holds, not a row in a provider database. Agents name a supervising personal identity.NexusAvailableDocs
  3. 03UNPAn address decoupled from the machine hosting it. A routing design, not an anonymity network.Nexus · IdentityAvailableDocs
  4. 04UniNet ChainsIsolated environments with their own ownership, state and limits. Isolation is container-level at most.Nexus · Identity · UNPAvailableDocs
  5. 05UniNet ComputeCPU, memory and storage capacity, inspectable across nodes and reserved atomically. Not GPU-aware.Nexus · Identity · UNPAvailableDocs
  6. 06UniNet WalletWallets, sub-wallets and signed transfers as network functions. External bridging is incomplete.Nexus · IdentityAvailableDocs
  7. 07UniNet GovernanceOwnership, treasury and authenticated voting, encoded as network state.Nexus · Identity · Wallet · ChainsAvailableDocs

Private networking

A visit crosses relays, not a direct line.

Each relay unlocks one layer and learns only the next stop. The service never sees the visitor's IP, and a static site can be hosted so that no record names its machine.

See it step by step

Target architecture

Where the layers are going.

A target, not the deployed network. GPU-aware scheduling does not exist in this form yet.

A target architecture, not a description of the deployed network. At the top, a sovereign agent layer - one state, not three directories - holding identity, authority and economy. Under it UNP, the private network, which addresses services independently of the machines serving them. Under UNP sit three resource classes - compute, storage and services - drawing on a tier of DePIN providers - datacenters, GPU owners and devices - that feed one pool every resource draws from. The provider tier is still to come, so it is drawn as outlines, and GPU-aware scheduling is not part of capacity discovery today. Traffic is drawn only from the agent layer down into UNP for that reason.

Authority

Permission is enforceable by the network.

A right is signed, scoped and dated - and the chain from holder to holder stays inspectable.

01
Delegation

Conferred by the delegator’s signature, not by a log entry.

02
Scope restriction

A grant is a subset of what the delegator holds. It narrows, never widens.

03
Expiry

Every grant has a validity window. Unrenewed authority lapses.

04
Cascading revocation

Revoke once, at the source. Everything derived from it goes too.

The same four-tier authority chain drawn twice. First, delegation: a human identity, which holds the rights it grants, delegates to an agent identity - the grant is signed and scoped to specific rights, with an expiry. The agent identity delegates again to a task grant, narrower in scope and with a shorter expiry, and the task grant fans out to three derived actions: reserve compute, send payload and settle payment. Second, the revocation cascade: the same chain with the grant from the human identity to the agent identity cut. The human identity keeps its rights; everything derived from the withdrawn grant - the agent identity's authority, the task grant, and all three actions - is drawn as an outline and struck through, because it stops resolving. One act at the point of delegation withdraws the whole branch, rather than an inventory of credentials issued downstream.

Read the authority docs

Read next

Check the claim.

What is built, and why it is built this way.

What works todayRead the manifesto