Mesh Substrate
Shared foundations for your life, your organisation and your systems. Identity says who is involved. Nexus controls disclosure. Communication connects them.
Identity is the starting point. Nostr-based keys identify an account; connections, consent and grants define what a particular interaction may use. Possessing a key alone does not establish every legal right or mandate.
Decide what to share with the public, uplinks, connections or specific people and machines—or keep it private. Nexus governs who may see which context, for what purpose and under which conditions. Permission to read does not grant authority to act.
The apps use different communication patterns. These describe who connects to whom—not who is allowed to see the content, or whether a claim is true.
FLOW 1:1
A direct exchange between two endpoints.
A private conversation or a bilateral request.
Explore the patternRELAY 1:N
One source reaches a chosen audience.
A publication, announcement or update.
Explore the patternAXIOM N:1
Several sources contribute to one receiving point.
Gather evidence while keeping each source visible.
Explore the patternMESH N:N
Peers exchange across a connected network.
Peer discovery, shared updates and adaptive paths.
Explore the patternProtocol designs in development. Permissions are separate; convergence is not consensus, and a drawn connection is not proof of delivery.
Skyzai’s distributed ledger technology, in development. Its design combines adaptive communication and shared event ordering without confusing either with permission to act.
Efficient paths
Peer discovery, gossip and routing information such as latency and reliability help Spectre find useful paths through the mesh. This is a design target, not measured live network performance.
Explore Spectre transportConsistent ordering
Spectre’s agreement layer is intended to establish a consistent order of events. Transport, ordering and authorization remain distinct responsibilities within the network design.
Explore the Layer-1 designRouting optimisation is not a consensus safety guarantee. Spectre’s integration and failure assumptions still require verification. This website does not establish a live mesh, mainnet or settlement network.
Explore SpectreUseful models still need computation. Connections need transport. Durable records need storage. The aim is to make reliable contributions worth sustaining, while keeping permissions and responsibilities clear.
They introduces the intended role of agents, machines and service providers in this noosphere mesh. SKY and ZAI’s economic roles remain research under Distributed Finance—not a live incentive programme.
Run the workloads the noosphere needs. Useful service is incentivised — idling and token-churning are not.
Design research: no provider admission, rewards or live network are offered by this page.
Context: Mesh Substrate. Local guide only. Messages are not sent or saved.