|
mercSuey (OP)
|
 |
July 28, 2013, 07:01:24 AM |
|
Hi everyone, I'm relaying a message on behalf of Mullick who is away from his computer at the moment. It has been discovered that BigVern's CAP pool is forked from the main blockchain. If you're mining at www.bottlecapspool.com then you are advised to stop immediately. Erundook and Silverwolf CAP pools are on the correct chain and Mullick suggests to mine at their pools until he can get in front of his computer and finish the latest client with new nodes. He apologizes to the miners at BigVern's pool for the inconvenience. -Merc |
|
|
|
|
|
|
|
|
|
|
|
|
|
The forum was founded in 2009 by Satoshi and Sirius. It replaced a
SourceForge forum.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
mercSuey (OP)
|
|
July 28, 2013, 07:11:11 AM |
|
|
|
|
|
|
|
mercSuey (OP)
|
|
July 28, 2013, 07:26:09 AM |
|
Please spread the word if you know someone mining at BigVern's pool. Thanks.
|
|
|
|
|
|
|
|
mercSuey (OP)
|
|
July 28, 2013, 07:49:43 AM |
|
Yes, I vouch for feeleep's pools. He's a very good pool op. Thanks feeleep.
|
|
|
|
|
|
captainfuture
|
|
July 28, 2013, 08:40:21 AM |
|
so coinchoose wrong now too ?
|
|
|
|
|
|
mercSuey (OP)
|
|
July 28, 2013, 08:55:53 AM |
|
so coinchoose wrong now too ?
hmm, it was right about a couple hours ago but now I see the difficulty on coinchoose is not in agreement with Erun and SW pool difficulty. |
|
|
|
|
Taxidermista
Legendary
 Offline
