Storage DFMS

Storage DFMS

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

›Rewards

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

Rewards

Rewards for files

If the Drive account has SM on the balance and the Drive has Pending or Finished state, Storage Replicator Nodes can send the transaction to get the reward for files transferring during the billing period. The consensus of Storage Replicator Nodes decides who will be the initiator. The initiator collects receipts (Fair Streaming protocol) from Storage Replicator Nodes and the owner and after creates the get rewards transaction and announces it to Blockchain. Other Storage Replicator Nodes validate it (the owner doesn't validate it), and cosign it in case everything is correct.

If the transaction contains information about Storage Replicator Nodes, which didn't put the deposit for active files or uploaded size equals zero, Blockchain will reject it.

Replicators should send information about all files uploaded during a billing period. But before sending this information, Storage Replicator Nodes should validate receipts of each other, so everyone makes sure that they are related to the same billing period accordingly. Uploaded information can be collected via Fair Streaming. After confirmation of the transaction, all SM that stored on the balance of the drive's account will be spread proportionally uploaded data. Only then Storage Replicator Nodes can delete receipts.

In case the Drive has the Finished state, but the Drive account contains SM on its balance, Storage Replicator Nodes still can send the get reward's transaction. After the confirmation, Blockchain prunes info about the Drive from cache after 360 blocks, the multisig account will be removed.

Rewards for drive

At the end of each billing, period Storage Replicator Nodes get their reward for participation in the drive. The billingPrice of the Drive is distributed between all Storage Replicator Nodes that passed verification. Every Storage Replicator Node gets the reward appropriate to its time in the contract (formula below). If it was the last billing period, then the deposit would be returned to honest Storage Replicator Nodes.

Formula

alt-text
Where
alt-text
Where
alt-text if a Storage Replicator Node passed all verifications
Or
alt-text if a Storage Replicator Node failed verification.

← OverviewCross-block protocol →
  • Rewards for files
  • Rewards for drive
  • Formula
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