Storage DFMS

Storage DFMS

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

›Drive

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

Drive Overview

The Drive in a nutshell is a representation of a client drive that handles file management system commands. A representational drive or directory where in the owner can manage its files that is subsequently pushed out to replicators. The main drive owner is a multisignature account created by an Storage Director Node. Only Storage Replicator Nodes are signers of this account. It is required for consensus between Storage Replicator Nodes on operations with the Drive.

Properties

The Drive has the following properties:

PropertyDescription
OwnerEvery Drive has a user who created it.
DurationThis value contains the time of Drive existing (counted in blocks, required). Until the end of the Drive, the Storage Director Node can change it (contract prolongation).
Billing PeriodPayout frequency to Storage Replicator Nodes (counted in blocks, recommended 1 month). Note: Billing period must be a multiple of the duration (duration mod billingPeriod = 0)
Billing PriceThe reward for participation. Paid once in billingPeriod (in SO; recommended replicas*driveSize) and is divided between all Storage Replicator Nodes.
Drive SizeA Drive space in MB (required).
ReplicasThe count of Drive copies (required); Amount of Storage Replicator Nodes is not limited. Any Storage Replicator Nodes can join to Drive even if it has the required amount of Storage Replicator Nodes.
Min replicatorsThe minimum count of Storage Replicator Nodes for starting to execute Drive (recommended to be equal to replicas);
Percent ApproversThe percentage of signatures for accepting any transaction (recommended 67);
← Supercontract ExecutorLifecycle →
  • Properties
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