✺ nety · decentralized social

What nety is

identity

Own your graph

Your identity is an Ed25519 keypair in an encrypted keystore — not a row in someone's database. Posts, profiles and follows are signed and yours to carry.

try it

your keystore

⚷ generate keypair

peerId12D3KooWh9c…Hx7q

pubkeyed25519:9f3a…b1c4

The private key is sealed in your local keystore — it never leaves the device.

✍ sign “gm from the mesh”

sig3045022100…a7

✓ verifiable by any peer — no server needed

interop

Connect any network

A peer-to-peer social protocol over libp2p (gossipsub + Kademlia) moves posts and follows between peers. A GraphQL gateway lets apps speak to the mesh.

try it

peer A · you

“gm from the mesh”

peer B

↳ gm from the mesh

peer C

↳ gm from the mesh

📡 broadcast over gossipsub

No server in the middle — the post gossips peer-to-peer until the whole mesh has it.

cooperative

Shared resources

Nodes offer compute, storage and AI to each other. A Web of Trust plus CRDT reputation decides who to rely on — no central operator required.

try it

⚙ compute 💾 storage ✦ ai

your node offers 8 vCPU · 16 GB RAM 240 GB · IPFS-pinned RTX 4090 · 24 GB VRAM

→ match a job to the network

scheduler picked a peer · trust path you → alice → bob ✓ · reputation 0.92

Stack at a glance

Rust libp2p Wasmtime · WASM IPFS · S3 · Hybrid GraphQL · axum Ed25519 · ChaCha20 CRDT reputation Web of Trust

Where it's at

nety is alive and growing — the core networking, storage and runtime work today; the social gateway and trust layers are landing phase by phase. Here's the honest picture.

F0Bootstrapworkspace, daemon, CLIdone

F1Networking + discoverymDNS on LAN + explicit bootstrap peers · NAT traversal pendingpartial

F2Storage layerLocal + IPFS + S3 + Hybrid backendsdone

F3WASM + schedulingWasmtime runner + local scheduler (MVP)done

F4Identity + cryptoEd25519 + keystore + JWT · biometrics pendingpartial

F5GraphQL gatewayschema + auth + playground · in-memory store, no live subscriptions yetpartial

F6ReputationCRDT + gossip · cryptographic signing nextpartial

F7Trust graph2nd-order transitivity + Ed25519 edge verificationpartial

F8Replication + cachehybrid local tiers · cross-node replication pendingpartial

F9Distributed GPUresource sharing for AI workloadsin progress

functional partial / gaps in progress planned

Today vs. the design

Being straight about it: the GraphQL gateway currently keeps feed, profiles and follows in an in-memory store (lost on restart) and doesn't yet talk to the P2P daemon. WebSocket subscriptions are in the schema but not served over the wire. The private-subnet PSK flag is accepted but not enforced at the transport layer yet. The mesh runs; wiring the social gateway into it is the work in flight.