Topic: [ANN] 42 | Time to Revive 42 Coin - Everyone get in here!!! - page 27. (Read 357186 times)

Totally agree.  I run pools for over 20 coins, and for the most part we get notified or mentioned in passing, that a coin has an upcoming fork, for whatever reason.

42 has been very calm and no earth-shattering changes in a long time (if at all even..). So this kind of hit us and other pools blindly without notice.  Some of us (my pool included) was one of the more popular pools on the network, which makes it sting a little more than usual.

Needless to say, I follow 42coin on twitter now just incase.

Regarding this whole fiasco, there is fault on both sides.

For pool operators, especially the big ones, it's your job to keep up with the coins you list.  You are paid by the fees and donations you receive.  No excuses.  I mine for fun and like to mine one offs like this, and I use dedicatedpool for them most of the time.  I'm considering going elsewhere.

For the developer, where are you?  You can't just disappear after the hard fork happens that you caused to happen.  There are folks out there with real fiat currency invested in your altcoin.  You knew the hard fork was coming and you apparently never bothered to check up on the pools.  I think in the spirit of open source software another developer should take over development since the current developer can't be bothered to support the coin.

Hey OP.. wheres my post? you deleted my explanation/reply to a miner on my pool.

Unfair moderation.. so here it is again:

Quote
Quote from: lunswor on Today at 02:48:18 PM
Quote from: ThomasMuller on Today at 02:34:31 PM
I don't understand this crap! Hashfaster said they had updated their wallet then I woke up today and they orphaned my last 48 hours of mining. I keep saying it is up to the Admin to make sure he is running a safe and current pool. I agree with Dutch, the Dev published in big RED letters and tweeted for the last 3 weeks telling everybody to update.

There is pool here that was on the same block as Hashfaster and they allowed transfer to Cryptsy. I'm very upset right now!

That is whole situation is just crazy....

Regarding HashFaster's 42coin pool. The situation was no, we did not see the dev's notices and was not aware of any imminent hardfork, and we found out hours after block 55000 that something wasn't right and promptly upgraded and restarted our wallets (resync) and put up a notice on our pool.  We watched the situation carefully and at that time we had no reason to believe we were not on the correct fork (a resync fixes this usually).  We promptly put up a MOTD cautioning people of the situation (it said: Mine at your own risk, coin is forked) , and the fact that the coin has 5+ forks going on, and no confirmation of which chain is the right one.  Nearly a day later, no help from devs, or anyone to confirm the correct blockchain, so we posted our block hashes for people to compare.  After about 4-5 comparisons it was clear we were not on the right fork.  We had the wallet upgraded, so our ONLY option was to stop the wallet, blow away all blockchain data again and resync again.  We did this and eventually came up with the same blockhash as other users were reporting. That unfortunately confirmed that the last 48 hours of "hoping this will turn out well" ended up in resulting in 48 hours of wasted mining (and 12 hours of paying out on a fork!).  This means we obviously had to orphan the blocks mined on the wrong chain, as they were orphans, simply put.

I can't say for sure why this would happen, but clearly we were not the only pool that it happened to.  Its possible that upon the first resync, the peers our wallets connect to had majority on a wrong fork (likely due to alot of people and pools not even aware the coin was forking).

We are still cleaning up the pool as you could imagine, paying out 1000 orphaned blocks can cause havoc in transaction tables, and in many cases cause a pool wallet balance to fall of sync (until a rescan can re-verify all txes).

As mentioned, we wasted no time in putting up a notice to caution miners, which I assume was ignored or dismissed, the warning was clearly important (and may have saved people some wasted hashing) given the end result of this forking issue.

I am sorry it happened, it wasted alot of miners time, and wasted my time trying to pick up the pieces that a "failed fork" causes. It also didn't help that profit based on coinwarz was inflated, which clearly had 42coin on top because they were displayed a super low diff on the wrong fork.

I hope this clears up any confusion to what happened.

yes that is the correct fork

I got too. Is it right fork?

So which is it?  Which is the correct fork we're all going with?

There still isn't a clear answer.

I updated my 42 coin client when it came out those of you that did not will have to update to the  new one and re sync your whole chain. 

From what i can see it appears everyone who updated in time is on the same chain.

I updated Cryptsy on April 2nd but failed to update altexplorer.info at the same time.

Redownload of altexplorer.info got me on the same chain as cryptsy and altexplorer.net

Looks like hashfaster and coinchoose did not update in time I take it?


Given this deposits/withdrawals have been enabled at cryptsy again

Hi there !

hard times those days...

Could anyone suggest me a good pool for mining 42 Coin ?

I'm actually mining at CoinPool.de

Cheers !

That is whole situation is just crazy....

I don't understand this crap! Hashfaster said they had updated their wallet then I woke up today and they orphaned my last 48 hours of mining. I keep saying it is up to the Admin to make sure he is running a safe and current pool. I agree with Dutch, the Dev published in big RED letters and tweeted for the last 3 weeks telling everybody to update.

There is pool here that was on the same block as Hashfaster and they allowed transfer to Cryptsy. I'm very upset right now!

Thanks for your efforts BC!

Will the coin exchange sites (cryptsy, etc..) be affected by this?

PS
..I started mining 42 at block 55002 - - I didn't think it was possible for a "good friday" to be just another crappy Monday...LOL

All pools that have not updated the client must do it now!
if you are waiting for a response from Devs read tweets and posts.

update clients !!

some pools even have links to old wallets which needs fixing to point to updated ones.(you know who you are)

if you run a pool for any coin you need to have current links to latest wallets etc.
it's not a set and forget thing ya know, and to me sounds like a pool management issue.

and if you don't keep the clients updated when dev's have been posting and tweeting about it the last 3 weeks then is it the dev's fault,
I don't think so.

Any news about p2pool.org ?

Damn I lost 0.01 of this coin. When the "fork" did a transaction took place 0.01 of Cryptsy my wallet and never received! Is there any way to get them to the number of transaction? Above the pool is down for maintenance because the developer of the coin is not contacted them. This is the pool:

http://42.dedicatedpool.com/index.php

can we all just switch to updated clients, Then throw all the hashing at that.
shouldn't that Fork it the right way ??

I don't know where this will all end up but, as it stands now, blocks we've mined at our pool are being accepted immediately at cryptsy on deposit in out test deposits.  We corrected one of our earlier posts, coinwarz is using an older client and are most likely not on the right fork. Cryptsy seems to be, but we only think that because they seem to be on the same fork we are.

I don't think they are on the wrong fork, I didnt start the pool until after the latest source was released and untill after block 55000.

we get d8ef6acf1da476ea6ea53050a5355e9f7fc35f0918862df66b85aed8c6438649 for that block

I got d8ef6acf1da476ea6ea53050a5355e9f7fc35f0918862df66b85aed8c6438649