Membership and admission ↗
Signed invitations, device-bound proofs, scoped certificates, delegation and revocation.
YuraMesh
A protocol family for a world with memory.
YuraMesh is YuraNetwork’s proposed next-generation protocol architecture: distinct components with explicit responsibilities, designed to connect identity, admission, names, services, data and continuity without collapsing them into one authority.
SPECIFICATION STATUS
YuraMesh v0.4 is a coordination specification. Native v1 remains operational and authoritative. YuraMesh production implementation is not authorized.
PRESENT
OS / Core / Native
YuraNetwork OS, YuraCore and Native provide the current environment, coordination surface and private transport.
→
DIRECTION
YuraMesh
An additive protocol architecture with separate keys, deterministic CBOR and explicit authorization boundaries.
→
ECOSYSTEM
Names / Sites / Data
Anchors, Presence, Vault objects, hosting delegation and future private discovery.
Why it exists
Beyond a route.
Beyond a name.
A private network can provide transport, but it does not by itself prove website ownership, authorize service access, protect object keys or record permanent retirement.
YuraMesh explores those boundaries as an ecosystem. It is additive: Native v1, WireGuard, DNS, HTTPS and existing services remain separate and unchanged.
The protocol family
Distinct responsibilities.
One architectural direction.
Select a component to move from the platform view into its evidence-grounded design notes.
Name and service resolution ↗
Proposed authenticated naming and signed service records for the private .yura environment. The existing resolver is not replaced.
Identity separation ↗
Installation, device/session, membership, owner, hosting and content identities remain distinct.
Persistent site identity ↗
An owner-key-derived identity independent of host, IP, OS, provider or WireGuard address.
Private discovery ↗
Signed Presence and capability records with discovery visibility separated from access authority.
Client-side encrypted objects ↗
Planned encrypted object and owner-backup profiles using reviewed standard primitives; implementation remains gated.
Continuity and recovery ↗
Owner-key rotation, migration, hosting delegation and recovery without a hidden server master key.
Permanent retirement ↗
Signed, checkpointed retirement that prevents later Presence or reactivation records for an Anchor.
Future privacy transport ↗
An authenticated encrypted transport interface and possible multi-relay direction; no anonymity guarantee is claimed.
What is implemented today?
Native v1 remains the operational foundation: account-authenticated device identity, signed challenges, expiring sessions, WireGuard transport, private addressing, private .yura resolution and private HTTPS. A Native admission or WireGuard handshake does not prove YuraMesh membership, ownership or anonymity.
What is specified?
YuraMesh v0.4 defines a separate deterministic-CBOR protocol identifier, Ed25519 signatures, SHA-256 identities, X25519 agreement direction, VEIL membership, Anchor identity, Presence, Vault and Severance concepts. Production implementation is not authorized.
What remains research?
Operational deployment, witness governance, exact recovery thresholds, privacy-preserving Native association and multi-relay transport require further implementation, testing and review.