Standards of Encrypted and Mutable Data on IPFS
summary
DAG-JOSE standardizes signed and encrypted IPLD objects by combining DAG-JOSE with JOSE, IPLD and DIDs, enforcing that payloads are CIDs so links are traversable; encrypted payloads use an inline CID (identity-hash) to encrypt the entire object rather than leaking cleartext. JS IPFS supports it now and @ceramicnetwork/ipfs-daemon bundles it; an IPLD-Prime codec exists and Go IPFS support is coming. Wallet RPC extension EIP-2844 (authenticate / create / decrypt methods), JS-DID, 3ID Connect and IDX libraries enable key rotation, multi-wallet auth and anchored mutable documents.
AI-written summary · about
chapters (11)
- 0:00Introduction to DAG JOSE
- 1:32Data challenges on IPFS
- 3:24Existing solutions analysis
- 5:24The DAG JOSE standard
- 7:24Implementing DAG JOSE codecs
- 10:57Handling encrypted data
- 12:15Decentralized identifiers
- 14:45Support and integration
- 15:56Applications and use cases
- 17:26The Ceramic network
- 22:29IDX and conclusion
related talks
16mIPFS and Dapps: Obstacles and Opportunities
51mDistributed Apps with IPFS
17mIPFS in Action: Conflict Zone Use-case
18mIPIP Protocol Improvements: Review & Working Session
11mIPFS for Science
13mLucid & Tiles — Simple, secure, and hackable IPFS dApps
27mDecentralized Storage with IPFS: How does it work under the hood?
12mThe State of IPFS in JS