Rust P2P model directory

MiniModel.org

Find every checksum-bound .slm model in the public catalog, see where it came from, and verify whether a consenting peer is currently available before importing it into TinyRustLM.

Public model catalog

P2P models

Current P2P models appear only after Rust validates unexpired outside-network proof. Browse the separate catalog view for models awaiting a proven peer and runtime-only fixtures.

Loading catalog Checking peers Checking share readiness

Loading checksum-bound catalog metadata.

  1. Loading models.

Boundary

MiniModel.org is not a model hosting service and not an inference service. The goal is discovery, external source routing, peer transfer, checksum verification, license routing, and local import.

Build plan

Roadmap

  1. 01

    Manifest

    Define a MiniModel manifest for `.slm` packages, source identity, license route, tokenizer/config checksums, eval evidence, final artifact checksum, and an externally signed payload-hash envelope.

  2. 02

    Verifier

    Use the first Rust CLI to verify package bytes, manifest fields, evidence routes, chunk/Merkle data, drift cases, and TinyRustLM import readiness before a user trusts a file.

  3. 03

    Catalog

    Publish static catalog metadata and signed index snapshots. `write-catalog-entry` validates manifest plus peer-offer proof, and announcement-feed snapshots can bind same-origin peer availability metadata by SHA-256 without hosting model bytes. Inspectors report exact metadata byte counts and SHA-256 values, and reject catalog/feed JSON above 4 MiB before parsing.

  4. 04

    Share Metadata

    Export a local `minimodel.local_slm_share_metadata.v0` bundle from verified `.slm` imports with artifact SHA256, chunk hashes, chunk-list SHA256, Merkle root, and disabled live-transfer flags.

  5. 05

    Peer App

    Use the first direct peer-piece fetch prototype for known consenting HTTP peers, then build toward an optional user-run MiniModel Peer Companion for local identity, piece stores, consent prompts, cache quotas, receipts, receipt ledgers, and TinyRustLM handoff.

  6. 06

    Browser Handoff

    Let verified local `.slm` files open in TinyRustLM for browser-local Rust/WASM loading and generation.

The full working roadmap is tracked in ROADMAP.md.

Source lanes

Model options

Implementation docs

First build layer

Manifest v0

Line-oriented schema for local `.slm` verification, metadata routes, evidence checksums, chunk metadata, and signature fields.

Rust verifier

Implemented local verifier commands for manifest parsing, byte-count drift, checksum drift, chunk/Merkle checks, generated catalog entries, companion-readable peer-share state, direct peer-piece serve/fetch, peer-piece export/reassembly, one-command peer import requests, TinyRustLM compatibility, import receipts, and metadata-only receipt ledgers.

Fixture manifest

Real q8 fixture manifest binding artifact SHA-256, `.slm` checksum, tokenizer checksum, tensor-layout checksum, peer-offer route, chunk-list SHA-256, and Merkle root.

Catalog boundary

Metadata-only catalog rules, checksum-bound announcement feeds, consent gates, legal posture, takedown routes, and ecosystem tradeoff staging.

Peer Companion spec

Roadmap design for a future user-run local companion: source lanes, Rust command contracts, local receipt ledgers, accepted/deferred/rejected intake findings, local state, piece-store rules, consent gates, UI requirements, tests, and completion criteria.

Catalog endpoint

Static metadata entries for local `.slm` imports, checksum verification, and TinyRustLM browser handoff without hosted model bytes.

Availability feed

Checksum-bound peer-source metadata feed. The current public feed is empty, so it checks availability without making any model P2P-ready.

Share metadata example

Example local bundle and peer-offer proof for a verified `.slm` with catalog-entry candidate, chunk hashes, and live transfer explicitly disabled.

Generated catalog entry

Real fixture catalog metadata written by `write-catalog-entry` from an admitted manifest plus peer-offer proof, with no hosted model bytes.

Peer offer example

Rust-generated text proof binding an admitted `.slm` to artifact SHA-256, chunk SHA-256 rows, and a Merkle root while transfer remains disabled.

Peer import request

Example TinyRustLM request JSON consumed by `minimodel import-peer-request` after a user supplies a consenting known peer URL.

Companion state

`write-peer-companion-state`, `write-peer-companion-inventory`, and `write-peer-contact-book` validate prepared-share state, receipt-ledger evidence, quota metadata, and reviewed peer contacts for future peer companion UI without embedding model bytes; duplicate contact endpoints are rejected before display.

Research prompts

Start here

P2P Architecture

Compare Rust P2P approaches for a model package exchange: direct known-peer HTTP now, protected TinyRustLM NuGet local piece verification for ecosystem apps, optional user-run MiniModel Peer Companion later, then libp2p, Iroh, BitTorrent-style chunking, DHT discovery, static bootstrap registries, NAT traversal, and signed catalogs.

Hugging Face Source

Use Hub API metadata, OpenAPI docs, model-card discovery, endpoint awareness, and local conversion-script handoffs as an external source lane while keeping `/resolve/` downloads, tokens, and remote inference outside project servers.

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.