Explanation
Five pages. They explain why the pieces are arranged this way and what each choice rules out. The Guides are where you run things, and they carry the badges that say what has been exercised on the hosted instance; a concept page makes no claim about the instance, so most of these carry none.
This is also the only group where a page may describe something not yet built.
- A storage receipt is not a provenance receipt — Walrus records that a blob is held; the receipt on Sui records what the content was and when it was recorded. Only one of those survives the storage arrangement ending, and the difference decides which promises this site makes.
- Deletion by key destruction — you cannot un-write bytes on a shared substrate, so deletion here means destroying the only key that reads them and certifying that on chain.
- Leases, renewal, and nothing expiring silently — storage is leased by epoch, a lapsed lease fails silently, and the instance treats every object’s lease end as state it owns.
- What survives Permafrost, and what does not — given only a receipt id, what you can reconstruct without us, and the exact line where that stops.
- Planned: attested key release — the one piece that is designed and not built.
Start with the first if you are weighing what the storage claim is worth. Start with the fourth if you are weighing whether you could leave.
Permafrost runs on Sui testnet and Walrus testnet. Everything here describes a shipped testnet instance, not a production service.