P2P Architecture
Compare Rust P2P approaches for a model package exchange: libp2p, Iroh, BitTorrent-style chunking, DHT discovery, static bootstrap registries, NAT traversal, and signed catalogs.
Rust peer-to-peer tiny model exchange
MiniModel.org
A planned peer-to-peer catalog for checksum-bound tiny model packages that users download, verify, and run locally.
Boundary
MiniModel.org is not a model hosting service and not an inference service. The goal is discovery, peer transfer, checksum verification, license routing, and local import.
- No server-side model execution.
- No hosted runnable model weights from MiniModel.org.
- Every package is identified by checksums and provenance.
- Users choose, download, verify, and run models locally.
Build plan
Roadmap
-
01
Manifest
Define a signed MiniModel manifest for `.slm` packages, source identity, license route, tokenizer/config checksums, eval evidence, and final artifact checksum.
-
02
Verifier
Ship a Rust CLI that verifies package bytes, manifest fields, evidence routes, drift cases, and SLMComposer import readiness before a user trusts a file.
-
03
Catalog
Publish static catalog metadata and signed index snapshots. The catalog routes users to sources and peers without serving model weights.
-
04
Peer App
Build a Rust desktop peer app for discovery, chunk transfer, resume, checksum validation, and local handoff to SLMComposer.
-
05
Browser Handoff
Let verified local `.slm` files open in SLMComposer for browser-local Rust/WASM loading and generation.
Research prompts
Start here
Trust Model
Design checksum-bound manifests for `.slm` files with source SHA, config/tokenizer checksums, license route, eval evidence, quantization, byte count, and final artifact checksum.
Legal Boundary
Recommend UX language, model-card fields, consent flows, takedown handling, and a clear separation between catalog metadata, peer transfer, and local execution.