v2.1.1

v2.1.1

v2.1.0

v2.1.0 Release Notes

v2.1.0 is a MANDATORY release!

This release is MANDATORY because it has changes to our reward system and a new protocol that will be enforced when we reach block 515000.

• Finished xcb integration.

• bitcoin_qt update.

• Masternode new collateral is 10,000 LYTX and will take effect when we reach block 510000.

• New rewards are 60% maxnode, 20% masternode and 20% staking. It will take effect when we reach block 515000.

• New checkpoints and code cleanup.

MacOS will be added soon.

How to Upgrade Wallets

Windows: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is located in %APPDATA%\Lytix\wallet.dat by default. Stop any running clients. Select the *.exe that matches your operating system (32-bit or 64-bit) and install in the default location. The new binary will start and begin to synchronize.

Linux: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is normally located in ~/.lytix/wallet.dat. Stop any running clients and select the proper binary for your distribution. Untar and unzip the binary and simply copy them over to the /usr/local/ directory as sudo cp -r lytix-2.1.0/* /usr/local Start the qt wallet by running lytix-qt or the daemon by running lytixd.

How to Upgrade Masternodes

Upgrade the client wallet first that holds you masternode.conf configuration using the procedures above in How to Upgrade Wallets.

Once completed go to the masternode and stop the daemon. Upgrade following the method described above. Restart the daemon. It may be necessary to re-activate the masternode. If the masternode goes missing simply go to the client wallet and re-activate the missing masternode.

How to Upgrade Maxnodes

Upgrade the client wallet first that holds you maxnode.conf configuration using the procedures above in How to Upgrade Wallets.

Once completed go to the maxnode and stop the daemon. Upgrade following the method described above. Restart the daemon. It may be necessary to re-activate the maxnode. If the maxnode goes missing simply go to the client wallet and re-activate the missing maxnode.

v2.0.3

v2.0.3 Release Notes

v2.0.3 is an OPTIONAL release

This release has recent checkpoints and the correct checkpoint for the chain split that occurred at block 312987. It should help keep your nodes on the right chain. Packages have been updated to a more recent Qt as well. We no longer need different Mac OSX builds after this release. This release also has the new branding with the new logo and motto.

Bug Fixes

1. Fixed the green synch icon in the GUI wallet to show enabled after masternodes synch properly.

2. Fixed the issues with different builds for Mac OSX Mojave and below. Fixed the pink outlines and background that shows up sometimes in Mojave builds.

3. Fixed ban crash in the wallet for adding banned nodes manually

Enhancements

1. Added log viewer in the Tools > Debug Console > Logs (port over from C++Kitty's work). Shows 25 logs at a time and cycles through the debug.log file to give you a view into it from the GUI.

2. More up to date depends packages. Qt upgraded, as well as several other packages that are used in the build process.

How to Upgrade Wallets

Windows: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is located in %APPDATA%\Lytix\wallet.dat by default. Stop any running clients. Select the *.exe that matches your operating system (32-bit or 64-bit) and install in the default location. The new binary will start and begin to synchronize.

Mac OSX Mojave: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is located in the ~/Library/Application Support/Lytix directory. Stop any running clients and select the Lytix-2.0.3-Mac-OSX-Mojave.dmg disk image. Open the image and copy the Lytix binary to the Applications folder. If it does not run at start you may have to go into the Utilities/Security & Privacy setting and click on run the Lytix binary anyway. The client should start to load and synchronize at that moment.

Mac OSX 10,x: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is located in the ~/Library/Application Support/Lytix directory. Stop any running clients and select the lytix-2.0.3-osx-unsigned.dmg disk image. Open the image and copy the Lytix binary to the Applications folder. If it does not run at start you may have to go into the Utilities/Security & Privacy setting and click on run the Lytix binary anyway. The client should start to load and synchronize at that moment.

Linux: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is normally located in ~/.lytix/wallet.dat. Stop any running clients and select the proper binary for your distribution. Untar and unzip the binary and simply copy them over to the /usr/local/ directory as sudo cp -r lytix-2.0.3/* /usr/local Start the qt wallet by running lytix-qt or the daemon by running lytixd.

How to Upgrade Masternodes

Upgrade the client wallet first that holds you masternode.conf configuration using the procedures above in How to Upgrade Wallets.

Once completed go to the masternode and stop the daemon. Upgrade following the method described above. Restart the daemon. It may be necessary to re-activate the masternode. If the masternode goes missing simply go to the client wallet and re-activate the missing masternode.

How to Upgrade Maxnodes

Upgrade the client wallet first that holds you maxnode.conf configuration using the procedures above in How to Upgrade Wallets.

Once completed go to the maxnode and stop the daemon. Upgrade following the method described above. Restart the daemon. It may be necessary to re-activate the maxnode. If the maxnode goes missing simply go to the client wallet and re-activate the missing maxnode.

Credits

Thank you to luke, tybiboune and BioLogic for their help on the new website and the new logo featured in this release. Thank you akshaynexus for the mac app nap work and advice on some of our issues.

v2.0.1 - Stakers release

This release ignores maxsync to enable staking until we can completely clean off the 1.7.5 nodes.

Use this for your clients to stake and keep the network going so we can kill off the old nodes.

This release is OPTIONAL and the only reason you would need it is if you are going to stake with your wallet.

bootstap.dat is from August 10, 2019 10:53 AM CST

lytix_dir.tar.gz is a good chain directory you can use to hop on the right chain with your wallet.dat, lytix.conf, masternode.conf and maxnode.conf files added to it.

v2.0.0

2.0.0 Release Notes

Mandatory Release

If you are staking as then you are free to wait until close to block 300,000 before moving over.

This release contains the following enhancements:

1. Maxnodes - ability to create and manage maxnodes
2. Rewards changes
3. Removal of zLYTX

Maxnodes

Maxnode cost 100,000 LYTX to run as collateral. They will receive rewards when we get close to block 300,000 due to the changes in the rewards system we will activate with their rewards. The guide on how to create and run a maxnode is here: https://github.com/LytixChain/lytix/wiki/Maxnode-Guide

Bootstrap

If you are having trouble synching the chain you can copy the bootstrap.dat into your Lytix folder and it will synch from disk up to recently. Then it will connect to the network and get a few remaining blocks.

Procedure:

Make sure that Lytix is not running.
Make a backup of your Lytix directory or at the very least make a backup of your wallet.dat file.

Copy the bootstrap.dat to the following locations:

Windows: %APPDATA%\Lytix
MacOSX: Libraries/Application Support/Lytix
Linux: .lytix

Start the client and you will see at the bottom it will read "Synchronizing from Disk." After it completes then it will reach out to the network to complete synchronization. This may take about 5 minutes to update masternodes, sporks, etc

Thanks

Thank you to luke for his advice and testing for this release. He has put in a lot of time to help move this along.

v.1.7.5b

OPTIONAL - not needed unless you are having issues with crashing daemons

Bug fix for issue 11 - #11
Seed node changes
Wallet crash fixes, spork removals, and checkpoints added

v1.7.5

1.7.5 Release Notes

OPTIONAL Release

This release changes some of the seed nodes to the consolidated list

1. Also bans all version prior to 1.7.4 due to chain forking issues.
2. Update if you want. It is not required in any way.

Bootstrap

If you are having trouble synching the chain you can copy the bootstrap.dat into your Lytix folder and it will synch from disk up to 2/23/2019 8:04 AM CST. Then it will connect to the network and get a few remaining blocks.

Procedure:

Make sure that Lytix is not running.
Make a backup of your Lytix directory or at the very least make a backup of your wallet.dat file.

Copy the bootstrap.dat to the following locations:

Windows: %APPDATA%\Lytix
MacOSX: Libraries/Application Support/Lytix
Linux: .lytix

Start the client and you will see at the bottom it will read "Synchronizing from Disk." After it completes then it will reach out to the network to complete synchronization. This may take about 5 minutes to update masternodes, sporks, etc

Raw Block Copy

If you want the raw blocks you can use the LytixBlocks.tar or LytixBlocks.zip and copy that over the blocks directory in your Lytix folder. If you do the bootstrap you don't need to do this. This is just a different method to accomplish the same task.

v1.7.4

#MANDATORY RELEASE for ALL clients and masternodes

Critical bug fix in rewards structure for Proof of Stake

To compensate for the bug I am awarding 100 LYTX as the reward for 10,000 blocks
50 = Staker and 50 = Masternode winner

v1.7.3

v1.7.3 Release Notes

v1.7.3 is a MANDATORY release for all wallets, masternodes, servers, and seed nodes. We will implement a soft fork at block 90,000 to move to the new Proof of Stake switch over at block 100,000. If you do not upgrade your clients by that date they will be blocked by the network and all nodes running code at 1.7.3.

Please upgrade as soon as possible.

Bug Fixes

1. Implemented the Fake stake DoS fix for this vulnerability: https://medium.com/@dsl_uiuc/fake-stake-attacks-on-chain-based-proof-of-stake-cryptocurrencies-b8b05723f806

2. Fixed daemon stability in #5 thanks to Eureka's debugging. Thank you for finding that.

3. Fixed #8 so the Privacy tab loads properly when zLYTX begins at block 150,000

How to Upgrade Wallets

Windows: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is located in %APPDATA%\Lytix\wallet.dat by default. Stop any running clients. Select the *.exe that matches your operating system (32-bit or 64-bit) and install in the default location. The new binary will start and begin to synchronize.

Mac OSX Mojave: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is located in the ~/Library/Application Support/Lytix directory. Stop any running clients and select the Lytix-1.7.3-Mac-OSX-Mojave.dmg disk image. Open the image and copy the Lytix binary to the Applications folder. If it does not run at start you may have to go into the Utilities/Security & Privacy setting and click on run the Lytix binary anyway. The client should start to load and synchronize at that moment.

Mac OSX 10,x: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is located in the ~/Library/Application Support/Lytix directory. Stop any running clients and select the lytix-1.7.3-osx-unsigned.dmg disk image. Open the image and copy the Lytix binary to the Applications folder. If it does not run at start you may have to go into the Utilities/Security & Privacy setting and click on run the Lytix binary anyway. The client should start to load and synchronize at that moment.

Linux: Before you begin copy your wallet.dat to a safe location. The wallet.dat file is normally located in ~/.lytix/wallet.dat. Stop any running clients and select the proper binary for your distribution. Untar and unzip the binary and simply copy them over to the /usr/local/ directory as sudo cp -r lytix-1.7.3/* /usr/local Start the qt wallet by running lytix-qt or the daemon by running lytixd.

How to Upgrade Masternodes

Upgrade the client wallet first that holds you masternode.conf configuration using the procedures above in How to Upgrade Wallets.

Once completed go to the masternode and stop the daemon. Upgrade following the method described above. Restart the daemon. It may be necessary to re-activate the masternode. If the masternode goes missing simply go to the client wallet and re-activate the missing masternode.

Credits

Thank you to our fantastic community on discord. You all have been fantastic in helping move this release forward.

v1.7.2

Release to move past the 71,000 block

Binaries uploaded shortly