Verify a download

No account, no token, no throttle. Three commands from clean machine to verified model.

The three commands

1 · Download the torrent

Every model page in the catalog carries its .torrent file. Fetch yours and hand it to your client:

aria2c https://aiseedbank.org/torrents/<slug>.torrent

Each model page also carries a magnet link that opens the swarm directly — no file download needed.

2 · Fetch the signed manifest set

curl -O https://aiseedbank.org/torrents.json
curl -O https://aiseedbank.org/torrents.json.minisig
curl -O https://aiseedbank.org/minisign.pub

3 · Verify the signature

minisign -V -m torrents.json -p minisign.pub

The manifest lists every published model with its infohash, per-file hashes, and provenance. If minisign says the signature is good, the bytes you compare against are the bytes the maintainers signed — a mirror that tampered with anything fails here.

Checking the per-file hashes

Every model page carries a Files & hashes table: one row per file with its digest and a method badge. The badge is the algorithm actually used to produce that digest — the archive stores files two ways, so the digest you check depends on the file:

• sha1-git-blob — the file as git stores it. Verify with git hash-object <file> (git prefixes a size header, so a plain sha1sum will not match).
• sha256-lfs — the payload file as git-lfs stores it, a straight sha256 of the bytes. Verify with sha256sum <file>.

So both digests live in one signed place: the large model payloads (weights and other LFS-stored files) carry sha256, the small git-stored files (READMEs, configs, tokenizers) carry sha1 — each labeled with its method, never relabeled.

On top of the per-file table, each model ships a signed <slug>.SHA256SUMS — a sha256 for every file in the model, whatever its storage method, plus its minisign signature. One command checks a whole download against it:

minisign -V -m <slug>.SHA256SUMS -p minisign.pub
sha256sum -c <slug>.SHA256SUMS

Fetch both from https://aiseedbank.org/torrents/ alongside the .torrent — the Cite this release card on each model page links the pair when the model's sums are complete.

What "verified" means here

Every payload in this archive was verified against upstream Hugging Face at fetch time, with the exact upstream revision pinned in the signed manifest. That is the claim — nothing more. Seedbank does not audit model behavior, and the upstream of record for each model is Hugging Face; this archive preserves and re-distributes those bytes.

Which client? Which file? Get help has the client and format guide. Ready? Browse the catalog →