MEMO Storage
  • Introduction
    • MEMO and MEFS
      • MEMO Website
    • Concepts
      • Characteristics and Advantages
      • How to check the balance
      • How to Pledge MEMO
      • MEMO TOKEN ECONOMICS
      • Payment of Memo
      • Requirements
      • Role Introduction
    • Version Introduction
      • Version1-Phecda
      • Version2-Megrez
        • Difference from Phecda
      • Latest Version-Megrez 2.5
  • Start Usage
    • Start user in windows
    • Start user in docker
      • How to start
      • How to use
        • Bucket Operation
        • Upload and Download
    • Start provider in docker
      • How to start
      • Hardware Recommendation
    • How to use user
    • Gateway Mode
    • HTTP Operation
    • Docker Installation
      • For Windows
      • For Linux
  • Commandline Usage
    • Keeper Commandline Mannual
    • Provider Commandline Mannual
    • User Commandline Mannual
  • FAQ
    • Check Log File
    • Common
    • Connection
    • Startup problems
    • Disconnection problems
    • Others
    • Q&A for V1
      • Common
      • User
      • Provider
      • Check Log File
      • Others
  • RAFI
  • Version Update
    • Upgrade to Megrez2.5
    • Volunteer Recruitment Plan
  • Resources
Powered by GitBook
On this page
  • Introduction
  • Sign up for Auth Token
  • Interactive Forum

Was this helpful?

Export as PDF
  1. Introduction

Concepts

PreviousMEMO and MEFSNextCharacteristics and Advantages

Last updated 1 year ago

Was this helpful?

Memo is a large-scale decentralized data storage system with high security and reliability built around blockchain. It is a new-gen blockchain decentralized cloud storage protocol that organizes global edge storage nodes to provide users with safe, reliable and highly available storage services.

MEFS(MEmo File System) is the file storage system for MEMO.

MEMO is a new-gen blockchain decentralized cloud storage protocol developed by MEMO Labs. Our mission is to build a reliable infrastructure for Web3.0. To achieve high scalability and availability, MEMO has vastly innovated data tiering, verification, fault tolerance, and recovery mechanisms. MEMO has made technological breakthroughs on blockchain cloud storage with a new architecture and multiple innovations.

MEMO has designed three user roles: the User, the storage space user; the Provider, the storage space provider; and the Keeper, the coordination manager. Driven by smart contracts, three interconnected roles constrain each other.

MEMO can be divided into three functional role-based layers: settlement, verification, and storage. The settlement layer processes settlement on-chain by aggregating order information and sending the amount of each order to the storage nodes Provider. The verification layer is conducted off-chain. The Keeper nodes challenge the Provider nodes, verifie the results of the proof, and decide whether to issue the withdrawal certificate to the Provider nodes. All processes on the verification layer will go through nodes on the same layer and pass the Byzantine fault-tolerant consensus. The storage layer consists of massive scattered Provider nodes, which store genuine User data and regularly submit the proof of storage to the verification layer.

The following articles will help you learn more.

What is MEMO?

Roles:

Technology:

The user clicks on the link to obtain test tokens in the Memoriae wallet (under development), and the system will send the user a test token of 10 Memo. When the user's test balance is not less than 10 Memo, they will not be able to apply for the test token again.

Email subject: apply for test token

Email content: account address (format such as 0x...), role (Provider or Keeper or User)

Persons who are interested in decentralized data storage systems are welcome to join the Memo community and participate in interaction!

send an eail to to apply for test tokens

Our URL is:

Our is:

Memoriae — Next Generation of Decentralized Cloud Storage Based on Blockchain
Build an Autonomous Storage System: Role Design in Memoriae
Memoriae System Node Matching
Multilevel Fault-tolerant Mechanism Design for MEMO Decentralized Cloud Storage System
MEMO Original Data Recovery Strategy: Risk-Aware Failure Identification (RAFI)
Sign up for Auth Token
sup@memolabs.org
Interactive Forum
GITHUB
https://github.com/memoio/testnet/issues
TWITTER URL
https://twitter.com/Memo_Labs
Introduction