You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
How do Arc Space, Solid, IPFS, Filecoin and Arweave compare?
Compare control, access protocols, addressing and retention as distinct responsibilities.
These systems discuss data at different layers. The table describes their primary concerns; it does not establish that one product has integrated another protocol.
| Approach | Primary concern | Ask next |
|---|---|---|
| Arc Space | DID-associated data spaces and application access | Which permissions, transports and migration paths exist in this deployment? |
| Solid | Web protocols for permissioned access to externally stored data | Which versions and authorization mechanisms do client and server implement? |
| IPFS | Content addressing, discovery and transfer | Who retains copies and makes them retrievable? |
| Filecoin | Provider-based storage organized with proofs | What are the storage arrangement, retrieval path and availability conditions? |
| Arweave | A protocol objective of long-term, permanent retention | How are versions handled, and does retention fit deletion requirements? |
| MyData | Human-centric data principles and collaboration | How do principles become understandable control and working services? |
A public archive and a private journal have different acceptance criteria. Start with concrete operations and expectations, then choose mechanisms at the appropriate layer. The cited Arc Space technical documentation describes ARC 2.0.0-beta.28; it does not establish equal capabilities across all backends and transports.
Sources and further reading
Check your understanding
Does content addressing establish personal data sovereignty by itself?
No. Also examine authorization, application understanding, continued access and migration.
Continue along a learning path
- Understand personal data spacesStep 8 of 8