Topic: BigVern CAP pool is forked [message from Mullick] (Read 1866 times)
You'd think you'd be grateful that your NanoCoin got the endorsement of MultiPool. Too bad Big Vern doesn't have the quality control we do and should be orphaned for causing the fork.
i lost all my caps from last night too.
someone sys to me i should have mined on the greatest pool to be on the "right" cain.
but so the pool gets greater and greater and then they say: spread the load....
so what shall i do? i prefer smaller pools but they will loose
someone sys to me i should have mined on the greatest pool to be on the "right" cain.
but so the pool gets greater and greater and then they say: spread the load....
so what shall i do? i prefer smaller pools but they will loose
Mullick can't login right now, but asked this node be posted here:
199.180.115.100
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 "
the registration is not the problem.
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.
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.
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.
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.
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.
Mullick can't login right now, but asked this node be posted here:
199.180.115.100
199.180.115.100
so everyone add this node to your config file:
addnode=199.180.115.100
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.
How does something like this happen? 1 minute block time isn't long enough?
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 ?
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 ?
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 ?
they are on your crawler but ?
963a2e04383fb957fe82823c74bcd69aba1f79359e6abf89c714de39db4f7e1e
should i say goodbye to the Caps ?
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.
And what about multipool.in?
ask flound. he shall look into it.
And what about multipool.in?
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.
so coinchoose wrong now too ?
you are welcome to mine here as well: http://mcap.coinmine.pl
Yes, I vouch for feeleep's pools. He's a very good pool op. Thanks feeleep.
you are welcome to mine here as well: http://mcap.coinmine.pl
Please spread the word if you know someone mining at BigVern's pool. Thanks.
Jump to: