The node bounty script stores the uptime with your ip address, so if you use a dynamic dns service and your ip changes, your uptime is lost.
Topic: . - page 52. (Read 491783 times)
I was using hz-v3.9.2-node but it had no option to "stake" or "mint" type of thing.
So I went to get hz-v3.9.2 and found latest is hz-v4.0e but that too had no staking/minting.
So now I tried hz-v3.9.2 andf that too does not have it.
So how does one go about it now?
Once upon a time one of my machines did have under logout an option to logout leaving the thing staking, but none of these three versions show that anymore.
ALso once upon a time there was a button to turn on staking, but I vaguely recally something about that being removed from the public nodes version, which is why I went for the non-node versions but none of them has it anymore.
Is there no staking / minting (making blocks) anymore or what?
Also, can you enter hostname (host.domain.tld) instead of IP address when making hallmark?
-MarkM-
So I went to get hz-v3.9.2 and found latest is hz-v4.0e but that too had no staking/minting.
So now I tried hz-v3.9.2 andf that too does not have it.
So how does one go about it now?
Once upon a time one of my machines did have under logout an option to logout leaving the thing staking, but none of these three versions show that anymore.
ALso once upon a time there was a button to turn on staking, but I vaguely recally something about that being removed from the public nodes version, which is why I went for the non-node versions but none of them has it anymore.
Is there no staking / minting (making blocks) anymore or what?
Also, can you enter hostname (host.domain.tld) instead of IP address when making hallmark?
-MarkM-
I set up a repository containing the language files for 5.0
Any help with fixing missing translations is appreciated
https://github.com/NeXTHorizon/hz-locales
Any help with fixing missing translations is appreciated
https://github.com/NeXTHorizon/hz-locales
Hello, everyone! After what seems to be months of coding, checking, verifying and bug-chasing (sigh), my automatic order-placing bot is now Good Enough For Live! For its first Asset, HZMMNXTT, I've already changed the [PRE-ANN] to [ANN] and updated the OP. HZMMNXTT is now firmly tied to both MMNXT's bid-ask on the Nxt and the last-trade NXT/HZ ratios!
I invite you to read HZMMNXTT's new [ANN] here. And if you're so inclined, buy some.
Thanks!
I invite you to read HZMMNXTT's new [ANN] here. And if you're so inclined, buy some.
Thanks!
no complaints about node bounty today, so everyone is happy?
everything is perfect, I love the new node information in the message
good to hear that, I added it specifically for you
no complaints about node bounty today, so everyone is happy?
everything is perfect, I love the new node information in the message
Thank you This is great improvement. If i update nodes to 4.0e then I will must update to 5.0 in future?
I think no,
sometime all must upgrade to V5, whether V3.9.2 or V4.0e
Can someone who used version 4.0 can confirm that no more blokchain rescan while daemon is up and running?
See here
Code:
2015-08-03 11:22:36 INFO: nhz.debugTraceLog = "nhz-trace.csv"
2015-08-03 11:22:36 INFO: Genesis block already in database
2015-08-03 11:22:36 INFO: Last block height: 413166
2015-08-03 11:22:36 INFO: nhz.forceScan = "false"
2015-08-03 11:22:37 INFO: Started API server at 127.0.0.1:7776
2015-08-03 11:22:37 INFO: Started peer networking server at 0.0.0.0:7774
2015-08-03 11:22:37 INFO: Initialization took 4 seconds
2015-08-03 11:22:37 INFO: Horizon server NHZ V4.0e started successfully.
Thank you This is great improvement. If i update nodes to 4.0e then I will must update to 5.0 in future?
Can someone who used version 4.0 can confirm that no more blokchain rescan while daemon is up and running?
See here
Code:
2015-08-03 11:22:36 INFO: nhz.debugTraceLog = "nhz-trace.csv"
2015-08-03 11:22:36 INFO: Genesis block already in database
2015-08-03 11:22:36 INFO: Last block height: 413166
2015-08-03 11:22:36 INFO: nhz.forceScan = "false"
2015-08-03 11:22:37 INFO: Started API server at 127.0.0.1:7776
2015-08-03 11:22:37 INFO: Started peer networking server at 0.0.0.0:7774
2015-08-03 11:22:37 INFO: Initialization took 4 seconds
2015-08-03 11:22:37 INFO: Horizon server NHZ V4.0e started successfully.
today the amount is 482.92546181 per node, 1272 nodes total and 214 transactions
Transparency is needed
thanks
How about, when the "Last Payment" time will be updated AFTER the payment was successfully sent?
It's happened again: no payment and the "Next Payment" counter was adapted.
It's happened again: no payment and the "Next Payment" counter was adapted.
that is intentional and changing this would require a rewrite of big parts of the bounty system.
I'm currently replaying today's transactions and I fixed another bug that prevented them from being sent in the first place.
today the amount is 482.92546181 per node, 1272 nodes total and 214 transactions
off-by-one errors possible because I pulled this from a debug script that didn't need to give perfect values at the time it was written, I'm just trying to improve transparency.
edit: all transactions sent.
So you can confirm that payment per node for 01.08.2015 and 31.07.2015 was 314HZ (you paid 628HZ per node in the lastest payment)? On 30.07.2015 it was around 600HZ.
yes. 314.40237421 per node on 01.08., doubled for each node that should have gotten a payment on 31.07.
fixed a bug and sent all transactions out again.
please message me with details (account#) if you did not receive you node bounty.
please message me with details (account#) if you did not receive you node bounty.
I do not want to annoy, the replay was noly for one day, but two missed.
payments from both days were included in the replay, as they would have been in the normal payout
So you can confirm that payment per node for 01.08.2015 and 31.07.2015 was 314HZ (you paid 628HZ per node in the lastest payment)? On 30.07.2015 it was around 600HZ.
is the node bounty script open source?
it is not, and we are not planning to make it public.
Jump to: