Claim words
Every claim on this site about evidence carries one of four words. The word says who stands behind what the claim says.
verifiable
Section titled “verifiable”You check it yourself, against Sui, a file you hold or your own key, with pf-verify (provided at onboarding) or any Sui explorer. It rests on nobody’s word, ours included.
witnessed
Section titled “witnessed”The deployment saw it while handling your data: the bytes it received, a read it served, where it put each copy, a request it turned away. It is our word. Once on the public ledger, it is signed with the deployment’s key and can’t be changed.
issuer-claimed
Section titled “issuer-claimed”The signer’s word, carried by their signature: a licence, a consent basis, an outcome. The deployment checks the signature and binds the claim to exactly the files named. It doesn’t check that the claim is true.
our statement
Section titled “our statement”What we say we did, or what we run, where nothing is left for anyone else to see: a key destroyed, files deleted, the release a deployment serves, where it says its data lives. It rests on our word alone.
Three rules
Section titled “Three rules”- Recorded isn’t checked. An entry on the ledger can’t change once recorded, and
pf-verifyshows that. The record is verifiable; what it says keeps the word of whoever stands behind it. - A signature counts for whoever holds the key. Where we hold a signer’s key, as for a demo deployment’s demo tenant, what that key signs is our statement, not the signer’s.
- An entry you hold, not every entry. The ledger shows that an entry you hold was recorded, not that you were shown every entry about a file. Save entries and their proofs when you get them.
Permafrost runs on Sui testnet and Walrus testnet. Everything here describes a shipped testnet instance, not a production service.