DÆTA
  • DÆTA
  • DÆTA Storage
    • Overview
    • Vision
    • Problem Statement
    • Market Opportunity
  • Use DÆTA
    • DÆTA Account
    • DÆTA Client
    • Use DÆTA App
  • Core Concepts
    • Decentralized Storage
    • Storage Nodes
    • Storage Contracts
    • Encryption and Security
  • Node Operations
    • Storage Node
    • Node Management
    • Performance Optimization
  • DÆTA Framework
    • Key Components
      • Users
      • Nodes
      • Satellites
    • Data Flow
    • Redundancy and Data Repair
    • Blockchain Compatibility
    • Third-party Integrations
    • Industry Use Cases
  • DÆTA LVRG
    • Overview
    • Vision
  • Key Features
    • GPT-to-Earn
    • Open Data Marketplace
  • Data Components
    • Datasets
    • Autonomous Agents
  • Data Sovereignty & Decentralization
    • Data Sovereignty
    • Decentralization & Censorship Resistance
  • How to Get Started
    • Install DÆTA LVRG Extension
  • Tokenomics
    • DÆTA Token
    • Utility and Economic Mechanism
    • Staking and Rewards
    • Allocations
  • Resources
    • Roadmap
    • FAQ
    • Glossary
    • Contact
    • Legal Disclaimer
    • Compliance
  • External Links
    • Website
    • Twitter
    • Telegram
    • Discord
    • Blog
    • GitHub
    • Whitepaper
    • Token Audit
    • LVRG Audit
    • LinkTree
Powered by GitBook
On this page
  1. Core Concepts

Storage Nodes

Storage nodes form the backbone of the DÆTA network, enabling the distributed infrastructure that powers decentralized storage.

Storage nodes are the backbone of the DÆTA network, providing the distributed infrastructure that makes decentralized storage possible.

Node Types

Minimal storage contribution (< 1TB)

Suitable for home users with spare capacity

Lower earning potential but easier to set up

Moderate storage contribution (1-10TB)

Ideal for enthusiasts and small businesses

Balanced earning potential and resource requirements

Large storage contribution (>10TB)

Designed for data centers and large organizations

Highest earning potential with stringent uptime requirements

Node Responsibilities
graph TD
    A[Store Data] --> B[Respond to Retrieval Requests]
    B --> C[Participate in Network Consensus]
    C --> D[Conduct and Respond to Audits]
    D --> E[Maintain High Uptime]
    E --> A
Node Setup Example | Standard Node
# Install DÆTA node software
curl -sSL https://get.daeta.xyz/node

# Initialize node with 2TB storage
daeta-node init --storage-path /mnt/daeta-storage --capacity 2TB

# Configure node
cat << EOF > ~/.daeta/config.yaml
node:
  id: "generate-unique-id-here"
  storage_path: "/mnt/daeta-storage"
  capacity: "2TB"
network:
  bootstrap_nodes:
    - "/ip4/104.131.131.82/tcp/4001/p2p/QmaCpDMGvV2BGHeYERUEnRQAwe3N8SzbUtfsmvsqQLuvuJ"
earnings:
  payout_address: "0xF942Dba4159CB61F8AD88ca4A83f5204e8F4A6bd"
EOF

# Start node
daeta-node start

Node Performance Metrics

Successful Audits.

99.9%.

Average time to respond to requests.

<100ms.

Percentage of allocated storage used.

80%.

Data transfer rate.

>100Mbps up/down.

Percentage of passed storage proofs.

99.99%.

PreviousDecentralized StorageNextStorage Contracts

Last updated 8 months ago