Xenea Docs
  • OVERVIEW
    • Summary of Xenea
    • Core Technology
      • PoD（Proof of Democracy）
      • DACS (Decentralized Autonomous Content Storage)
  • XENE Tokenomics 1.0
    • What is XENE?
    • XENE Tokenomics
    • XENE Max Supply
    • XENE Genesis Tokens
    • Mining XENE with PoD
    • XENE Burning Mechanism
  • WHITEPAPER
    • Abstract
    • Legal Disclaimer
    • Introduction
    • Basic Concepts of Blockchain
    • Current Blockchain Issues
    • General Description
    • Purpose and Uniqueness
    • Basic Functions of the Xenea
    • PoD Consensus Algorithm Overview
    • Xenea Blockchain Nodes: The Pillars of the Network
    • Block Reward Mechanism: Fair Distribution of Rewards
    • Specifications: A Deeper Dive into Xenea Blockchain
    • XENEA Wallet
    • DACS Node Architecture and Sustainable Generation Manager
    • Halving
    • Finality
    • Token Economics for Sustaining the Xenea
    • Token Allocation and Supply
    • Xenea Governance Overview
    • Future Works
    • Development Roadmap
  • TESTNET
    • How to Run a Test-Net Node
    • How to Connect to Kura Testnet
    • Claim Kura Testnet XENE
    • How to Deploy to Smart Contracts
      • Remix IDE
      • Hardhat
      • Truffle
  • OTHER DOCUMENTS
    • AML KYC Policy
Powered by GitBook
On this page
  1. OVERVIEW
  2. Core Technology

DACS (Decentralized Autonomous Content Storage)

PreviousPoD（Proof of Democracy）NextWhat is XENE?

Last updated 6 months ago

DACS (Decentralized Autonomous Content Storage) provides an architecture ensuring data consistency and persistence by integrating a distributed file system on the blockchain. DACS will initially support IPFS integration, followed by an expanded set of supported file system types.

All storage units have a physical life span, and keeping data in the same storage eventually leads to data loss. Therefore, DACS uses a technology called Sustainable Generation Manager (SGM) to prevent data loss and ensure data persistence. SGM refers to each storage's timestamp and data storage status, replicating the data to other DACS nodes. The data on the original DACS node is then erased. By default, storage expires 180 days after data is stored. Upon expiration, the data is replicated to a new DACS node. The destination of data replication is determined based on network distance (number of hops).

To make DACS more practical, we have also incorporated FASTD (Fast Track Contents Delivery Manager), which allows content to be preferentially cached in DACS nodes.

Related Articles

Sustainable NFT Blockchain Storage for High Availability and Security

For more information on DACS, please refer to our .

Whitepaper
https://ieeexplore.ieee.org/document/10092152
Diagram of Data Copying between Storage Units through SGM