DIOM Docs
  • WEB5 FOUNDATION
    • Wtf is Web5?
    • Core Components of Web5
    • Web5 Technical Breakdown
  • WEB5 ON ETHEREUM
    • Web5 Meets Ethereum
    • EVM Tech Layer for Web5
    • Decentralized Storage in DIOM
    • Privacy and Scalability with zk-SNARKs and zkSync
    • DIOM's Pioneering Approach
  • $DIOM Ecosystem
    • DIOM Vision
    • Web5 Identity Matrix Explained
      • Mechanics in Detail
    • Tokenomics
  • Additional Information
    • Glossary
    • Main Links
    • Assets
Powered by GitBook
On this page
  1. WEB5 ON ETHEREUM

Decentralized Storage in DIOM

Decentralized storage is a critical component of DIOM's architecture, ensuring scalability, security, and user ownership of data. By offloading data from the blockchain to distributed storage systems, DIOM provides a robust infrastructure for managing decentralized identity (DID) metadata, Verifiable Credentials (VCs), and other sensitive information.

Why Decentralized Storage?

Storing data directly on-chain is inefficient due to high costs and limited scalability. DIOM addresses this challenge by leveraging decentralized storage networks like IPFS, Arweave, and Filecoin. These systems offer several benefits:

  1. Scalability: Off-chain storage prevents blockchain bloat by storing large datasets externally while keeping cryptographic references on-chain.

  2. Data Integrity: Cryptographic hashing ensures that stored data is immutable and tamper-proof.

  3. User Ownership: Users retain full control over their data and its accessibility, eliminating reliance on centralized intermediaries.

  4. Cost Efficiency: By storing only cryptographic hashes on Ethereum, DIOM minimizes transaction costs.


Storage Workflow in DIOM

The interaction between decentralized storage systems and the blockchain in DIOM follows a clear, trustless process:

  1. Data Creation: DID metadata and Verifiable Credentials are generated and prepared for storage.

  2. Decentralized Storage Upload: The data is uploaded to IPFS, Arweave, or Filecoin, producing a unique cryptographic identifier (e.g., CID in IPFS).

  3. Blockchain Anchoring: The cryptographic hash of the data is recorded in an Ethereum smart contract to provide a tamper-proof reference.


Example Workflow

DID Document Storage

  1. A user creates a DID Document containing metadata and cryptographic keys.

  2. The DID Document is uploaded to IPFS, generating a unique Content Identifier (CID).

  3. The CID is recorded on Ethereum via a smart contract.

Solidity Example

pragma solidity ^0.8.0;

contract DIDStorage {
    struct DIDRecord {
        string cid; // IPFS CID or Arweave hash
        uint256 timestamp;
    }

    mapping(address => DIDRecord) public records;

    function storeDID(string memory cid) public {
        records[msg.sender] = DIDRecord(cid, block.timestamp);
    }

    function getDID(address owner) public view returns (string memory, uint256) {
        return (records[owner].cid, records[owner].timestamp);
    }
}

Decentralized storage is essential for DIOM's mission to bring Web5 to Ethereum. By leveraging IPFS, Arweave, and Filecoin for off-chain storage, DIOM achieves scalability, cost efficiency, and user-centric data ownership. Combined with privacy-preserving techniques like encryption and zkSync’s scalability, DIOM provides a robust framework for managing identity and data in a decentralized, trustless ecosystem. This ensures that users retain full control over their information while benefiting from the power of decentralized applications.

PreviousEVM Tech Layer for Web5NextPrivacy and Scalability with zk-SNARKs and zkSync

Last updated 5 months ago