MEMO Megrez Testnet Participation Guide

The MEMO Megrez testnet was officially launched on April 2, 2022. Compared with the Phecda testnet, the Megrez testnet has optimized the architecture, upgraded the security performance, and added multiple application interfaces, and also initiated challenges to security, performance, and large- scale carrying capacity.

The launch of the Megrez testnet means that the arrival of the mainnet is closer. We welcome encryption, storage, and Web3 enthusiasts from all over the world to participate and witness together.

There are three roles in MEMO decentralized storage protocol,namely User, Provider and Keeper. In the Megrez testnet, the test of User and Provider roles is open first. People can choose one of these two roles to participate in the test.During the Megrez testnet period, we suggest you only choose one role to participate.

Basic configuration environment:

Same as the Phecda testnet, the Megrez testnet still uses the command line language initially. Users execute commands by entering the command line. We recommend using it on different platforms such as Linux and Windows by deploying Docker. Meanwhile, we are also developing a web version with better visualization to meet the needs of different groups of people.

Suggestions for role selection:

●User: The end-user in the protocol, has the right to choose a suitable storage node Provider and manager(Keeper), to provide services for itself. At the same time, it needs to pay the corresponding fees for the services obtained.

●Provider: The party that provides storage space in the protocol. It provides storage services for users and is paid by users. It needs to maintain a certain online rate and accept the challenge of Keeper regularly.

We recommend:

●If you have large data storage requirements, you can choose the User role. Currently, all Users can store data with a free charge during the testnet.

●If you have idle or professional storage devices, you can choose the Provider role. MEMO supports almost every storage device, including internal storage devices (solid-state drives, mechanical hard drives), external storage devices (SD cards, U disks, etc.) and NAS devices.

Role configuration environment:

MEMO is an advocate of the sharing economy based on the blockchain, and a low threshold makes it possible for everyone to participate.

There are no special requirements for the basic environment configuration of the User role. Theoretically speaking, it can run as long as there is network access and Docker is successfully installed.

Since Provider is the party that provides storage services, we recommend the following configuration:

● 8 cores, 16G memory, 2TB storage, 20Mbps bandwidth

● External network IP (you must have an external network IP to become a provider node), port 4001 is available

● Docker environment

● Linux system

Register a role and run it:

Whether you choose to become a User or a Provider, the basic environment configuration requires Docker to be installed. So the first step is to install Docker. The function of Docker is to make the MEMO protocol compatible with different operating systems. The following describes the registration and running process of roles (take the User as an example).

1.Start the User role

(1) Install docker

There are two scenarios when installing docker: on Linux and on Windows. For the specific operation guide and download address, please refer to the following link

(2) Pull image

An image is an element in Docker that can only be used in the Docker environment. The service program of MEMO is released in the form of an image. If the version needs to be upgraded in the future, then re-pulling the image is required to obtain the latest version of the service program. Run the command as follows to pull the image.

If no error is reported and the following appears, it means that the image has been pulled successfully. This process will take about 2–3 minutes.

(3) Initialize wallet

Initializing a wallet is the process that which MEMO generates an account which is also called a wallet. It is a contract address deployed on the blockchain. This address is the only identity symbol that users own in the protocol, and the subsequent transactions will be done through this contract address.

After the above image is successfully pulled, the User root directory and password need to be modified in the output document.

Modify User root directory

The operation method to modify the User root directory to a directory on the user’s personal device. : Modify the following yellow characters “$yourLocaPath” to any file directory of the device, such as D:\memo.

Example after modification:

Change the password, the default password is memoriae

Change the following yellow characters “yourPassword” to your own password.

You can change the following yellow characters “yourPassword” to your own password. Please note: After changing to your own password in this step, please change to the same password as well accordingly in all subsequent commands to keep it consistent. In the following example, it is assumed that “the modified password” is still the default password: memoriae.

Example of the changed password:

After the above two modifications are completed, click the Enter to initialize the wallet. If no error is reported, you can proceed to the next step.

(4) Check wallet address

After the wallet is successfully initialized, the wallet address can be obtained, and then you can proceed to the next step to contact the MEMO developer community to top up. The top-up address is the wallet address.

Specific step: After the initialization is completed, you need to modify the root directory to execute the checking wallet address command. The modified root directory must be the same as the User root directory set in the previous step, that is, the following yellow characters “$yourLocaPath” need to be modified to D:\memo.

After the modification is completed, enter the corresponding command and press Enter to check the wallet address. The yellow string in the following example is the wallet address.

(5) Contact MEMO developer community for wallet top-up

This step is for the MEMO developer community to top up a certain amount of TOKEN for each participating role to help it start running in the protocol.

There are two steps: tweeting and sending emails.

