Leaving

If we stopped answering tomorrow:

What survives us

• Every receipt, on Sui, from any node. verifiable
• Verification of any original file against its receipt: with the file, and its salt for an encrypted one, whose fingerprint is salted by default. Keep each file’s salt with it. verifiable
• The way to your bytes. A receipt points to what it covers on Walrus, fetchable from any public gateway.
• The bytes on Walrus, while their span holds.

What deleting does

DELETE removes an object from your deployment. Data on Walrus stays readable by blob id until its span ends; the receipt stays. To remove it everywhere, use custody or ask for deletion at the end of a contract.

Taking your data out

While your deployment answers, copy your objects out with any S3 client: list each bucket and GET every object, or aws s3 sync s3://<bucket> <dir>. Save your receipts’ ids, each encrypted file’s fingerprint salt (its fingerprint is salted by default), and the ledger entries and proofs you want to keep alongside; they check against Sui after the deployment is gone. verifiable

Where it stops

• Encrypted with our keys: fetchable without us, not readable.
• Local files: never on the network.

To read without us, encrypt before upload. Your ciphertext and receipts are then yours alone.