Issue

We’ve been receiving issues from a selection of the Nodium wallet users when sending transactions to other wallets on the Nodium network and the CryptoBridge latest wallet.

Explained

CryptoBridge we organised in advance to update their older receiving wallet to the latest 3.0.6 zNodium chain. (Repository is here: https://github.com/nodiumproject/zNodium) in advance for the official changeover from Nodium to zNodium (zerocoin) chain at block 50,001.

Support from the CryptoBridge in this process has been great and it has been successfully updated.

With the latest wallet on running on the latest zNodium chain, any users who don’t correctly update their older wallet to latest Zerocoin are not connecting to the correct blockchain. Payments therefore don’t go through on the network to users on zNodium ready wallets. (mostly brand new users and CryptoBridge since updated)

Solution

Safety

• Firstly, before making the changes. Do the follow (VERY IMPORTANT, otherwise can loose your coins)

1. Backup your wallet.dat. This can be done by going launching your Nodium wallet. Click ‘File’ on the toolbar followed by clicking ‘Backup wallet’. It will then lead you to a file saving option, name the file wallet
2. Before clicking save, choose where to save it wisely. Best is a backup USB. Then it will be safely stored
3. Exit the wallet

Masternode owners

You will also need to save your masternode.conf file.

1. Load %appdata% on windows startbar
2. Then look for Nodium on the applications
3. You will find your wallet info, with the masternode.conf file
4. Back this up similar fashion as above, preferably on a USB also

zNodium wallet correct installation for an upgrade from 2.3 non zerocoin wallets

1. Once backed up all your necessary files for coin recovery on new wallet. Go back to %appdata% and find the Nodium folder again
2. Delete all files within the folder, so it’s empty
3. Then download the latest zNodium wallet 3.0.6 zerocoin ready here: https://github.com/nodiumproject/Wallets
4. Unzip the .exe file to desktop
5. Click the nodium launcher then exit it.
6. Go back to %appdata% and access the nodium folder again, you will see all the wallet files appear again
7. Drag your backed up files (wallet.dat and masternode.conf) into the folder and replace the existing
8. Reload wallet
9. You will now correctly be running on the zNodium chain and transactions from then on will be correct to all other users on the 3.0.6 wallet (this includes CryptoBridge)
10. Allow to fully sync. Do not exit the wallet until
11. If you have previously sent transactions, they will now show as ‘conflicted’ if they didn’t go through. You can solve this by going to ‘wallet repair’ and clicking ‘transactions 2’ this will solve the transactions which were not appearing. This will close and auto reload your wallet, do not exit. This will recover any failed transactions back to your wallet or send to your payees. The ‘sending’ area will afterwards be changed and any ‘conflicted’ transactions will no longer appear.
    Wallet solved. All transactions in future for upgraded 2.3 to 3.0.6 users on the Nodium network will work fine from now on.

• This has been thoroughly tested amongst the Nodium developers and a selection of users with both CryptoBridge and native wallet users. Follow correctly, and your wallet will function correctly from then on.

Don’t forget

The update is mandatory for block 50,001 to be ready. If you have not correctly upgraded after then, older transactions will no longer work. It is very important for users of the older 2.3 wallet to upgrade in advance correctly to avoid the issues we’ve been having.

• The ‘Nodium’ repository will stop functioning and be also removed from Github shortly after block 50,0001: https://github.com/nodiumproject/Nodium
• Upcoming correct chain for the Zerocoin protocol upgrade is here, and wallets run on this ready in advance: https://github.com/nodiumproject/zNodium

Users new to the network

If you’re brand new to the network, and started out with the 3.0.6 wallet — Do not worry. Your wallet is working correctly and will not have the issues wrote above.

Having some issues? Not so tech savvy?

Join our ever growing Discord channel of over 2200+ members, and message on the #support channel .There’s a great group of passionate users there usually to help.

Community support

We’d like to mention a thanks to the guys in our discord page for the amazing support in this bug which has now been solved. In particular for answering the many questions and helping keep things positive in the community whilst we worked on the issue.

This is a re-post from archived Medium publications. Nodium is now working via Steemit exclusively.