First, tweet and @MemoLabs (, the content is: I have joined the MEMO testnet, the example is as follows:

Then send an email to with the twitter link. The content of the email must include the following elements: wallet address, role type, and tweet link.

After receiving the email, MEMO developer community customer service will deposit a certain amount of TOKEN to the wallet address as soon as possible, and then the role is successfully registered. If you do not receive the TOKEN, please send dynamic screenshots or URLs to, and the developer community will deal with it as soon as possible after receiving the email. Due to the distribution of customer service in different regions of the world, there is a certain time difference, so there may be a delay in top-up, please be patient.

(6) Start up

The User must complete the top-up before proceeding to the next operation.

There are two types of User node startup: with gateway and without gateway. The gateway is mainly used for the startup of the Web page, and is suitable for the subsequent visualized Web version. Command line method is used at current stage, and there is no need to start the gateway.

The parameters of the root directory need to be modified when you start a command. Since this command is long, it is recommended to copy it to the general document to modify the parameters, and change the character “$yourLocaPath” to the root directory of User: D:\memo.(Tips:If you changed the password when initializing the wallet in the third step, you should also change the password to the new password here.)

The entire process of starting the User node will take about 20 minutes, please be patient.

For the specific execution commands of the above whole process, please refer to the User Startup Process Guide: Start User — MEMO (

2.User role operation

(1) Check the running status of the node

After the node is successfully started, you can enter the Docker container. Check the container status first. If the “app#” is displayed, it means that the container has been entered. The container needs to be entered first to proceed all subsequent bucket creation operations, uploads and downloads.

Then enter the command “mefs-user info” to check the running status of the node. Since the startup process takes about 20 minutes, when the Sync Information is displayed as “true”, it means that the node has been started. The example is as follows:

For specific commands, please refer to Checking the running status — MEMO (

(2) Create bucket

MEMO provides dedicated encrypted storage space (LFS) for each User. Each storage space contains multiple buckets. A bucket is a container used by users to store objects, and each bucket can contain multiple data files. The redundancy policies of the protocol are “erasure code” and “multi-copies”. The default policy is erasure code, however, a specific redundancy policy can be specified when creating a bucket. The erasure code uses the “3+2” mode by default, and the redundancy level can also be determined by adjusting the number of data blocks and check blocks. The data redundancy policy in each bucket is the same.

Before creating a bucket, you need to enter the container (execute the enter container command, when the “app#” is displayed, it means that you have entered the container), and then execute the create bucket command. After the following is displayed, it means that the bucket has been created successfully.

For details, please refer to Bucket Operation — MEMO (

(3) Upload and download

Uploading and downloading files is the basic operation of User.

To upload a file, you need to copy the specific file path to the command, and then execute the command. For example, the file path is ~/.memo-user/data/NFT.jpg, add this path to the command and execute. The following will be displayed when the command is successfully executed.

To download, you need to know the bucket name and file name. In the command, “bn” is the bucket name, “on” is the data name in the bucket, and the “path” is followed by the corresponding data download path and name. The path and name can be modified. As shown in the example below, a data named “onj1” is downloaded to the path of ~/test.txt, which can be viewed through the command ls~/test.txt.

For specific commands, please refer to Upload and Download — MEMO (

(4) Check the connection status of the User node

Check the network id (cid), ip address and port of the current User node. The function of this step is to check whether the network connection of the node is successful. If no error is reported, the connection is successful. For specific commands, please refer to Checking the net status — MEMO (

3.Provider role startup and operation

The startup process of the Provider role is the same as that of the User. It also has 6 steps: installing Docker, pulling the image, initializing the wallet, checking the wallet address, top-up, and starting. The parameters that need to be modified are also the root directory and password, there is only a little bit difference in commands.

For the startup process of the Provider role, please refer to Start Provider — MEMO (

Different from the User role, there is no bucket creation and upload and download for the Provider role, but checking the node running status and network connection status are also necessary.

Checking the running status, please refer to Checking the running status — MEMO (

Checking the network status ,please refer to Checking the net status — MEMO (

The Provider must apply for top-up from the MEMO developer community before they can be started.

Users from testnet Phecda to Megrez:

For users who have registered and run the Phecda testnet, it is quite easy to participate in the Megrez testnet. Just import the private key of the Phecda testnet into the Megrez testnet, and there is no need to repeat the registration process again. The specific process is as follows:

For the User: For the User — MEMO (

For the Provider: For the Provider — MEMO (

About subsequent updates:

The above is the participation guide for the MEMO decentralized cloud storage Megrez testnet. According to the progress of the testnet, we will have irregular updates in the follow-up, and the update reminder will be released in various channels in time. Please pay attention to the following accounts for the latest information:






MEMO, is a new-gen blockchain decentralized cloud storage protocol. The mission is to build a reliable storage infrastructure for the Web3 era.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Time for a 1-UPdate…

An Open Letter to Our Community on the Issuance of USDD, a Decentralized Algorithmic Stablecoin on…

Living Assets — NFT 2.0: a Toolbox for Engagement

Matt Yue —the former Senior Software Engineer of Meituan and LeEco Joined TRON

Factors That Make Or Break Blockchain-Based Projects

About Vinchain

Beyond Cryptocurrency: How Blockchain Technology Is Transforming Industries?

Introducing EKTA

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Memo Labs

Memo Labs

MEMO, is a new-gen blockchain decentralized cloud storage protocol. The mission is to build a reliable storage infrastructure for the Web3 era.

More from Medium

RociFi launches on Kovan Testnet

Archway Incentivized Testnet Torii-1

SalmonChain Blockchain Launch MainNet and TestNet.

A small guide to the Oracle finance testnet