Activity: 1147
Merit: 1001
|
|
July 28, 2013, 09:41:27 AM |
|
And what about multipool.in?
|
|
|
|
|
captainfuture
|
|
July 28, 2013, 09:42:34 AM |
|
And what about multipool.in?
ask flound. he shall look into it. |
|
|
|
|
|
mercSuey (OP)
|
|
July 28, 2013, 09:44:41 AM |
|
And what about multipool.in?
No, it is showing block count and difficulty same as BigVern's pool, thus they are forked as well. Notify flound. |
|
|
|
|
|
digitalindustry
|
|
July 28, 2013, 11:19:31 AM |
|
I just sent - Cap to Cryptsy , they confirmed on my Wallet , haven't appeared as pending on Cryptsy , so I'm guess in they just went into the wrong fork ?
they are on your crawler but ?
963a2e04383fb957fe82823c74bcd69aba1f79359e6abf89c714de39db4f7e1e
should i say goodbye to the Caps ?
|
- Twitter @Kolin_Quark
|
|
|
|
captainfuture
|
|
July 28, 2013, 11:32:01 AM |
|
i could mine on the wrong chain and sell it at cryptsy cause they are on this wrong chain too  OMG what happens to someone who buys this wrong caps? or isnt that possible ? why isnt caps stopped at crypts? i heared cause vern is sleeping. cant be that only 1 person can do that ? |
|
|
|
|
|
ilostcoins
|
|
July 28, 2013, 11:42:08 AM |
|
How does something like this happen? 1 minute block time isn't long enough?
|
LTC: LSyqwk4YbhBRtkrUy8NRdKXFoUcgVpu8Qb NVC: 4HtynfYVyRYo6yM8BTAqyNYwqiucfoPqFW TAG id: 4313
CMC: CAHrzqveVm9UxGm7PZtT4uj6su4suxKzZv YAC: Y9m5S7M24sdkjdwxnA9GZpPez6k6EqUjUt
|
|
|
|
mercSuey (OP)
|
|
July 28, 2013, 11:57:40 AM |
|
How does something like this happen? 1 minute block time isn't long enough?
This is an issue because a pool had 90% of the network hashrate. It is not an issue with the coin itself. This is why a pool should not be allowed to have more than 50% of network hashrate. Vern will be awake soon and it will be fixed. |
|
|
|
|
|
mercSuey (OP)
|
|
July 28, 2013, 12:04:36 PM |
|
Mullick can't login right now, but asked this node be posted here:
199.180.115.100
so everyone add this node to your config file: addnode=199.180.115.100 |
|
|
|
|
|
bcp19
|
|
July 28, 2013, 12:06:18 PM |
|
How does something like this happen? 1 minute block time isn't long enough?
This is an issue because a pool had 90% of the network hashrate. It is not an issue with the coin itself. This is why a pool should not be allowed to have more than 50% of network hashrate. Vern will be awake soon and it will be fixed. What is the pool supposed to do if people flock to it? Arbitrarily look at network hash vs pool hash and kick out people until the hash rate is low enough? If this pool ended up with 90% of the network, it'd have to dump 8/9's of it's hash to be under 50%!!(Don't try to say 45%, cause the kicked ones would not immediately reconnect to a different pool, so that would not work) Also, who do they kick? The biggest? The smallest? |
I do not suffer fools gladly... "Captain! We're surrounded!"
I embrace my inner Kool-Aid.
|
|
|
|
captainfuture
|
|
July 28, 2013, 12:12:18 PM |
|
automatic switching coin pools will destroy everything.
i mined all night long on the right chain, and now the bigger wins and make his chain to the right one...
if that wont change in future i will quit mining.
|
|
|
|
|
|
mercSuey (OP)
|
|
July 28, 2013, 12:16:29 PM |
|
How does something like this happen? 1 minute block time isn't long enough?
This is an issue because a pool had 90% of the network hashrate. It is not an issue with the coin itself. This is why a pool should not be allowed to have more than 50% of network hashrate. Vern will be awake soon and it will be fixed. What is the pool supposed to do if people flock to it? Arbitrarily look at network hash vs pool hash and kick out people until the hash rate is low enough? If this pool ended up with 90% of the network, it'd have to dump 8/9's of it's hash to be under 50%!!(Don't try to say 45%, cause the kicked ones would not immediately reconnect to a different pool, so that would not work) Also, who do they kick? The biggest? The smallest? It's not supposed to even reach that point. Historically, a pool op is supposed to close registration to new miners when the pool's hashrate has reached 40% of network hashrate. This wasn't done at Vern's pool, and it's not being done when these young coins have only one pool because there's a feeling there is no other choice, so might as well just leave registration open. |
|
|
|
|
|
captainfuture
|
|
July 28, 2013, 12:18:39 PM |
|
the registration is not the problem.
|
|
|
|
|
|
digitalindustry
|
|
July 28, 2013, 12:30:35 PM |
|
Mullick can't login right now, but asked this node be posted here:
199.180.115.100
I am logged in. The forks seem to be coming from multipool. The network hashrate has been relativity stable around 100-150Mh the last week or so. When mutlipool added caps to the rotation the network hashrate jumped by up to 700Mh in a matter of minutes The difficulty adjusted rather quickly and the pool moved on. The difficulty once again adjusted rather quickly and they came back. This seems to have caused the fork yesterday. It appears to be the same issue today. The chain was forked and verns pool and the cryptsy wallet followed the longer chain. Vern pool was the only pool to be moved to the new chain so the hashrate dropped to 50Mh when multipool left. Causing the difficulty to drop dramatically and bring multipool back in a continuing cycle. Due to the difficulty algorithm coin generation should only be minimally effected by this. I have asked for caps to be removed from the multipool rotation. When i return home i will release a temporary client with the new checkpoints awaiting the release of 1.4 I am sorry for any loss created by this unfortunate situation. I am doing my best to get the chain as reliable as it once was. I assure you i will do everything in my power to prevent this in the future. sorry for any loss ? i just sent 1100 cap to cryptsy ? do i get a refund ? or is that just " how it rolls " |
- Twitter @Kolin_Quark
|
|
|
|
