Topic: . - page 94. (Read 491737 times)
Nice to see volume growing and price growing a bit to.
...Any special reason for this?
Some people wanted to bring back the IRC channel - So I'll try and keep a presence in there more often.
https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23Horizonplatform
https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23Horizonplatform
Hi all.
Nice to see volume growing and price growing a bit to.
Any recent news about hzxchange asset? When can we think it will begin to work and to pay fee?
Nice to see volume growing and price growing a bit to.
Any recent news about hzxchange asset? When can we think it will begin to work and to pay fee?
Testing is complete and we are just finalizing the release...
Why node checher returns Hallmark Not Submitted By Node (Show) ?
Since i have a halmark valid and at in nhz-default.properties?
Since i have a halmark valid and at in nhz-default.properties?
Check an IP (example 81.169.133.57 ) and you will get "Hallmark Not Submitted By Node" but hallmark is submitted.
It's only a message. We are looking into it to fix that message return.
When the NodeChecker API will be available again?
e.g.
https://explorer.horizonplatform.io/api.php?page=nodecheck&nodeAddress=78.138.90.142
e.g.
https://explorer.horizonplatform.io/api.php?page=nodecheck&nodeAddress=78.138.90.142
Try here
https://explorer.horizonplatform.io/?page=nodecheck
I've seen this, but I mean the API
https://explorer.horizonplatform.io/api.php?page=nodecheck&nodeAddress=78.138.90.142
Any news about the node checker json API?
Why node checher returns Hallmark Not Submitted By Node (Show) ?
Since i have a halmark valid and at in nhz-default.properties?
Since i have a halmark valid and at in nhz-default.properties?
Seems to be a typo.
For those with a different taste (mostly old NFDler), I prepared an alternative HZ client with a Nxt-like GUI.
I call it HZng. Ng is the abbreviation for Nxt GUI.
HZng based on hz-v3.9 but with the NXT GUI and not the HZ own GUI.
A 'HZng-v3.9' node is recognized correctly by the node bounty program of HZ.
You will get payments for running a hallmarked public HZng-v3.9 node.
Download HZng client:
https://bitbucket.org/MattWo/hz-nxtgui/downloads
Please report bugs related to HZng on bitbucket:
https://bitbucket.org/MattWo/hz-nxtgui/issues?status=new&status=open
HZng is a personal project. It's not part of the official hz client.
I call it HZng. Ng is the abbreviation for Nxt GUI.
HZng based on hz-v3.9 but with the NXT GUI and not the HZ own GUI.
A 'HZng-v3.9' node is recognized correctly by the node bounty program of HZ.
You will get payments for running a hallmarked public HZng-v3.9 node.
Download HZng client:
https://bitbucket.org/MattWo/hz-nxtgui/downloads
Please report bugs related to HZng on bitbucket:
https://bitbucket.org/MattWo/hz-nxtgui/issues?status=new&status=open
HZng is a personal project. It's not part of the official hz client.
Great!
It is not just a matter of different taste.
In the process of trying out the new wallet ...
First thing I notice: Downloads are shown to come from http://nhz.woll-e.net/~matthias
I suggest to put them on the main server instead.
This time, the checksums match what is given on the website. Here's what I got:
hz-v3.9.zip
MD5 Checksum: 30E456175E6C558D87928201FD94DCD3
SHA-1 Checksum: 8A317AD3B0AE1593BC7EDFB82265C07D3BE6FDBC
SHA-256 Checksum: 26A2BFA55C87FB2EB4EE6209E3DA2B525DCA84C98DAFEC2CAF84C004EA4A7591
SHA-512 Checksum: 017C4FE41B4F91987924DF97E0C6EAB50920FD8EBB9E2318865DCEF0AFB6F046CA7C1953FCA9CC6 A538F544B93D1B7B85F198AB7B8795AF0769F0A1B9EA0F310
hz-v3.9-node.zip
MD5 Checksum: 08AD6A68C358EB389A386E682BF6BAD7
SHA-1 Checksum: A5B4745B0B1D8A6BA09440DA97A47B233F2C9430
SHA-256 Checksum: 612F69882280B31B2F6442C5664D5A1F588A5F0C09F77CE7AE3764210C44E579
SHA-512 Checksum: EEC30B2D1128FB7EED38E0205FDC6008907B52E5E2E944CBE5CE8745BC5015434CAC42FA8733007 9E8BA10A727C6CF52DE29F14D5F18F64518B65D4EDFD4911B
First thing I notice: Downloads are shown to come from http://nhz.woll-e.net/~matthias
I suggest to put them on the main server instead.
This time, the checksums match what is given on the website. Here's what I got:
hz-v3.9.zip
MD5 Checksum: 30E456175E6C558D87928201FD94DCD3
SHA-1 Checksum: 8A317AD3B0AE1593BC7EDFB82265C07D3BE6FDBC
SHA-256 Checksum: 26A2BFA55C87FB2EB4EE6209E3DA2B525DCA84C98DAFEC2CAF84C004EA4A7591
SHA-512 Checksum: 017C4FE41B4F91987924DF97E0C6EAB50920FD8EBB9E2318865DCEF0AFB6F046CA7C1953FCA9CC6 A538F544B93D1B7B85F198AB7B8795AF0769F0A1B9EA0F310
hz-v3.9-node.zip
MD5 Checksum: 08AD6A68C358EB389A386E682BF6BAD7
SHA-1 Checksum: A5B4745B0B1D8A6BA09440DA97A47B233F2C9430
SHA-256 Checksum: 612F69882280B31B2F6442C5664D5A1F588A5F0C09F77CE7AE3764210C44E579
SHA-512 Checksum: EEC30B2D1128FB7EED38E0205FDC6008907B52E5E2E944CBE5CE8745BC5015434CAC42FA8733007 9E8BA10A727C6CF52DE29F14D5F18F64518B65D4EDFD4911B
nhz.woll-e.net is my server.
You can also download the binaries from github:
https://github.com/NeXTHorizon/hz-source/releases
Coinerz will change the links to github when he is back online.
In the process of trying out the new wallet ...
First thing I notice: Downloads are shown to come from http://nhz.woll-e.net/~matthias
I suggest to put them on the main server instead.
The checksums match what is given on the website. Here's what I got:
hz-v3.9.zip
MD5 Checksum: 30E456175E6C558D87928201FD94DCD3
SHA-1 Checksum: 8A317AD3B0AE1593BC7EDFB82265C07D3BE6FDBC
SHA-256 Checksum: 26A2BFA55C87FB2EB4EE6209E3DA2B525DCA84C98DAFEC2CAF84C004EA4A7591
SHA-512 Checksum: 017C4FE41B4F91987924DF97E0C6EAB50920FD8EBB9E2318865DCEF0AFB6F046CA7C1953FCA9CC6 A538F544B93D1B7B85F198AB7B8795AF0769F0A1B9EA0F310
hz-v3.9-node.zip
MD5 Checksum: 08AD6A68C358EB389A386E682BF6BAD7
SHA-1 Checksum: A5B4745B0B1D8A6BA09440DA97A47B233F2C9430
SHA-256 Checksum: 612F69882280B31B2F6442C5664D5A1F588A5F0C09F77CE7AE3764210C44E579
SHA-512 Checksum: EEC30B2D1128FB7EED38E0205FDC6008907B52E5E2E944CBE5CE8745BC5015434CAC42FA8733007 9E8BA10A727C6CF52DE29F14D5F18F64518B65D4EDFD4911B
First thing I notice: Downloads are shown to come from http://nhz.woll-e.net/~matthias
I suggest to put them on the main server instead.
The checksums match what is given on the website. Here's what I got:
hz-v3.9.zip
MD5 Checksum: 30E456175E6C558D87928201FD94DCD3
SHA-1 Checksum: 8A317AD3B0AE1593BC7EDFB82265C07D3BE6FDBC
SHA-256 Checksum: 26A2BFA55C87FB2EB4EE6209E3DA2B525DCA84C98DAFEC2CAF84C004EA4A7591
SHA-512 Checksum: 017C4FE41B4F91987924DF97E0C6EAB50920FD8EBB9E2318865DCEF0AFB6F046CA7C1953FCA9CC6 A538F544B93D1B7B85F198AB7B8795AF0769F0A1B9EA0F310
hz-v3.9-node.zip
MD5 Checksum: 08AD6A68C358EB389A386E682BF6BAD7
SHA-1 Checksum: A5B4745B0B1D8A6BA09440DA97A47B233F2C9430
SHA-256 Checksum: 612F69882280B31B2F6442C5664D5A1F588A5F0C09F77CE7AE3764210C44E579
SHA-512 Checksum: EEC30B2D1128FB7EED38E0205FDC6008907B52E5E2E944CBE5CE8745BC5015434CAC42FA8733007 9E8BA10A727C6CF52DE29F14D5F18F64518B65D4EDFD4911B
For those with a different taste (mostly old NFDler), I prepared an alternative HZ client with a Nxt-like GUI.
I call it HZng. Ng is the abbreviation for Nxt GUI.
HZng based on hz-v3.9 but with the NXT GUI and not the HZ own GUI.
A 'HZng-v3.9' node is recognized correctly by the node bounty program of HZ.
You will get payments for running a hallmarked public HZng-v3.9 node.
Download HZng client:
https://bitbucket.org/MattWo/hz-nxtgui/downloads
Please report bugs related to HZng on bitbucket:
https://bitbucket.org/MattWo/hz-nxtgui/issues?status=new&status=open
HZng is a personal project. It's not part of the official hz client.
I call it HZng. Ng is the abbreviation for Nxt GUI.
HZng based on hz-v3.9 but with the NXT GUI and not the HZ own GUI.
A 'HZng-v3.9' node is recognized correctly by the node bounty program of HZ.
You will get payments for running a hallmarked public HZng-v3.9 node.
Download HZng client:
https://bitbucket.org/MattWo/hz-nxtgui/downloads
Please report bugs related to HZng on bitbucket:
https://bitbucket.org/MattWo/hz-nxtgui/issues?status=new&status=open
HZng is a personal project. It's not part of the official hz client.
Remember to update your nodes as well as updating your wallet.
This is a mandatory update, and you will not receive your bounty payouts if you do not update.
This will take effect in 10 days.
Wallets: https://horizonplatform.io/get-started/wallets/
This is a mandatory update, and you will not receive your bounty payouts if you do not update.
This will take effect in 10 days.
Wallets: https://horizonplatform.io/get-started/wallets/
NEW HORIZON WALLET UPDATE
We’re pleased to announce the release of version 3.9 of our wallet
which fixes several user interface bugs which were in the previous release.
We’ve also decided to drop the downloadable thin wallet because we found that
people preferred to use our online wallet instead.
CLICK FOR MORE INFO AND WALLET DOWNLOAD
We’re pleased to announce the release of version 3.9 of our wallet
which fixes several user interface bugs which were in the previous release.
We’ve also decided to drop the downloadable thin wallet because we found that
people preferred to use our online wallet instead.
CLICK FOR MORE INFO AND WALLET DOWNLOAD
changelog:
Quote from: https://github.com/NeXTHorizon/hz-source/blob/master/changelogs/hz-client-3.9.changelog.txt
Sometimes a transaction got not included in a block because of to many NHZ V3.2 nodes in peers list.
Now NHZ v3.2 nodes are blacklisted. They are already on a own fork since block 275000.
Peers updated and new pool peer addresses added to wellKnownPeers. The pool addresses are updated daily
to provide a daily fresh list of peers.
Checkpoint checks during blockchain download added. Every 720th block is checked. Checkpoints are hard coded blockId checks.
Only blockIds and heights in the blockchain up to the time of the release are recognized. Disable it by setting nhz.useCheckpoints to false.
GUI bug fixes:
* Sometimes mainnet got recognized as testnet.
* There were file encoding problems for some language
* Asset exchange buy/sell input fields were always visible
* Modals opened with full list of features (advanced mode) instead to open in basic mode.
* Sometimes buttons were overlapping
Now NHZ v3.2 nodes are blacklisted. They are already on a own fork since block 275000.
Peers updated and new pool peer addresses added to wellKnownPeers. The pool addresses are updated daily
to provide a daily fresh list of peers.
Checkpoint checks during blockchain download added. Every 720th block is checked. Checkpoints are hard coded blockId checks.
Only blockIds and heights in the blockchain up to the time of the release are recognized. Disable it by setting nhz.useCheckpoints to false.
GUI bug fixes:
* Sometimes mainnet got recognized as testnet.
* There were file encoding problems for some language
* Asset exchange buy/sell input fields were always visible
* Modals opened with full list of features (advanced mode) instead to open in basic mode.
* Sometimes buttons were overlapping
Hello,
is necessary to change main folder name. previous was hz, now hz-v3.9 or even hz-v3.9-node. Is a little bit harder to upgrade VPS node. This is thing that also changed, and from now it will be used?
I think, that v3.8 on the nodes is still fully acceptable. Am I right?
is necessary to change main folder name. previous was hz, now hz-v3.9 or even hz-v3.9-node. Is a little bit harder to upgrade VPS node. This is thing that also changed, and from now it will be used?
I think, that v3.8 on the nodes is still fully acceptable. Am I right?
My preferred way to upgrade a vps is using git. I'm using screen to detach and reattach a terminal session.
initial:
Code:
git clone https://github.com/NeXTHorizon/hz-source.git
cd hz-source
./compile.sh
screen -S hzlive -L ./run.sh
CTRL-a d
upgrade to latest version:
Code:
git pull
./compile.sh
screen -rd hzlive
CTRL-C
screen -S hzlive -L ./run.sh
Jump to: