about this register
◆ sol pbc says this file describes the v1 chain, in the v1 chain's own words, and is shown exactly as published.
sol pbc release transparency — https://transparency.solstone.app/releases/ what this surface attests: - what sol pbc released: for each product release, a signed ledger entry naming the exact artifacts, their sizes, and their SHA-256 digests, plus the companion release manifests and install/smoke proof receipts. - that it is immutable: release entries and keys live under create-only, indefinitely retained object paths; nothing under releases/<product>/v/ or releases/keys/ is ever overwritten or deleted. - that history is publicly reconstructible: entries are hash-chained, signed with the key below, and independently witnessed; anyone can re-derive and verify the full chain from this surface alone. what this surface does NOT claim: - it does not claim the released binaries provably match their source (no reproducible-build claim). the guarantee is that any later rewrite of history is detectable, not that the original attestation is infallible. signing key: releases/keys/solpbc-transparency-1.pub (minisign). rotation publishes a successor key cross-signed by its predecessor in the same directory. delivery surfaces (where the attested bytes are actually served): - solstone-journal: https://pypi.org/project/solstone-journal/ (with the solstone, solstone-core, solstone-journal-cuda, and solstone-journal-models packages on the same index) - solstone-windows: https://solstone.app/download/windows - solstone-linux: https://github.com/solpbc/solstone-linux/releases note: "schema" URLs inside ledger entries are version identifiers, not dereferenceable documents.