Nice to see the new thread has some activity.
Any plans for a 0.8.6.6 mac wallet?
Topic: [ANN][0.8.6.6] Hirocoin - X11 - Hardfork at Block 290,000 [Complete] - *New Dev* - page 9. (Read 36489 times)
September 28, 2014, 01:34:55 PM
September 25, 2014, 08:27:46 PM
That P2Pool hasn't updated to the current client and is on an invalid fork. To check the current valid block chain check the block explorer.
I 0.8.6.5 nodes are from the previous attempt to fork. In the next update with the new wallet UI I'll update the rule to only connect to 70014 Protocol (Next Version).
I 0.8.6.5 nodes are from the previous attempt to fork. In the next update with the new wallet UI I'll update the rule to only connect to 70014 Protocol (Next Version).
September 25, 2014, 03:52:29 PM
hmmmm. i see a warning, and my wallet was able to connect to this node,
and 3-4 more the same old protocol, i thought it shouldn't:
{
"addr" : "162.243.212.142:9348",
"services" : "00000003",
"lastsend" : 1411651805,
"lastrecv" : 1411651805,
"bytessent" : 1898,
"bytesrecv" : 64021,
"blocksrequested" : 0,
"conntime" : 1411651787,
"version" : 70012,
"subver" : "/Satoshi:0.8.6.4/",
"inbound" : false,
"startingheight" : 290539,
"banscore" : 0
}
and 3-4 more the same old protocol, i thought it shouldn't:
{
"addr" : "162.243.212.142:9348",
"services" : "00000003",
"lastsend" : 1411651805,
"lastrecv" : 1411651805,
"bytessent" : 1898,
"bytesrecv" : 64021,
"blocksrequested" : 0,
"conntime" : 1411651787,
"version" : 70012,
"subver" : "/Satoshi:0.8.6.4/",
"inbound" : false,
"startingheight" : 290539,
"banscore" : 0
}
The links have been updated with the windows client that includes the rule. The linux clients are correctly disconnecting from the old nodes.
September 25, 2014, 08:28:12 AM
the fork did fianally work, however the network is still weak, i have 1 network connections :/
Add the list of nodes to your conf. I have 13 connections on the block explorer, 6 on my pool and 7 on my personal wallet. Hopefully as time goes on the DNSeeder should become more efficient and automatically connecting the clients to nodes.
September 25, 2014, 08:10:23 AM
the fork did fianally work, however the network is still weak, i have 1 network connections :/
September 24, 2014, 10:59:16 PM
The hardfork is complete and the dynamic block rewards are now in place. Please remember to download the newest client in the ANN post. MintPal should be on the new client when MintPalv2 is active.
Allcoin has updated to the newest client.
Allcoin has updated to the newest client.
September 24, 2014, 12:37:06 AM
I have submitted what I hope to be the final change to the github. I had some help from Raveneye to fix the bug causing the ConnectBlock error.
If you download the client you should be able to sync correctly to the current chain that I am on along with the clients who did not upgraded as it's the longest one. The client will disconnect at block 290,000 and MintPal will allow deposits and withdrawals on the new client as soon as the move to MintPalv2 is complete.
Please update to the new client and use this in your hirocoin.conf to sync to the correct chain with the new client.
UPDATED LIST OF NODES (v. 0.8.6)
addnode=93.178.105.197
addnode=176.28.13.164
addnode=67.215.11.195
addnode=188.226.194.191
addnode=110.143.228.78
addnode=54.193.113.180
addnode=192.99.32.187
Sorry for the inconvenience
The block explorer is now runningcorrectly. It can be found here:
http://explorer.hiropool.org:3001/
There's an issue with the Insight Explorer and X11 hash function causing live block updates to cause a crash. Everything besides the latest blocks tab is functional. The correct block height is available at the top and syncs correctly.
If you download the client you should be able to sync correctly to the current chain that I am on along with the clients who did not upgraded as it's the longest one. The client will disconnect at block 290,000 and MintPal will allow deposits and withdrawals on the new client as soon as the move to MintPalv2 is complete.
Please update to the new client and use this in your hirocoin.conf to sync to the correct chain with the new client.
UPDATED LIST OF NODES (v. 0.8.6)
addnode=93.178.105.197
addnode=176.28.13.164
addnode=67.215.11.195
addnode=188.226.194.191
addnode=110.143.228.78
addnode=54.193.113.180
addnode=192.99.32.187
Sorry for the inconvenience
The block explorer is now running
http://explorer.hiropool.org:3001/
There's an issue with the Insight Explorer and X11 hash function causing live block updates to cause a crash. Everything besides the latest blocks tab is functional. The correct block height is available at the top and syncs correctly.
September 23, 2014, 01:57:40 PM
So it looks like there was an error in Hiro's original code which has caused these errors in hardforking.
I have opted for a direct halving at block 288,000 in the meantime. I'll be investigating the issue and will issue a fix when possible. I was told by Hiro that this update had been tested previously but I will test it myself.
I have opted for a direct halving at block 288,000 in the meantime. I'll be investigating the issue and will issue a fix when possible. I was told by Hiro that this update had been tested previously but I will test it myself.
please allow people time to update before forking, also what about exchanges?
September 23, 2014, 07:10:21 AM
Fork failed again at block 287500
error: {"code":-1,"message":"CreateNewBlock() : ConnectBlock failed"}
Also no exchange processing deposits now
Will be back to the original hiro version for now!
error: {"code":-1,"message":"CreateNewBlock() : ConnectBlock failed"}
Also no exchange processing deposits now
Will be back to the original hiro version for now!
September 22, 2014, 10:24:10 PM
Please git pull the new updates from https://github.com/OmarxGx/Hirocoin
I have added additional rules to disconnect from the old client beginning at block 287,500. This should ensure that the hardfork will occur regardless of where the new block is solved as the old client will be invalidated.
I have added additional rules to disconnect from the old client beginning at block 287,500. This should ensure that the hardfork will occur regardless of where the new block is solved as the old client will be invalidated.
Great... but there are now 3 versions of the code on the network sporting the version number v8.6.5 70013 (and one v8.6.5 70012):
Hiro's fork at 224000 (70012)
Omar's fork at 285550
Omar's fork at 287550
Omar's fork at 287550 w/disconnect other versions
It would be nice if you updated version numbers as you updated code, particularly when you are altering the block chain.
The rule will check for Protocol version 70013. The other versions never synced and the code also checks for chain length so we shouldn't see any issues. I will keep in mind to update the version numbers regardless each time I do make an edit.
Thanks
September 22, 2014, 03:52:52 PM
Please git pull the new updates from https://github.com/OmarxGx/Hirocoin
I have added additional rules to disconnect from the old client beginning at block 287,500. This should ensure that the hardfork will occur regardless of where the new block is solved as the old client will be invalidated.
I have added additional rules to disconnect from the old client beginning at block 287,500. This should ensure that the hardfork will occur regardless of where the new block is solved as the old client will be invalidated.
Great... but there are now 3 versions of the code on the network sporting the version number v8.6.5 70013 (and one v8.6.5 70012):
Hiro's fork at 224000 (70012)
Omar's fork at 285550
Omar's fork at 287550
Omar's fork at 287550 w/disconnect other versions
It would be nice if you updated version numbers as you updated code, particularly when you are altering the block chain.
September 22, 2014, 12:55:40 PM
Please git pull the new updates from https://github.com/OmarxGx/Hirocoin
I have added additional rules to disconnect from the old client beginning at block 287,500. This should ensure that the hardfork will occur regardless of where the new block is solved as the old client will be invalidated.
I have added additional rules to disconnect from the old client beginning at block 287,500. This should ensure that the hardfork will occur regardless of where the new block is solved as the old client will be invalidated.
Please contact exchanges to update too, deposits not clearing yet (more than 12 hours now!)
September 22, 2014, 11:53:46 AM
Please git pull the new updates from https://github.com/OmarxGx/Hirocoin
I have added additional rules to disconnect from the old client beginning at block 287,500. This should ensure that the hardfork will occur regardless of where the new block is solved as the old client will be invalidated.
I have added additional rules to disconnect from the old client beginning at block 287,500. This should ensure that the hardfork will occur regardless of where the new block is solved as the old client will be invalidated.
September 22, 2014, 11:08:35 AM
It looks like ConnectBlock is passing a pointer to the current block index to GetBlockValue.
CreateNewBlock is passing a pointer to the previous block index to GetBlockValue.
This is causing them to generate different coinbase amounts, and ConnectBlock is rejecting the block created by CreateNewBlock.
CreateNewBlock is passing a pointer to the previous block index to GetBlockValue.
This is causing them to generate different coinbase amounts, and ConnectBlock is rejecting the block created by CreateNewBlock.
September 22, 2014, 10:51:33 AM
A new windows wallet will need to be compiled to allow resyncing to the current network.
The linux daemon will sync correctly using -reindex.
The linux daemon will sync correctly using -reindex.
September 22, 2014, 10:44:21 AM
New version stuck on block 285550 with error:
error: {"code":-1,"message":"CreateNewBlock() : ConnectBlock failed"}
error: {"code":-1,"message":"CreateNewBlock() : ConnectBlock failed"}
+1, reindex doesn't help
where's working block explorer?
any valid seednode ?
debug.log:
CreateNewBlock(): total size 1962
ERROR: ConnectBlock() : coinbase pays too much (actual=13400000000 vs limit=12500000000)
September 22, 2014, 06:23:06 AM
I forgot that I had some Hiro , time to update the wallet , I hope price will bounce back.
September 22, 2014, 12:52:51 AM
The exchanges had updated already. I have confirmation from MintPal, Poloniex and Allcoin.
Suchpool said that they were updating to the new source in a message to me but apparently they did not.
Suprnova is the only other major pool that has not responded to update.
Suchpool said that they were updating to the new source in a message to me but apparently they did not.
Suprnova is the only other major pool that has not responded to update.
September 22, 2014, 12:50:31 AM
It seems that pools did not update in time for the hardfork. Suchpool and Suprnova I can confirm were not on the correct version as they are continuing to solve blocks.
Please git pull from the latest source. The hardfork has been pushed back once again to block 287,500.
You will have to start the daemon with the -reindex option to sync correctly.
Please git pull from the latest source. The hardfork has been pushed back once again to block 287,500.
You will have to start the daemon with the -reindex option to sync correctly.
What about exchanges? we need to exchange coins for our miners, this is not gonna work unless there is general consensus!
September 21, 2014, 11:53:38 PM
It seems that pools did not update in time for the hardfork. Suchpool and Suprnova I can confirm were not on the correct version as they are continuing to solve blocks.
Please git pull from the latest source. The hardfork has been pushed back once again to block 287,500.
You will have to start the daemon with the -reindex option to sync correctly.
Please git pull from the latest source. The hardfork has been pushed back once again to block 287,500.
You will have to start the daemon with the -reindex option to sync correctly.
Jump to: