Topic: [ANN] Infinitecoin - IFC | V1.8 Released! *Mandatory Upgrade, upgrade ASAP* - page 18. (Read 199669 times)

I bought 60mill on cryptsy without reading this, and choose withdraw only when I didn't see the incoming amount I checked out here.
So what do we do now ?

I actually mined for a couple days on the fork... so I mined like 100 Million coins... then they all disappeared.
Sigh... my fault for not checking first to see if everything was ok.

Cryptsy is not on that block chain, it's still on the original fork stuck at high diff so if you try and withdraw or deposit any coins it with Cryptsy it will fail.

Excellent solution monocolor!

I have been stuck for a while now... I loaded your block chain, put in the listed nodes on the new client and was 100% synced in minutes.
Thank you!

I like monocolors solution.

OK I think this is enough. For 3 days, I've been waiting for this super hard block to be solved, and it was not solved, and I don't know how long it will take. The blockchain is jammed. The coin is about to be dead. Thanks to all the attackers to put IFC in this situation.

Luckily we have a way to get out of it. I was sync'ed to an apparent forked chain, and I watched it go from block 247330 to block 248722. I started to mine it sometimes ago, it works fine. With version 1.7 and starting from 248000, the diff retarget becomes normal and everything seems working.

I will not be stuck at block 246953 in the old chain forever. I am using the new chain. By comparing the forked chain with the one in block explorer, I see it forked out of block 246948, 5 blocks before the one we get stuck. So it is not too bad, only 5 blocks will be lost.

You can use 1.7 client and sync from scratch (you need to clean up the config dir, NOT delete wallet and config file, then start to sync with your client), you should get to the forked chain like I did. The sync will take about 3 hours to complete. Or you can download the chain here (pretty big: 228M) :
https://mega.co.nz/#!ZghiRIzT!GlZMiA2_Nv7MQ6V4QqwJRzgfSI5IgkKsnvnZbzJ2Pn4

unrar the file, and copy the files into your config dir (please backup your existing chain, so if you don't like it you can go back).

Also here are my peers, that you may want to use as addnode.

66.87.67.255
108.62.211.7
66.63.176.231
80.7.165.182
24.144.220.244
192.241.222.102
98.18.252.73
192.249.59.81
75.152.93.200
95.170.82.34
67.177.3.56
80.234.71.58

Note, apparently there are more than one forked chains, but other chains can not be sync up, possibly they violate some constraints such as checkpoints. Once you sync to 2487xx, you should be able to start mining with 1.7 client.

I bet right now they are forks in this chain all over the place. Everyone needs to choose an update and stick with that one, even if it means going back to basics with some of the code.

Well, that seems like a problem, no?

I have an IFC deposit on Cryptsy stuck on 5 confirms for days now, I will not be the only one, so I think they might freeze the coin, who knows they might reverse the dump, but whoever bought the coins wont be able to withdraw them so it doesn't really matter. The will just be stuck on Cryptsy forever if the block chain doesn't get fixed.

dumped on cryptsy so i am guessing that it was already on the exchange

It wasn't on the main block chain, that hasn't advanced in days therefore no transactions.

Somebody just dumped 10 Bilions IFC which is 11% of existence. Any ideas why?

So how long are we going to have to trudge through these mega-difficult blocks?

Thank you for issue rectification and quick help!

Looks like the chain I sync'ed is a forked chain at block 246948, so it does not violate any checkpoints. If some confirmations are overwritten, will anyone lose coins? Or the transactions will be considered not happened?

If someone will lose big coins, then we better wait. Otherwise we may use the forked chain which will get to the switch point earlier. The problem with block 246953 is that it is at big diff, no idea when it will be solved.

Apparently there's at least one more blockchain at block 254501 now.

Trouble is that the shorter chain is jammed on Cryptsy at high diff with transaction confirmations riding on it.

Looks like this is a forked blockchain that gets around that block that has huge diff, which virtually jammed the chain. Let me see if I can sync to it.

If you sync from scratch with version 1.7, I think you will sync to this chain, which is currently at block 247332, this looks the correct chain to me. I tried it in another computer, I got the same thing.

246953 looks like the last block.

http://exploretheblocks.com:2750/chain/Infinitecoin

Dev already changed the diff retarget to the PPCoin algorithm, and set the switch block to be 248000. I think this algorithm should be reliable, as it has been used by all pos coins. The block 248000 may be a little conservative, but if people don't switch then we are in a bigger problem. It really depends on the diff, some cycles the diff did not go very high, but some are really high, it may depends on the hashrate at that time. It was faster a few days ago.

Some people attacked the IFC for sure. Any pow coin with 60 blocks or above retarget diff cycle can be attacked exactly the same way as IFC. That is, use high hash to boost the diff, then leave, then come back at low diff etc. After a few cycles, the coin will likely be blocked due to its high diff. IFC being the first one attacked this way possibly because its popularity.

But it looks like I am in another chain... I am at block 247330 sync'ed.

There maybe multiple chains out there, I saw one at 254488, another at 244999, but these two are not sync'ed though.