Before infernoman went to sleep he was very sure the short one is the correct one. Why dont those miners running on long, just stop until the short gets ahead?
he is the guy who put the code together, so I tend to believe he is correct
Be great if those miners who are not running on the short chain https://chainz.cryptoid.info/crw/#!extraction just stopped mining. I am offering a bounty for lost funds.
Topic: [ANN][CRW] CROWN (SHA256) | Platform | Governance | Systemnodes | Masternodes | - page 151. (Read 317079 times)
February 08, 2017, 02:35:21 PM
February 08, 2017, 02:32:13 PM
Both my test setup as well as mergemining are on proper fork (from the discussion here and verified by tx and txid to c-cex) .. Anything I can do to help smooth out this fork?
Yes you can help and everyone who is on the short chain, can you guys pls put more hash so we can surpass the 1.3th s which is being thrown currently on the long chain?
That would be appreciated!
There more like 905.6 TH/s on the long chain... that is a lot of miners. which is why, IMO, shouldn't it be the correct one? My pool has CRW off or it's be another 2-300TH....
February 08, 2017, 02:28:41 PM
Both my test setup as well as mergemining are on proper fork (from the discussion here and verified by tx and txid to c-cex) .. Anything I can do to help smooth out this fork?
Yes you can help and everyone who is on the short chain, can you guys pls put more hash so we can surpass the 1.3th s which is being thrown currently on the long chain?
That would be appreciated!
And those on long just stop for few hours!
February 08, 2017, 01:22:30 PM
Both my test setup as well as mergemining are on proper fork (from the discussion here and verified by tx and txid to c-cex) .. Anything I can do to help smooth out this fork?
February 08, 2017, 01:00:51 PM
I totally see where you're coming from. Traditional views are that you should always allow your users to be able to access an exchange if you fork.
Give us a couple of hours to come back to you on this. It would be a lot easier to just go with the longer chain.
I've tried several times now to get on the "short" chain but I already end up going back to the long one.... which is where the bulk of the clients are and where all the hashrate is....
What is the problem your having updating exactly?
eh? thought it was pretty plain. Everytime I sync, I go to the long chain.... even if I put in nodes from chainz explorer...
I've only just caught up with what's going on, i'm with you now and have the same issue.
February 08, 2017, 12:56:59 PM
I totally see where you're coming from. Traditional views are that you should always allow your users to be able to access an exchange if you fork.
Give us a couple of hours to come back to you on this. It would be a lot easier to just go with the longer chain.
I've tried several times now to get on the "short" chain but I already end up going back to the long one.... which is where the bulk of the clients are and where all the hashrate is....
What is the problem your having updating exactly?
eh? thought it was pretty plain. Everytime I sync, I go to the long chain.... even if I put in nodes from chainz explorer...
February 08, 2017, 12:53:18 PM
Did you notify syspool that a fork was about to happen? I got no notice of this. Is syspool even mining crowns asfaik its not even online
Can you please help us with that? It would be greatly appreciated. Seems they are not on Twitter.
Based on your tweet you are saying that syspool has not updated its daemon and they are causing your fork? But have you even been to syspool recently? It's not even online because sys is merge mined with btc and the pool is just used for our internal testing mostly when we have new features. Sigwo is the guy who manages it and I think he wanted to do major updated (pertaining to Segwit) and took it down for now, I'll have to catch up with him.
Yes your right, it's not syscoin. I can't even find the pool anymore, probably because of the reasons you mention.
February 08, 2017, 12:44:33 PM
Did you notify syspool that a fork was about to happen? I got no notice of this. Is syspool even mining crowns asfaik its not even online
Can you please help us with that? It would be greatly appreciated. Seems they are not on Twitter.
Based on your tweet you are saying that syspool has not updated its daemon and they are causing your fork? But have you even been to syspool recently? It's not even online because sys is merge mined with btc and the pool is just used for our internal testing mostly when we have new features. Sigwo is the guy who manages it and I think he wanted to do major updated (pertaining to Segwit) and took it down for now, I'll have to catch up with him.
February 08, 2017, 12:36:05 PM
Used node list and full resync bring me back to the long chain.
Did you resync the old chain or download the new chain and then resync?
I copied Inferno node list, deleted everything under crown folder and downloaded from zero
I just checked my local wallets and I seem to have the same problem.
The old chain must still be dominant
February 08, 2017, 12:15:45 PM
Used node list and full resync bring me back to the long chain.
Did you resync the old chain or download the new chain and then resync?
I copied Inferno node list, deleted everything under crown folder and downloaded from zero
February 08, 2017, 12:11:42 PM
February 08, 2017, 12:11:02 PM
Used node list and full resync bring me back to the long chain.
Did you resync the old chain or download the new chain and then resync?
February 08, 2017, 12:07:17 PM
Used node list and full resync bring me back to the long chain.
February 08, 2017, 12:04:30 PM
I totally see where you're coming from. Traditional views are that you should always allow your users to be able to access an exchange if you fork.
Give us a couple of hours to come back to you on this. It would be a lot easier to just go with the longer chain.
I've tried several times now to get on the "short" chain but I already end up going back to the long one.... which is where the bulk of the clients are and where all the hashrate is....
What is the problem your having updating exactly?
February 08, 2017, 12:03:25 PM
Did you notify syspool that a fork was about to happen? I got no notice of this. Is syspool even mining crowns asfaik its not even online
It's seems syspool dropped crw.. not sure why? They said nothing..
February 08, 2017, 12:00:42 PM
okay i will accept your view
"never support an un-intented harfork"
edit: sorry, i am still on the wrong chain. reindex did not help. will come back to this in some hours..
"never support an un-intented harfork"
edit: sorry, i am still on the wrong chain. reindex did not help. will come back to this in some hours..
You need a fresh copy of the blockchain.
February 08, 2017, 11:59:56 AM
I totally see where you're coming from. Traditional views are that you should always allow your users to be able to access an exchange if you fork.
Give us a couple of hours to come back to you on this. It would be a lot easier to just go with the longer chain.
I've tried several times now to get on the "short" chain but I already end up going back to the long one.... which is where the bulk of the clients are and where all the hashrate is....
February 08, 2017, 11:56:14 AM
Did you notify syspool that a fork was about to happen? I got no notice of this. Is syspool even mining crowns asfaik its not even online
Can you please help us with that? It would be greatly appreciated. Seems they are not on Twitter.
February 08, 2017, 11:41:52 AM
Did you notify syspool that a fork was about to happen? I got no notice of this. Is syspool even mining crowns asfaik its not even online
February 08, 2017, 11:18:25 AM
okay i will accept your view
"never support an un-intented harfork"
edit: sorry, i am still on the wrong chain. reindex did not help. will come back to this in some hours..
"never support an un-intented harfork"
edit: sorry, i am still on the wrong chain. reindex did not help. will come back to this in some hours..
Jump to: