Protocol framework for peer-to-peer networks. KIP defines the vocabulary and mechanisms that allow any network to describe itself and any node to understand what a network expects.
KIP does not define how data is exchanged, how peers connect, or what security model is used. Those are extensions.
| KIP | Name | Status | Description |
|---|---|---|---|
| KIP-0001 | Core Protocol | Draft | Nodes, roles, layers, manifests, extensions |
| KIP-0002 | Manifest | Draft | Manifest format, roles, network map |
| KIP-0003 | Extensions | Draft | Extension identification, spec requirements, registry |
| Name | Layer | Roles | Status | Description |
|---|---|---|---|---|
chunk-exchange |
Exchange | peer | Draft | Chunk-based file transfer between peers |
kippit-tracker |
Discovery | tracker, peer | Draft | WebSocket-based peer discovery and signaling |
jwt-auth |
Semantics | tracker, peer | Draft | JWT authentication (ES256) |
aes-encryption |
Semantics | peer | Draft | Data encryption (AES) |
key-delivery |
Semantics | peer, tracker | Draft | Encryption key delivery (API, URL, peer-exchange, manual) |
hls-streaming |
Semantics | peer | Draft | Sequential priority, HLS manifest |
resource-catalog |
Discovery | peer, tracker | Draft | Browseable resource listing |
resource-metadata |
Semantics | peer, tracker | Draft | Per-resource metadata (name, size, type) |
sync |
Semantics | peer | Draft | Multi-node replication with change tracking |
messaging |
Semantics | peer | Draft | Real-time small data |
bt-bridge |
Exchange | peer | Draft | BitTorrent wire protocol compatibility |
bt-tracker |
Discovery | tracker | Draft | BitTorrent tracker protocol (announce, scrape) |
manifest-visibility |
Semantics | tracker, peer | Draft | Controls what appears in public manifest |
endpoint-discovery |
Discovery | peer, tracker | Draft | Endpoint map (sitemap-like) |
webrtc-signaling |
Connection | tracker, peer | Draft | WebRTC SDP/ICE exchange |
mdns-discovery |
Discovery | peer | Draft | LAN zero-config discovery |
| Name | Layer | Roles | Description |
|---|---|---|---|
lease-agreement |
Semantics | peer, tracker | Terms of hosting between peers (storage, duration, SLA) |
metered-usage |
Semantics | peer, tracker | Bandwidth and storage accounting |
quota |
Semantics | tracker | Resource limits per peer |
reputation |
Semantics | tracker | Peer reliability scoring |
billing |
Semantics | tracker | Payment for hosting/bandwidth |
moderation |
Semantics | tracker | Content policy enforcement |
governance |
Semantics | peer, tracker | Democratic/hybrid voting and rule negotiation |
External extensions use repository paths (e.g. github.com/someone/cool-extension). See KIP-0003.
Transport specs define how bytes flow between nodes. Each interface in a manifest declares its transport(s).
| Name | Type | Stream | Reliable | NAT | Browser | Spec |
|---|---|---|---|---|---|---|
| TCP | tcp |
stream | yes | no | no | transport-tcp.md |
| UDP | udp |
datagram | no | partial | no | transport-udp.md |
| uTP | utp |
stream | yes | partial | no | transport-utp.md |
| HTTP | http |
request-response | yes | yes | yes | transport-http.md |
| WebSocket | websocket |
message | yes | yes | yes | transport-websocket.md |
| WebRTC | webrtc |
message/stream | configurable | yes | yes | transport-webrtc.md |
| Unix socket | unix |
stream | yes | N/A | no | transport-unix.md |
- protocol-layer-model.md — 5-layer model with roles (design document)
- tracker-manifest-authority.md — federation governance model (design document)
| Status | Meaning |
|---|---|
| Draft | Work in progress, may change fundamentally |
| Review | Complete, requires review |
| Accepted | Approved, ready for implementation |
| Final | Implemented and tested |
KIP specs are written in Markdown. Each KIP is a self-contained document. To propose a new KIP, open an issue or PR.