Repository navigation
Tensorseed 0.3.1
Tensorseed 0.3.1 is a verified serving and catalog release. It adds
signed follow lists, claim expiry and revocation, a check-claim command,
a verify-only crate with a WebAssembly build and a JavaScript package, and
an endpoint check that no longer fails honest sellers. Tensorseed Desktop
is 0.3.1 too: it gets the library changes and is the first version offered
to 0.3.0 installs through the in app updater. Formats and commands may
still change before 1.0.
Highlights
check-endpointno longer fails honest sellers. On one CPU host,
0.3.0 passed an honest llama.cpp seller 1 run in 11 against its own
reference set, because llama.cpp logprobs drift from run to run and one
failing challenge failed the run. References now hold per-token medians
over several passes (reference-logprobs --samples N, default 5), the
run is decided over the whole set (ts.set-decision/1: any bad
signature, more than--max-fail-fractionfailing challenges, default
0.25, or a median deviation above--max-median, default 0.35 nats),
andtensorseed calibrate-referencewrites your own server's spread into
the reference file. 55 of 55 honest runs passed, and other
quantizations, a smaller model under the claimed name, and tampered
responses failed every run.--max-fail-fraction 0keeps the 0.3.0 rule.tensorseed check-claim <url-or-file>checks a seller's
ts.served-weights/1claim end to end: its hash and wallet signature,
that it is served at its ownpublic_base_url, that its catalog is one
you trust with the same publisher key, manifest, and files, no takedown,
catalog freshness, and the commercial serving mark recomputed from the
catalog's license. Exit 0 pass, 1 fail, 2 inconclusive;--jsonwrites
ts.claim-check/1.- Claim expiry and revocation. An optional
expires_at(set with
--expires-inonclaim-servingandserve-inference --sign) and
signed revocation lists (tensorseed revoke-claim, served at
/.well-known/tensorseed/revocations.json).check-claim,
check-endpoint, andverify-responsehonour both; an unreadable
seller list makes a passing seller check inconclusive. - Signed follow lists (
ts.follow-list/1). A publisher signed list of
catalogs that a marketplace, a community, or one user can follow
instead of adding each catalog by hand:catalog follow-list create,
sign,verify,follow, andunfollow. Followers pin the list key
and the acceptedrev, and a list only touches the entries it added. - Verify anywhere.
tensorseed-verifyis now the verify-only crate
for claims, revocations, signed responses, catalogs, and follow lists,
with no networking or serving dependencies, and it builds for
wasm32-unknown-unknown. The WebAssembly build exports the claim and
response checks, and the@tensorseed/verifyJavaScript package (built
and tested in this release, not published to npm yet) wraps it for
Node and browsers. - Smaller fixes.
verify-responsechecks URLs likecheck-claim
(url_mismatch), the response skew window is configurable
([verify] max_skew_secs,--max-skew, 1 second to 7 days) and
verify-response --atchecks stored responses,catalog export --catalogexports catalogs added withcatalog add,catalog info
shows an empty publisher contact as "none published", and the release
archives ship every guide.
The full list of changes is in
CHANGELOG.md.
Compatibility with 0.3.0
Read this before mixing 0.3.0 and 0.3.1 on one machine or between a
seller and a buyer.
- Reference files: 0.3.0 reference files, commitments, and reports
load unchanged in 0.3.1. Reference files written by 0.3.1 with
--samplesabove 1 (the new default is 5) or calibrated with
calibrate-referenceare rejected by 0.3.0 binaries. - Claims with
expires_at: claims without an expiry hash and verify
exactly as in 0.3.0, in both directions. A claim withexpires_atis
rejected by 0.3.0 binaries (unknown field). There is no default
expiry, so leave out--expires-inwhile your buyers still run 0.3.0. - Configs with follow lists: the new config keys
[[follow_lists]]
andfollow_listin[[catalogs]]make 0.3.0 refuse the config.
Remove them (or runcatalog follow-list unfollow) before going back
to 0.3.0. Desktop and the CLI share one config, so this applies to
both. - Hand-written claims: no claim hash changes, and every claim
Tensorseed has written is unaffected. A hand-written claim with an
explicitnullfor an optional field, without
catalog.publisher_key_idorlicense.id, or with unknown nested
fields loaded in 0.3.0 and is rejected in 0.3.1. verify-response --claim <URL>now fails withurl_mismatchwhen
the claim is not served at its ownpublic_base_url(for example, a
claim fetched through a local proxy). Pass the claim file instead.--max-skewof 0 or above 604800 (7 days) is now refused. Use
verify-response --atfor stored responses.- Reports:
ts.claim-check/1,ts.check-endpoint/1, and
verify-response --jsongain optional fields and the error labels
claim_expired,claim_revoked, andurl_mismatch; 0.3.0 reports
still load.
Downloads
Tensorseed Desktop
| File | For |
|---|---|
Tensorseed.Desktop_0.3.1_x64-setup.exe |
Windows x86_64, NSIS installer. Installs for you, no administrator rights. |
Tensorseed.Desktop_0.3.1_x64_en-US.msi |
Windows x86_64, MSI. Installs for all users, needs administrator rights. |
Tensorseed.Desktop_0.3.1_amd64.AppImage |
Linux x86_64, any distribution. Make it executable and run it. |
Tensorseed.Desktop_0.3.1_amd64.deb |
Debian and Ubuntu, x86_64. |
Tensorseed.Desktop-0.3.1-1.x86_64.rpm |
Fedora and RHEL, x86_64. |
Tensorseed.Desktop_0.3.1_x86_64.flatpak |
Flatpak bundle, x86_64. Not on Flathub yet. |
Install the Flatpak bundle with
flatpak install --user Tensorseed.Desktop_0.3.1_x86_64.flatpak. It uses
the GNOME 51 runtime, which Flatpak fetches from Flathub. It includes the
tensorseed CLI (flatpak run --command=tensorseed dev.tensorseed.desktop).
Command line
The CLI archives and packages as in 0.3.0: static Linux builds for x86_64
and ARM64, a glibc 2.17 Linux build, Windows x86_64 and ARM64, .deb and
.rpm packages for x86_64 and ARM64, and signed source archives
(tensorseed-0.3.1-src.tar.gz and .zip).
There is no macOS build.
Updates
- AppImage, MSI, and NSIS from 0.3.0: Desktop offers 0.3.1 when it
starts (unless you turned the check off in Settings) or when you choose
Check for updates. It shows the version and these notes and
installs only after you confirm, and only if the installer is signed
with the Tensorseed Desktop update key (idB81047C9B22BB400) for
0.3.1. You can also install 0.3.1 by hand from the files above. - .deb and .rpm: these never update themselves. Install the 0.3.1
package with your package manager. - Flatpak: the bundle never updates itself. Install the 0.3.1 bundle
the same way as 0.3.0. - CLI: download the new archive or package.
Windows SmartScreen
The Windows installers are not code signed yet, so Microsoft Defender
SmartScreen may show "Windows protected your PC" when you start one, and
your browser may call the file uncommon. Check the download against
SHA256SUMS first (see "Verify your download" below), then choose
More info and Run anyway.
Serving inference
Tensorseed does not bundle an inference engine. To serve a model, install
llama.cpp (llama-server, for GGUF models) or vLLM (vllm, for
safetensors checkpoints; Linux with a supported NVIDIA or AMD GPU, or WSL 2
on Windows) yourself, then use tensorseed serve-inference. Desktop does
not serve inference yet; use the CLI. See the
seller guide
and, for marketplaces, the
integration guide.
Verify your download
Every download above is listed in SHA256SUMS, which is signed with the
Tensorseed release key (minisign, key id F5D2D3C4C27D459D). Download the
file, SHA256SUMS, and SHA256SUMS.minisig, then:
minisign -Vm SHA256SUMS -P RWSdRX3CxNPS9Vl1JNjDnZ04OmM/3xrfp9vqG5FO8TNpK8Sbg6ENAI4P
sha256sum -c --ignore-missing SHA256SUMSThe trusted comment must read tensorseed 0.3.1 release SHA256SUMS. On
Windows, see
RELEASE-KEY.md.
The .sig files next to the Desktop installers are the update signatures
that Desktop checks; you do not need them to verify a download.