This update will force a hard fork at block # 515,000
You will also need to update your nodes by this block to the current version to continue receiving bounties as long as distribution continues.
Beside not qualifying for the remaining distribution is there a downside to transacting w/V4.0e as I've not had success w/Ver 5.2 on Win7/64 showing assets (the decimal for assets in the dashboard simply flashes and all Assets listings spins endlessly).
I also just reconfirmed the behaivor w/v5.2 that I reported in an earlier post and now can see that Forging tries to kick-in when logged-in with passphrase but continues to exhibit the java error shown in my previous posted here
https://bitcointalk.org/index.php?topic=823785.msg13044883#msg13044883.. so for me (and presumably 18 of 24 peers, all PC, reported in my client still on V4.0e) V5.2 is a non-starter. I'm wondering if the 5 PC peers on V5.2 and 1 PC peer on V5.3 reported in my client can see assets, and also what v5.3 is about.
4.0e and versions older than 4.0e will be on an own fork after block 515000. We already informed all exchanges to upgrade to the newest horizon version.
This means, if you create a transaction with a version older than v5.2 after block 515000, then this transaction will not be valid for clients >= v5.2.
The transaction is thrown away and your node gets blacklisted. As example it will be not possible for you to send HZ to an exchange after block 515000 with a version less than v5.2.
Could you please try out the public node
http://eu3.woll-e.net:7776/index.html ?
Do you still have issues with this version?
I can see assets with my nodes. Sometimes they not show up, but after a reload I see them.
v5.3 will be the next version. Usually I test new versions some days or weeks on mainnet. You have seen one of my nodes which is already running version v5.3.