.

[Nxtblg]

A new HZng release v3.9.2 is available at bitbucket https://bitbucket.org/MattWo/hz-nxtgui/downloads
It's based on hz-v3.9.2.  https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v3.9.2  (announcement coming soon)

HZng - Horizon core with a Nxt GUI - is a personal project. It's not an official hz client, but is correctly recognized  by the node bounty program of HZ.
You will get payments for running a hallmarked public HZng node.

Please report bugs related to HZng on bitbucket:
https://bitbucket.org/MattWo/hz-nxtgui/issues?status=new&status=open

Thanks, MaWo.

[1714824488]

1714824488

[1714824488]

1714824488

[tiker]

Is there any list what's new in version 3.9.2 comparing with 3.9.1?

There was a description of what's new on the release page: https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v3.9.2

There is also a .txt file in the ChangeLog directory inside the .zip files with the same information.

[UrsaMajorisBeta]

Page 102, glad to see Horizon moving forward

[pharesim]

Reminder:
You have to update your nodes to 3.9.2 to keep getting the node bounty.
You won't need to follow the 4.0 update then, 3.9.2 will stay the official version until the 5.0 hard fork.

[Nxtblg]

There was a description of what's new on the release page: https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v3.9.2

Under the hood classes were renamed back to Nxt class naming convention. This makes the source code more Nxt compatible and improves maintenance and code merges.

And that change brings up a question: is the API going to be changed too?

From: ...:7776/nhz?... to: ...:7776/nxt?... <- Is this change in the works?

[MaWo]

There was a description of what's new on the release page: https://github.com/NeXTHorizon/hz-source/releases/tag/hz-v3.9.2

Under the hood classes were renamed back to Nxt class naming convention. This makes the source code more Nxt compatible and improves maintenance and code merges.

And that change brings up a question: is the API going to be changed too?

From: ...:7776/nhz?... to: ...:7776/nxt?... <- Is this change in the works?

API URL and configuration settings were preserved for backward compatibility.

[acha]

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

[MaWo]

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?

[sokol]

How often script checking nodes? How long to wait before the node is displayed here ?

[sokol]

Is it possible to take full advantage of http://api.nhzcrypto.org:7776?

[MaWo]

Is it possible to take full advantage of http://api.nhzcrypto.org:7776?

HZ v4.0 is still beta/experimental. You should be aware of this, but I don't expect any problems.
If you experience unusual/strange things then please report them.

[Emerger]

Noticed I wasn't getting any peers then found in my nhz-default.properties, two settings starting with nxt: nxt.maxNumberOfKnownPeers and nxt.minNumberOfKnownPeers

I changed it to: nhz.maxNumberOfKnownPeers & nhz.minNumberOfKnownPeers

.. and working again. Don't know if this was an earlier mistake I made but this wasn't a problem with 3.9.1

(I tend to re-use same config settings so didn't notice straight away)

[MaWo]

Noticed I wasn't getting any peers then found in my nhz-default.properties, two settings starting with nxt: nxt.maxNumberOfKnownPeers and nxt.minNumberOfKnownPeers

I changed it to: nhz.maxNumberOfKnownPeers & nhz.minNumberOfKnownPeers

.. and working again. Don't know if this was an earlier mistake I made but this wasn't a problem with 3.9.1

(I tend to re-use same config settings so didn't notice straight away)

It was an issue with 3.9.1, but with 3.9.2 both prefixes will work.

[Emerger]

Noticed I wasn't getting any peers then found in my nhz-default.properties, two settings starting with nxt: nxt.maxNumberOfKnownPeers and nxt.minNumberOfKnownPeers

I changed it to: nhz.maxNumberOfKnownPeers & nhz.minNumberOfKnownPeers

.. and working again. Don't know if this was an earlier mistake I made but this wasn't a problem with 3.9.1

(I tend to re-use same config settings so didn't notice straight away)

It was an issue with 3.9.1, but with 3.9.2 both prefixes will work.

Strange, because I had this issue with both my servers. Both were updated to 3.9.1 first day and have run fine, but both had peer problem with 3.9.2 until I changed to prefix of those two settings to nhz.

Thanks

[acha]

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?

Of course. Replaced nhz-default.properties v3.9.1  from it's conf folder on nhz-default.properties in conf folder v3.9.2. Folders v3.9.1 and v3.9.2 different - folder v3.9.1 and folder v3.9.2 respectively. The fact that the time is not changed, it freezes after the transition to v3.9.2. If an error in the configuration file, node checker sees the node but thus there is a countdown. May be reconfigure nodes? What's the point...

[acha]

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?

Of course. Replaced nhz-default.properties v3.9.1  from it's conf folder on nhz-default.properties in conf folder v3.9.2. Folders v3.9.1 and v3.9.2 different - folder v3.9.1 and folder v3.9.2 respectively. The fact that the time is not changed, it freezes after the transition to v3.9.2. If an error in the configuration file, node checker sees the node but thus there is a countdown. May be reconfigure nodes? What's the point...

Back on one node on v3.9.1 - has begun the countdown. What's the problem?

[MaWo]

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?

Of course. Replaced nhz-default.properties v3.9.1  from it's conf folder on nhz-default.properties in conf folder v3.9.2. Folders v3.9.1 and v3.9.2 different - folder v3.9.1 and folder v3.9.2 respectively. The fact that the time is not changed, it freezes after the transition to v3.9.2. If an error in the configuration file, node checker sees the node but thus there is a countdown. May be reconfigure nodes? What's the point...

Back on one node on v3.9.1 - has begun the countdown. What's the problem?

Just for clarification, I don't know whether I understood you correctly:
You should not modify the file nhz-default.properties, instead create a nhz.properties file with only the
properties you need to change, and set them there. The values in nhz.properties override those in nhz-default.properties.
The same applies for logging-default.properties. Create a logging.properties file and make your changes there.

When you extract a new release, you only need to move or copy your database directory nhz_db/
and your custom config files
conf/nhz.properties
conf/logging.properties

[cbkr]

Back on one node on v3.9.1 - has begun the countdown. What's the problem?

The issue has been fixed; please allow up to an hour for the data to be updated.

[acha]

Something I do not understand... Yesterday changed on the nodes version to 3.9.2 and Upime Until Next Payou has stopped, there is no payment from all nodes. But one node has not changed, the version is 3.9.1 - payment came. Is something wrong?

Did you copy the configuration files with your hallmarks?

Of course. Replaced nhz-default.properties v3.9.1  from it's conf folder on nhz-default.properties in conf folder v3.9.2. Folders v3.9.1 and v3.9.2 different - folder v3.9.1 and folder v3.9.2 respectively. The fact that the time is not changed, it freezes after the transition to v3.9.2. If an error in the configuration file, node checker sees the node but thus there is a countdown. May be reconfigure nodes? What's the point...

Back on one node on v3.9.1 - has begun the countdown. What's the problem?

Just for clarification, I don't know whether I understood you correctly:
You should not modify the file nhz-default.properties, instead create a nhz.properties file with only the
properties you need to change, and set them there. The values in nhz.properties override those in nhz-default.properties.
The same applies for logging-default.properties. Create a logging.properties file and make your changes there.

When you extract a new release, you only need to move or copy your database directory nhz_db/
and your custom config files
conf/nhz.properties
conf/logging.properties

Working))) On all versions I've always modified the nhz-default.properties... Thank you very much!!!

[Nxtblg]

API URL and configuration settings were preserved for backward compatibility.

Thanks again, MaWo. In my case, not preserving backward compatibility would have involved a little more debugging (sigh).