Topic: . - page 124. (Read 491737 times)
Sirs! We are near the 275000 block, and that means.. c;
Fork will occur then, and we'll be on other exchanges and hopefully bring to light what we've been working on for the past four months.
Make sure you update your wallet / node to 3.8
horizonplatform.io
Also, if you are running a forging pool, make sure you have updated!
Horizon mentioned on Bitcoin Rush (at 4.00). If you guys want a full item, he can add HZ for some donations. Must have a video or enough graphics. You can contact him on Twitter: https://twitter.com/Bitcoin_Rush
https://www.youtube.com/watch?v=YXSHdWvnyNc
https://www.youtube.com/watch?v=YXSHdWvnyNc
Hello block explorer node checker says that my node is not detected yet. I have generate hallmark, external ip address. Set up it in conf file, download wallet and sync fukk blokachain running process in screen everything is ok but my node is not visible by block explorer. my other node are up and running without problems. IP: 185.32.157.29
EDIT: another node same problem 185.32.157.27
EDIT: another node same problem 185.32.157.27
i'm still using web wallet for my hz
Use full wallet for the nodes and forging on pools.
Horizon Forging Pool at http://nhz.coin.emergate.net:8810/ has been updated to 3.8.
.. But I notice only 49/188 connected peers have updated. If you're running a node, I guess you should update!
.. But I notice only 49/188 connected peers have updated. If you're running a node, I guess you should update!
Thank you for updating
LOL. Forged a block with 10,000 HZ fees today 
10K fees?! Never seen such a large transaction before.
I think you are really a lucky man.
Horizon Forging Pool at http://nhz.coin.emergate.net:8810/ has been updated to 3.8.
.. But I notice only 49/188 connected peers have updated. If you're running a node, I guess you should update!
.. But I notice only 49/188 connected peers have updated. If you're running a node, I guess you should update!
We have decided to stop paying out nodes that are still running V 3.2 in the next 48 hours. This should help get the people who have not yet updated to update to V 3.8. This is mandatory and you can download it here: https://horizonplatform.io/wallets/
If you do not update, you will stop receiving reward bounties for your nodes!!
If you do not update, you will stop receiving reward bounties for your nodes!!
I'm running 3.8, but no payment for today. Account NHZ-C9U3-SW9X-5WFG-DCN3T. Node check OK.
EDIT: 217.17.88.5
Probably because it hasen't run today yet.
Starting today, if you have not updated your client / nodes to V3.8, you will not receive a node bounty. Update!! https://horizonplatform.io/wallets/
We have decided to stop paying out nodes that are still running V 3.2 in the next 48 hours. This should help get the people who have not yet updated to update to V 3.8. This is mandatory and you can download it here: https://horizonplatform.io/wallets/
If you do not update, you will stop receiving reward bounties for your nodes!!
If you do not update, you will stop receiving reward bounties for your nodes!!
I'm running 3.8, but no payment for today. Account NHZ-C9U3-SW9X-5WFG-DCN3T. Node check OK.
EDIT: 217.17.88.5
We have decided to stop paying out nodes that are still running V 3.2 in the next 48 hours. This should help get the people who have not yet updated to update to V 3.8. This is mandatory and you can download it here: https://horizonplatform.io/wallets/
If you do not update, you will stop receiving reward bounties for your nodes!!
If you do not update, you will stop receiving reward bounties for your nodes!!
Just fyi, ran into this bug running v3.8
Wiser man said it is an old nxt bug. But seemed to go on for quite a while on my node (last block I seen in my wallet at that time was more than 23 hours old).
EDIT:
So It seems that my blockchain got stuck on that block I was attempting to forge (block 265272, blockex ofc says someone else forged it).
Restarted multiple times. Tried to revalidate blocks, no errors there.
However, I can't seem to connect to any well known peers, am I blacklisted?
Managed to get one peer last night, however after 7 hours and more than 2gb of traffic my blockchain is still out of date. Is the db corrupted? Should I try full resync?
I am wary of deleting the db to resync entirely because, like I mentioned, I can't seem to connect.
Wiser man said it is an old nxt bug. But seemed to go on for quite a while on my node (last block I seen in my wallet at that time was more than 23 hours old).
EDIT:
So It seems that my blockchain got stuck on that block I was attempting to forge (block 265272, blockex ofc says someone else forged it).
Restarted multiple times. Tried to revalidate blocks, no errors there.
Managed to get one peer last night, however after 7 hours and more than 2gb of traffic my blockchain is still out of date. Is the db corrupted? Should I try full resync?
I am wary of deleting the db to resync entirely because, like I mentioned, I can't seem to connect.
We haven't run into this issue ourselves. I'll get one of the devs to take a look. I'd suggest a fresh install as the wallet + my node are working fine.
I did manage to get the node running in the end. However, please have someone look into it as I was told this is a bug in nxt dating back to, at least, September 2014.
Keep up the good fight
Investigating. Thanks
horizon block explorer node checker does not work. It return empty results.
Fixed.
Just fyi, ran into this bug running v3.8
Wiser man said it is an old nxt bug. But seemed to go on for quite a while on my node (last block I seen in my wallet at that time was more than 23 hours old).
EDIT:
So It seems that my blockchain got stuck on that block I was attempting to forge (block 265272, blockex ofc says someone else forged it).
Restarted multiple times. Tried to revalidate blocks, no errors there.
However, I can't seem to connect to any well known peers, am I blacklisted?
Managed to get one peer last night, however after 7 hours and more than 2gb of traffic my blockchain is still out of date. Is the db corrupted? Should I try full resync?
I am wary of deleting the db to resync entirely because, like I mentioned, I can't seem to connect.
Wiser man said it is an old nxt bug. But seemed to go on for quite a while on my node (last block I seen in my wallet at that time was more than 23 hours old).
EDIT:
So It seems that my blockchain got stuck on that block I was attempting to forge (block 265272, blockex ofc says someone else forged it).
Restarted multiple times. Tried to revalidate blocks, no errors there.
Managed to get one peer last night, however after 7 hours and more than 2gb of traffic my blockchain is still out of date. Is the db corrupted? Should I try full resync?
I am wary of deleting the db to resync entirely because, like I mentioned, I can't seem to connect.
We haven't run into this issue ourselves. I'll get one of the devs to take a look. I'd suggest a fresh install as the wallet + my node are working fine.
I did manage to get the node running in the end. However, please have someone look into it as I was told this is a bug in nxt dating back to, at least, September 2014.
Keep up the good fight
lol thank you! Something must be wrong with the OP as it shows different contents when I reload multiple times. Sometimes it loads with the "Developer verified" and client screenshot. Then I don't see the specs.
Another time it doesn't load those two, then the specs are visible
Nevermind, 2 min blocktime means we are still 8 days until the fork happens. Don't forget to update your nodes to v3.8, guys!
Another time it doesn't load those two, then the specs are visible
Nevermind, 2 min blocktime means we are still 8 days until the fork happens. Don't forget to update your nodes to v3.8, guys!
Jump to: