Besides 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).
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.
Thanks MaWo for the explanation and suggestion to try the web wallet which helped me towards a resolution after observing the public node at the above link works like a charm with both Chrome and IE - displaying Assets and even the previously missing forging status/control.
Suspecting I had an incorrect distribution sure enough I found that I had downloaded the first zip in the downloads list "hz-v5.2-node.zip" NOT the standard client install "hz-v5.2.exe" or "hz-v5.2.zip".
https://github.com/NeXTHorizon/hz-source/releasesSo, using "hz-v5.2.exe" on one win7/64 machine and "hz-v5.2.zip" on another I now get full client behavior with IE11 on both - reliable asset listings and forging status/control although surprisingly Chrome on both still refuses to list assets where Chrome AND IE work fine on the above reference web wallet.
More surprising is the web wallet on the Horizons site is behaving like my local node when I was running hz-v5.2-node.zip locally, notably the non-functioning forging status/control, so an Hz Admin might want to check the web wallet installation on the HZ site.
http://nexthorizon.github.io/hz-source/