Proof of space
A protocol in which a prover shows that it is dedicating a given amount of storage or memory, rather than computation, to a task.
A proof of space is a protocol in which a prover convinces a verifier that it is dedicating a given amount of storage, rather than computation as in a proof of work 1.
In an initialization phase the prover stores data of the required size; later the verifier sends random challenges that the prover can answer quickly only if it still holds the data, because the data are expensive to regenerate 1. Dziembowski and colleagues built secure schemes in the random-oracle model from graphs with high "pebbling complexity" and Merkle hash trees 1. A related primitive, the proof of secure erasure, uses memory-filling challenges to show that a device's memory has been overwritten 2. Earlier protocols required the prover to be isolated during the protocol; Bursuc and colleagues relax this to slow communication with an outside accomplice 2. One low-trust system design applies these ideas with optional memory challenges that use response latency to check whether data is present, and with memory wiping to remove residual capacity for hidden workloads, as in timed memory-occupation challenges and memory wiping and proofs of secure erasure 3.
Related
Used in
- R1Memory wiping and proofs of secure erasure
- R1Proofs of useful work and resource exhaustion
- R1Timed challenge-response and memory-occupation challenges
- Model weights or data have not left the facility
Sources
- AS. Dziembowski et al. (2015). Proofs of Space. CRYPTO 2015 (IACR Cryptology ePrint Archive 2013/796). Source recordSupports: definition of proofs of space as the storage analogue of proofs of work; initialization and execution phases; construction with pebbling-hard graphs and Merkle hash trees in the random oracle model · abstract; §2
- AS. Bursuc et al. (2024). Software-Based Memory Erasure with Relaxed Isolation Requirements. 2024 IEEE 37th Computer Security Foundations Symposium (CSF 2024). Source recordSupports: proofs of secure erasure; isolation assumption relaxed to slow communication with an external conspirator · abstract
- BN. Cankaya (2026). A System Overview for Near-Term, Low-Trust AI Compute Verification. Machine Intelligence Research Institute. Source recordSupports: optional memory challenges using response latency; memory wiping with incompressible noise to remove residual capacity for hidden workloads · system architecture