Storage DFMS

Storage DFMS

  • Getting Started
  • CLI
  • Guides
  • API Endpoints
  • Help

›Roles

Getting Started

  • What is Distributed File Management System (DFMS)?
  • The External Economy
  • Participate

Roles

  • Storage Director Node
  • Storage Replicator Node
  • Supercontract Executor

Built-In Features

    Drive

    • Overview
    • Lifecycle
    • State

    Replicator

    • Overview

    Verifier

    • Overview

    SuperContract

    • Overview
    • Lifecycle
    • State
    • SC files
    • WasmVM

    Challenge

    • Overview

    Rewards

    • Overview

Protocols

  • Cross-block protocol
  • Fair streaming

Algorithms

  • Verification
  • Consensus

Storage Director Node

The Storage Director Node is a DFMS role that initiates files storage in the network. It is essentially the client that accepts the files and pushes them to replicators. When initiating a drive, a virtual drive is created for the customers to manage their files and directories. To create a new Drive, the owner should prepare and create a new Drive account.

In an autonomous storage network, customers usually access their acquired storage via an easy to use interface. The inner workings of this interface is programmatically designed to accept files or even directories from the customer. The role of the drive owner is to provide an easy way for their customers to access the storage they provided.

Price and Token Economy

Drive Owner as storage providers accepts the payment from customers which in turn they'll use to pay for replicators on the network. Drive will need to have XPX before it can push files to replicators. Exchange protocol kicks in that will convert XPX to Service Units which will then be accepted by the replicators that participates on the contract.

Drive Owner Responsibilities

  • The Storage Director Node creates a Drive account and prepares it with desired properties. When the Drive is prepared, the owner must transfer XPX to Drive balance that equals at least one billing period.

  • The Storage Director Node can upload, remove, rename, move, download files and directories in Drive. Every action has its price and must be paid by the owner.

  • The Storage Director Node can initiate verification of storing files by Storage Replicator Node (the Challenge). Each owner wants to save its file safe and secure.

  • The Storage Director Node makes payments to Storage Replicator Nodes. When the Storage Director Node doesn't pay for the next billing period Storage Replicator Nodes can terminate the Drive.

← ParticipateStorage Replicator Node →
  • Price and Token Economy
  • Drive Owner Responsibilities
Storage DFMS
Roles
SDNSRNVerifierSC Executor
Built-in Features
DriveSuperContractChallengeRewards
Protocols
Cross-block protocolFair streaming
Algorithms
VerificationConsensus
CLI
dfms-clientdfms-replicatorsupercontracts
Giudes
ContractDriveSupercontractsNetwork
Copyright © 2021 ProximaX