hey was I lucky! I just went to the repo to DL NFD and saw that MaWo had added NFD1.3.5 just half an hour ago
Hehe
New NFD client release nfd-client-NFD-1.3.5.zipThis is the first release which stores most objects in the embedded SQL H2 database, instead of keeping them in memory.
This version will perform an initial build of the objects tables, which on a fast machine takes about 10 minutes,
but may take longer depending on your hardware. A VPS usually needs much longer! The database size will grow
during this rescan, but after shutdown it should shrink to around 560 MB. The memory usage of the client will increase.
This version is the first version which includes a checkpoint check at every 720th block height. It's triggered during
block download. Checkpoints are hard coded blockId checks. Only blockIds and heights in the blockchain until the time of the release are recognized.
You can manually force a check by starting a scan with validation (nxt.forceScan=true and nxt.forceValidate=true) at startup.
If the check detect that you are on a fork, it will pop off all blocks until last valid one.
This version has also a rewritten UPnP component. Now it takes care about myAddress on its own. UPnP is enabled by default.
Please add nxt.enableUPnP=false to your conf/nxt.properties to disable UPnP mapping.
With this version we introduce a simple client. Please use it with caution, it's still in experimental state.
http://localhost:8876/simple.htmlOther important changes:
Blacklist peers with version older than 1.2.0.
Limit peer networking request and response sizes to prevent out of memory attacks
Insecure SSLv3 protocol disabled for API.
Improved digital good store UI.
Forced validation is disabled again.
Improved test page
http://localhost:8876/testAccess to the H2 database at runtime
http://localhost:8876/dbshell (only with nxt.enableDebugAPI=true)
Limit total number of known peers merged from NXT 1.4.10:
To prevent overloading a node with invalid peer addresses, the maximum total number of known peers is
limited to nxt.maxNumberOfKnownPeers (default 2000).
Once this number has been reached, new peer addresses are not added, and peers
that have been last connected to more than a week ago are removed from the known
peer list, provided the node has enough connected public peers, until the number
of known peers is again reduced to below nxt.minNumberOfKnownPeers (default
1000).
Also included are all new API calls, bug fixes and other improvements from NXT 1.3.5 and before.
Please see NXT changelogs for more details: