The Ultimate Guide to Achieving Work-Life Balance: Expert Tips and Strategies

💡Tryout HIVEOS Entirely Free:

Iron Fish Mainnet Update: How to Update Your Nodes


The Iron Fish mainnet has finally been launched, which means it’s time to update our nodes once again. In this article, we will guide you through the process of updating your nodes to the latest version of Iron Fish. We will provide step-by-step instructions and explain the changes you need to make to ensure a smooth transition to the mainnet.

Exporting Your Wallet

Before updating your nodes, it’s important to export your wallet to ensure that you don’t lose your funds in case something goes wrong during the transition. Exporting your wallet is similar to writing down your seed phrase. By saving your private keys, you can easily import your wallet and access your funds again.

To export your wallet, open up Powershell and run Iron Fish by going to Wallet > Export. This will display your private keys, which you should save in a secure location such as a notepad or USB drive. Keeping a backup of your wallet is crucial for the safety of your funds.

Installing the Latest Version of Iron Fish

To update your nodes, you need to install the latest version of Iron Fish. The process is quite simple. Open Powershell (or Powershell ISE as an administrator) and run the following command:

npm install -g ironfish

This command will download and install the latest version of Iron Fish. It may take some time to complete, so be patient during the process. Once it says, “changed 571 packages in 46 seconds,” you can proceed to the next step.

Updating to Mainnet

Now that you have installed the latest version of Iron Fish, it’s time to update your nodes to the mainnet. In Powershell, type the following command:

ironfish mainnet

This command will initiate the migration process and swap your data from the testnet to the mainnet. You will be prompted with a message asking if you want to proceed with the migration. Type “yes” and hit enter to continue.

Please note that if you are using Powershell ISE, you may encounter some issues during this step. If that’s the case, it’s recommended to switch to regular Powershell to complete the migration process successfully.

Verifying Your Node Status

Once the migration process is complete, you can verify that your node is successfully connected to the mainnet. Open a new Powershell tab and run the following command:

ironfish start

This command will start your node, and if everything goes smoothly, it should display “main” instead of “test” in the output. This ensures that your node is now connected to the Iron Fish mainnet.

Checking Your Wallet Address and Balance

To confirm that your wallet address remains the same after the update, run the following command in Powershell:

ironfish wallet address

If the displayed public address matches your previous address, there is no need to worry. Your funds are intact and accessible.

To check your current balance, use the command:

ironfish wallet balance

If you had funds in your wallet on the testnet, they may not appear on the mainnet immediately. You might have to wait for a pool payout or perform solo mining to receive your funds on the mainnet.


Updating your nodes to the Iron Fish mainnet is a straightforward process. By following the steps outlined in this article, you can ensure that your nodes are up to date and connected to the mainnet successfully. Remember to export your wallet before the update and keep your private keys secure. With the mainnet in place, you can participate in the Iron Fish network and enjoy the benefits it offers. Happy mining!

You May Also Like


  1. Is there a way to run or move the ironfish node to another disk instead of the windows installed disk, it seems like it will take up a lot of space on the c disk in the future. like any config file setting. I've been able to do it for chia before. It would be good to do this too.

  2. Hey bro..
    This character ":" is called a colon, not a semi colon, which is ";"
    Just thought I'd mention it, cuz people might be confused when commands, which youre mentioning in your videos, don't work.
    Thanks for your videos btw. I've watched a ton of them.

  3. yesterday it was like a 1.6 Ph/s pool network now today its 1.8 , i thought some will give up and go back to other projects. i did 2 $Iron the first 24hrs idk if its good or not….lets see after a week

  4. My node is up and running on mainnet and I have it setup with the miners:pools:start and can connect from hive os to my node. None of the shares get accepted though. Got no issues pool mining so don't know what the deal is. Are you having any issues solo mining to your node?

  5. Hey Thank you for getting me on mainnet. I about didn't catch I was still on testnet! Hey so I'm using BZ miner with my graphics card to mine to flexpool. I remember the original client miner used a processor. soooooo. Im running the processor miner too with "ironfish miners:start" is this productive or a waste of time?

  6. I dowloaded the node yesterday via your prior vid. Just checked and i am on the mainnet. But as usual you helped me cause I didn't know how to get my keys. Been mining for bout a day so far and have 1.47 iron in my wallet. Sure hope it comes in at a great starting price and after does not tank so this is all worth it. BTW. I'm using BZMINER on windows and my 2070 super and 1080 ti cards will not take the core and memory lock settings. Going to try LOLMINER and see if that is better as they worked fine on kaspa

Leave a Reply

Your email address will not be published. Required fields are marked *