Skip to main content

Distributed Storage System for NFT (H2 2025)

Planned for H2 2025 and is part of the Fungistor System.

Technical Specifications

NFTs (Non-Fungible Tokens) can be stored using FungiStor + QSFS + ZSTOR architecture,

ensuring:

  • NFT Metadata (JSON, image, etc.) is stored in QSFS, distributed over ZSTOR and ZDBs
  • The NFT token itself (on-chain) contains a pointer (e.g. QSFS link, hash, or content ID)
  • Retrieval goes through Decentralized DNS → HTTPS Frontend → QSFS

advantages:

  • Streamlined upload process for NFT owners
  • Global retrieval capability with integrated data verification
  • Multi-interface availability (IPFS, HTTP(S), etc.) for global access
  • Built on a distributed storage architecture optimized for energy efficiency, security, and privacy
  • Data ownership remains with the NFT owner

Technical Architecture

Diagram

User-Controlled Data Persistence

The architecture implements a user-controlled approach rather than a shared-all model.

Data storage administrators maintain control over:

  • Geographic data placement parameters
  • Redundancy configuration
  • Data retention policies
  • Content delivery network configuration (availability zones and duration)

Technical Reliability Mechanisms

  • Data integrity verification through cryptographic hashing
  • Redundancy mechanisms to prevent data loss
  • Automatic integrity verification through hash (fingerprint) validation with self-healing capabilities
  • Per-owner encryption and compression implementation
  • Configurable redundancy levels

Lookup Architecture

  • Integration with Mycelium Network protocols
  • Multi-protocol URL and storage network support
  • Compatible with IPFS and HyperDrive URL schemas
  • Implements unique DNS schema with globally unique identifiers

Content Delivery Implementation

Files are distributed across multiple geographic locations for optimized access.

Each file is assigned a unique URL for retrieval from any available storage location.

Edge caching is implemented at each endpoint for improved performance.

Self-Healing Storage Architecture

The system implements automatic detection and correction of data corruption (e.g., bitrot).

In hardware failure scenarios (storage device or node), the system automatically redistributes data according to the configured redundancy policy.

Underlying Storage Algorithm

  • Implements a distributed storage system using quantum-safe security protocols
  • Designed for global-scale operation with significant efficiency advantages over traditional replicated systems
  • Utilizes forward-looking error correcting codes for data integrity

Energy Efficiency

The storage architecture requires approximately 3-10x less energy compared to traditional replicated systems.

Multi-Protocol Interface Implementation

The stored data is simultaneously accessible through multiple protocols:

  • Interfaces:
    • IPFS
    • HTTP(S)
    • Filesystem

This multi-protocol approach provides flexibility for various integration scenarios.

Content objects (videos, images, etc.) can be embedded in any HTTP-compatible platform.