Hello FARO
Please check your wallet inbox ("Messages").
Thx a lot!
Topic: . - page 51. (Read 491783 times)
I am having difficulty getting the online wallet connected to the server. I have been having trouble for a few days. I am wondering is there something wrong with the platform right now?
Thanks
Thanks
It works for me. The online wallet use http://api.nhzcrypto.org:7776/nhz as backend.
Is it possible that you are behind a firewall and/or proxy which blocks http traffic to ports like 7776?
I need a reliable, 24/7-always-on HZ nrs with open API.
https://account.horizonplatform.io:7776/test does not work
http://nexthorizon.github.io:7776/test does not work
What is the address of the webwallet NRS?
The load will be tiny, just for my new countdown server.
Which public api can I query?
I'm using this one:
http://api.nhzcrypto.org:7776/test
I need a reliable, 24/7-always-on HZ nrs with open API.
https://account.horizonplatform.io:7776/test does not work
http://nexthorizon.github.io:7776/test does not work
What is the address of the webwallet NRS?
The load will be tiny, just for my new countdown server.
Which public api can I query?
Something statistics about the node bounties of the last 2 weeks
Explanations:
- Amount_per_node, #Nodes_payed from blockchain
- Total_node_bounties: (Amount_per_node * #Nodes_payed)
- Remaining_HZ: Total_node_bounties / 0,5%
- Distributed_HZ: 1,000,000,000 - Remaining_HZ
- Stakeholder_Bounty: Distributed_HZ * 10% / 365
- Other_Bounty: Distributed_HZ(act) - Distributed_HZ(prev.) - Stakeholder_Bounty(prev) - Total_node_bounties(prev)
If value is negative: perhaps not all Distributed_HZ gets Stakeholder_Bounty?
EDIT: If the "other bounties" remain at this size, the distribution is completed in about 2-3 months
| Payment_date | Amount_per_node | #Nodes_payed | Total_node_bounties | Remaining_HZ | Distributed_HZ | Stakeholder_Bounty | Other_Bounty | Note |
| 25-07-15 | 526.38568 | 1227 | 645,875 | 129,175,046 | 870,824,954 | 238,582 | 0 | |
| 26-07-15 | 585.54878 | 1096 | 641,761 | 128,352,293 | 871,647,707 | 238,808 | -61,704 | |
| 27-07-15 | 556.44826 | 1146 | 637,690 | 127,537,941 | 872,462,059 | 239,031 | -66,218 | |
| 28-07-15 | 447.11158 | 1417 | 633,557 | 126,711,422 | 873,288,578 | 239,257 | -50,201 | |
| 29-07-15 | 661.9737 | 951 | 629,537 | 125,907,398 | 874,092,602 | 239,477 | -68,790 | |
| 30-07-15 | 573.32467 | 1091 | 625,497 | 125,099,443 | 874,900,557 | 239,699 | -61,060 | |
| 01-08-15 | 314.40237 | 1973 | 620,316 | 124,063,175 | 875,936,825 | 239,983 | 171,072 | replayed transaction for 2 days |
| 02-08-15 | 482.92546 | 1272 | 614,281 | 122,856,237 | 877,143,763 | 240,313 | 346,640 | replayed transaction for 1 days |
| 03-08-15 | 465.9214 | 1310 | 610,357 | 122,071,407 | 877,928,593 | 240,528 | -69,764 | first transaction with detailed node information |
| 04-08-15 | 391.83203 | 1444 | 565,805 | 113,161,090 | 886,838,910 | 242,970 | 8,059,431 | Big dev bounties??? |
| 05-08-15 | 352.96779 | 1509 | 532,628 | 106,525,679 | 893,474,321 | 244,787 | 5,826,636 | Big dev bounties??? |
| 06-08-15 | 333.80953 | 1116->1569 | 523,747 | 104,749,431 | 895,250,569 | 245,274 | 998,833 | seams there are some missing payments, 1569 is the approximated node count |
| 07-08-15 | 297.48466 | 1732 | 515,243 | 103,048,686 | 896,951,314 | 245,740 | 931,723 |
Explanations:
- Amount_per_node, #Nodes_payed from blockchain
- Total_node_bounties: (Amount_per_node * #Nodes_payed)
- Remaining_HZ: Total_node_bounties / 0,5%
- Distributed_HZ: 1,000,000,000 - Remaining_HZ
- Stakeholder_Bounty: Distributed_HZ * 10% / 365
- Other_Bounty: Distributed_HZ(act) - Distributed_HZ(prev.) - Stakeholder_Bounty(prev) - Total_node_bounties(prev)
If value is negative: perhaps not all Distributed_HZ gets Stakeholder_Bounty?
EDIT: If the "other bounties" remain at this size, the distribution is completed in about 2-3 months
Hello once again. 
I've changed a third Asset powered by my market-making bot from [PRE-ANN] to [ANN]: HZNxtty Like HZSuperNET and HZMMNXTT, HZNxtty's bid-ask is firmly tied to both Nxttycoin's bid-ask on the Nxt AE and the last-trade NXT/HZ ratios on Poloniex.
If you're interested, check out HZNxtty's new [ANN] here. And if you're so inclined, feel free to buy some.
One again, thanks.
I've changed a third Asset powered by my market-making bot from [PRE-ANN] to [ANN]: HZNxtty Like HZSuperNET and HZMMNXTT, HZNxtty's bid-ask is firmly tied to both Nxttycoin's bid-ask on the Nxt AE and the last-trade NXT/HZ ratios on Poloniex.If you're interested, check out HZNxtty's new [ANN] here. And if you're so inclined, feel free to buy some.
One again, thanks.
Hey, thanks for enabling my Assets.
Hello again, everyone! I've changed another Asset powered by my market-making bot from [PRE-ANN] to [ANN]: HZSuperNET. Like HZMMNXTT, HZSuperNET's bid-ask is firmly tied to both SuperNET's bid-ask on the Nxt AE and the last-trade NXT/HZ ratios on Poloniex.
If you're interested, check out HZSuperNET's new [ANN] here. And if you're so inclined, feel free to buy some.
Again, thanks.
If you're interested, check out HZSuperNET's new [ANN] here. And if you're so inclined, feel free to buy some.
Again, thanks.
Enabled on http://hzxchange.net
Happy trading!
Hello again, everyone! I've changed another Asset powered by my market-making bot from [PRE-ANN] to [ANN]: HZSuperNET. Like HZMMNXTT, HZSuperNET's bid-ask is firmly tied to both SuperNET's bid-ask on the Nxt AE and the last-trade NXT/HZ ratios on Poloniex.
If you're interested, check out HZSuperNET's new [ANN] here. And if you're so inclined, feel free to buy some.
Again, thanks.
If you're interested, check out HZSuperNET's new [ANN] here. And if you're so inclined, feel free to buy some.
Again, thanks.
Is there any problem with detect new nodes on 4.0 version? I made some new nodes yesterday and today they are not detected.
No, I had no problems.
If you give me the IP's, I can check the hallmarks.
Today is ok.
Is there any problem with detect new nodes on 4.0 version? I made some new nodes yesterday and today they are not detected.
No, I had no problems.
If you give me the IP's, I can check the hallmarks.
BIG CONGRATS to the 4.0. I had no time for it yet ... but for
a reason. Here comes SSP: Shameless Self Promotion
! assetgraphs.py is born !
my 1st hackathon participation in
nxthacks 2015 - vote now
retweet: https://twitter.com/altsheets/status/628005223466991616
and https://twitter.com/altsheets/status/628018551417384960 thx!
More info will be in my assetparser.py thread - now it gets ... visual
VOTE FOR ME - 4 days left to vote. 6 participants, 6 great projects!
My submitted epic: http://altsheets.ddns.net/assetgraphs yiehah!
:-)
my 1st hackathon participation in
nxthacks 2015 - vote now
retweet: https://twitter.com/altsheets/status/628005223466991616
and https://twitter.com/altsheets/status/628018551417384960 thx!
More info will be in my assetparser.py thread - now it gets ... visual
VOTE FOR ME - 4 days left to vote. 6 participants, 6 great projects!
My submitted epic: http://altsheets.ddns.net/assetgraphs yiehah!
:-)
And the best news, and why this is HZ-related after all:
I can adapt this new tool to Horizon soon! If you want to ...
That forging indicator is (always has been, but not really sure if it still is because i'm not involved in the build-process any more) commented out in the node version. The normal wallet always had it.
See html/ui/html/sidebar.html line 16
See html/ui/html/sidebar.html line 16
There is no mention of forging on any of the three versions I mentioned previously.
I do recall having seen it once long ago, but that might have been before creating any hallmarks.
All my machines now have hallmarks could that be disabling forging somehow?
I don't know where I read that that forging indicator had been removed from the node version.
But I had hoped/expected to see it by moving over to the none node versions.
But that isn't happening.
I do have in my nhz.properties
in all cases. (I copy over the nhz.properties as well as the database so all three versions have same of both (although the version 4 updated the database to a new type or something it started with same database.))
-MarkM-
I do recall having seen it once long ago, but that might have been before creating any hallmarks.
All my machines now have hallmarks could that be disabling forging somehow?
I don't know where I read that that forging indicator had been removed from the node version.
But I had hoped/expected to see it by moving over to the none node versions.
But that isn't happening.
I do have in my nhz.properties
Code:
# Disable Forging? (if set to true)
nhz.dontForge=false
in all cases. (I copy over the nhz.properties as well as the database so all three versions have same of both (although the version 4 updated the database to a new type or something it started with same database.))
-MarkM-
Jump to: