Congratulations on Provider nodes over 1000 and User registrations over 7000 — MEMO testnet Phecda test report
MEMO is a new generation of decentralized cloud storage protocol based on blockchain. MEMO is dedicated to building the world’s largest data pool and serving the entire Web3.0 era. In terms of security, availability and scalability, MEMO storage protocol opens a new door for Web3.0 storage with its unique architecture design, innovative verification mechanisms and original storage strategy.
The project was launched in 2017. MEMO’s first version of the white paper was completed in 2018. In terms of project development, testnet Phecda was launched last May. Since its launch, Phecda has received extensive attention in the global encryption and storage fields. The testing has also achieved milestone results. Most features in its original design described in the white paper have been successfully implemented. The MEFS (MEmo File System) has also achieved preliminary results.
1. About Test Data
Phecda is mainly open to the Provider and the User. Up to now, registered Provider nodes exceeded 1,100, including institutional and individual servers, as well as idle storage devices. The pledge space reached 48PB, and registered User roles exceeded 7,000.
2. Protocol Function Test
The MEMO protocol includes the construction of the protocol architecture, role interaction, smart contracts, verification mechanisms, storage strategies, economic models, etc.
In terms of architecture and economic model, Phecda has implemented a tiered design, storing smart contracts on-chain and other data on edge nodes. Three roles are available for registration, namely the Provider, the User, and the Keeper. Related smart contracts can run normally between three role interactions, such as orders, transactions, payments, and withdrawals.
In terms of verification mechanisms, the Keeper challenges the Provider through a random verifiable function. The Provider sends back the proof of data possession after verification, and the Keeper verifies again. The randomness and unpredictability of the whole process can be verified.
In terms of storage strategy, the multi-level fault tolerance mechanism is enabled by two redundancy methods: multi-copies and erasure coding. The test results reveal that the overall speed of erasure coding redundancy is faster than that of multi-copies redundancy. MEMO proposes a multi-level fault tolerance mechanism in its initial design, because erasure coding redundancy is not only more suitable for future large-scale storage scenarios, but also better able to meet the personalized needs of different users.
3. Role and System Performance Test
System performance is mainly presented through the user experience of different roles. For the Provider and the User, apart from basic role registration and deployment, we also test the system’s load capacity, contributing factors, and data storage availability.
1. For the Provider
Role registration test: The Provider is the first role that testnet Phecda has opened for registration . It has tested the process of users registering as Provider, including the registration process, interface smoothness, etc. It has also checked and optimized some bugs encountered in the registration process.
Node deployment test: The storage space of the system is from the space provided by the Provider. In this test, the node deployment of the Provider has been tested, which contains the startup process and pledge space, etc.
Running persistence test: The long-term online rate of nodes is an important factor affecting data reliability, and it is also one of the requirements of the system for the Provider. Therefore, the persistence of the node’s running is an important target in this test.
2. For the User
In addition to the role registration test, the tests for the User (the end-user the system) are mainly in the following aspects:
Upload and download test: The data upload and download speed and related performance were tested. It is found that in most cases, the upload speed is between 1–3M/S (related to the performance of the machine that provides the service, and the bandwidth of the external network). The download speed is faster than the upload speed, and its average speed during the test is 2.5MB/s (5.6MB/s on top). In terms of uploading multiple files at one time, parallel uploading is not yet available, and this will be further optimized in the future.
Application extension test: The User involves institutional users and individual users. In addition to conventional local data uploading, the actual application scenario also involves connecting other application devices to MEMO. Therefore, this round of testing supports the application of various external devices such as cameras, nextcloud, and NAS to connect with the User. After testing, these devices can be connected normally and can upload data to the MEMO network for storage.
4. Where to be optimized in this round of testnet
During the test, MEMO’s underlying architecture, technical mechanisms, role registration and interaction, and usage performance have been well verified. From the test results, the current areas that need to be optimized are the product interface and the parallel uploading, etc.
5. What are the highlights of the next round of testing?
After the end of this round of testnet Phecda, the next round of testnet Megrez will be launched soon. On the basis of Phecda, Megrez has further strengthened the safety and performance, and optimized some functions. This round of testing will make MEMO truly challenge the “large-scale” operation. At that time, we will also launch a reward plan to encourage more users to participate. Please pay attention to the official announcement for the details and participation channels.
6. How to participate in MEMO testnet
Step 1: Enter MEMO official website http://memolabs.org
Step 2: Click on Join TestNet
Step 3: Select a role Provider or User, and follow the guide.
If you encounter problems, please give feedback to firstname.lastname@example.org in time.
Connect with us on