Published in


fastMPC Mainnet Node Installation and Registration

Linux experience will be useful for this task. The instructions here are valid for an Ubuntu setup with version 20.04 or higher ( #lsb_release -a ), though it will most likely work with 18.04. Minimum specification of machine is at least 2 CPU cores, 4 CPU cores and above are recommended, and 8 GB RAM 80 GB disk with fast and stable internet access, preferably at least 2M bandwidth. For this last reason it is recommended to use a VPS such as from AWS, Hetzner, Contabo, etc. rather than a home machine.

The node is installed using a Docker image. The installation starts the MPC service. If you are cutting and pasting commands from here, please do not include the # at the beginning of each command, which is only used to indicate the command prompt.

1.1 Install Docker Image

Start by updating the package list and installing Docker (if you have already installed docker, you can skip this step):-

# sudo apt update

# sudo apt install

1.2 Run the MPC Node

Before you start, you need to make sure that your VPS has port 5928 (in this case is 5928, it can be different for you) open. You may need to go to your firewall settings and open this for TCP and UDP.

If you have started the docker image with the name of gsmpc before, you need to kill the old gsmpc container and wait 2 minutes before updating the new docker image:

If you have already started a fastMPC node,please kill and rm the old gsmpc container first (you can run `docker ps` command to check the old fastMPC node):

# sudo docker kill gsmpc

# sudo docker container rm gsmpc

# sudo docker pull anyswap/fastmpcnode:7.2.5-beta

Notice: do NOT delete your gsmpc enode’s node.key file, it will lose all node data.

Start the docker:

# sudo mkdir /var/lib/docker/gsmpc -p

# sudo docker run -d --name gsmpc --network host --restart always -v /var/lib/docker/gsmpc:/gsmpc anyswap/fastmpcnode:7.2.5-beta --port 48528 --rpcport 5928 --nonetrestrict=false --presignnum 100

1.3 Check Node Status

Here you need to make sure that the node is running and then copy the URL of your node. Running the command below will show you if the node is running.

# sudo cat /var/lib/docker/gsmpc/log/gsmpc.log

# grep updateRemoteIP /var/lib/docker/gsmpc/log/gsmpc.log

This command will show the keyword “updateRemoteIP” and your IP and Port.

If your node is running correctly, you will see something similar to the above.

According to this case, you should ensure that the printed rpcport is equal to 5928.You need to copy the URL (here it is and the port 5928, so the link of the RPC Service Node IN THIS CASE is Your link will be different with this, because each link is unique.2. Node Registration and Login

The next step takes place in the browser of your own computer.

If you have run your MPC node based on the Step1 guidance, while you have not registered this node with it (here is, you need to register your node according to the following instructions.

For the node runners who have completed registration before, You can log in using the same account, click “Edit” and then “Save”, your node version will update to the new version immediately. You can also skip this step then wait for the node info update to the new version, it will take an hour or two. but be aware please do not change your metamask account and enode, it will reset your Run Days to 0.

2.1. Register the Node

Open and click ‘Connect Wallet’.

2.2. Registration Confirmation

After successfully registering the node, click “Network” in the upper left corner of the screen to see that the node is correctly displayed in the list and the version is correct.

When your node appears here and the version is “7.2.5-beta” ,you have completed the node registration.

We advise against running the fastMPC mainnet and testnet nodes on the same server, much alone the same node.

Finding a server other than the one running the testnet node is preferable . If not, it is necessary to ensure that the port and rpc port are different from the mainnet node (for example, the port of the mainnet node is 48528, and the rpc port is 5928, so the testnet node can use, for example, the port is 48516, and the rpc port is 5916) Thus, mainnet account, instead of testnet account, is required if you want to register to be a mainnet node.

Also, node registration pages are different, and must be separated. We have certain recruitment requirements for the mainnet nodes, and will also carry out corresponding verification and testing.

The numbers 5928 and 48528 here are just examples and need to be consistent with the port number of the command you ran earlier when you restart the node.

Note on re-registration: If you don’t change the rpc, just update the node version, you can not re-register, but the front-end update may be slower.
If you change the rpc, you need to register, and if you use the new vps, you need to copy the node key file of the old vps to the same path of the new vps, and then re-register with the previous account.

Note: After the re-registration is completed, you need to confirm whether the version number is correct and whether the registered wallet address is displayed correctly, if there is an error please contact in time, the team will handle it uniformly.

fastMPC mainnet node registration page is:

fastMPC testnet node registration page is:



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
Multichain (Previously Anyswap)

Cross-Chain Router Protocol (CRP), an infrastructure for cross-chain interoperability, envisioned to be the ultimate router for Web3