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

Thanks Redcoin. They both work great.

Managed to sync with no problems on my first try (after deleting the old blockchain data). I'm on the same chain as you (block 253128 as I post this).

I send 1 IFC to bter for test ,it's OK now(Transaction:b3f28dda0f28d3047fc530897d5cd7a14c715d868abb82e1be75078772068bb8   )
  send 1 IFC to Coins-e  for test ,it's still unconfirmed(Transaction: 72709816e5144976a3b976e730ebd32963e6c26a5048098be73641ce2f10e6cd)

Waiting for cryptsy.com list IFC again

if you are on the same block chain, come and play Coin Bomb!!

http://coinbomb.biz/infinitecoin/

check your blocks: http://coinbomb.biz/ifcblocks/

It seems IFC begun to move. I hope the developers will be a little bit careful to our favourite coin

Hi, im making an IFC bomb game, and  have re-enabled IFC on coinjack.com

have uploaded a block viewer after updating the client, i think everybody should be up to the same blocks, else you are on the wrong fork, and when you play the games your funds wont arrive.

Is everyone upto the same blocks?

http://coinbomb.biz/ifcblocks/

I've updated to 1.7 and reloaded the block chain, currently on block 252149 @ 2.137 diff, does this sound correct?

Network Hashrate: 465.015 MH already. Pool jumpers are on the loose again. WTF.

Coinchoose are on block 251903    but it says the difficulty is 249 Go figure!

dont think that epools are up anyway.

the pools are now integrated into coinEX.
as soon as i saw there is a fork we paused trading and mining until all are on the same chain. that was 7 days ago now.

BTW, the V1.7 client is working fine, and the last checkpoint is recent enough, so I don't see the need to release a new version of the client at this time.

tokyoghetto, thanks for the info. Can you PM me the email of BigVern, I will send him a summary of what has happened. However, I'd prefer we stabilize a few more days before allowing trading again, trading with many forked chains will be a very messy and unpleasant thing to do.

So basically as you know, the original blockchain is jammed due to extreme high difficulty. It is jammed because the linear retarget algorithm has issues. We fixed the algorithm in the Version 1.7 client, by using the PPCoin algorithm, which has been proven to be reliable in many pos coins. But unfortunately before the planned switch happens, the blockchain jammed for 3 days, and seems continue to be jammed. During the jam, apparently several forked chains were created, in which one of them seems reasonably good, and is being adopted by the community. It is in the after-switch zone, and seems the new PPCoin diff retarget algorithm works reasonably well. If everything is working fine with this blockchain, then I have no problem (and no choice) to go with the community, and this is probably the best way we get out of the mess we have been in the last few weeks. This is a p2p network, I have no control over which blockchain to take or which not to take. It is entirely depends on the miners.

As I said before, I will continue support any enhancements/upgrades for the client as seen needed by the community. But again please understand that I can only help there. P2p coin once released, the dev can no longer control it.

Good luck to IFC!

I just spoke with BigVern over at Cryptsy. He said that they won't be re-instating IFC until they hear from the Dev "fisheater" about what has happened with IFC and what the solution is.

I just finished downloading the new blockchain using the 1.7 client. I didn't need to add any new nodes, just the ones that came with the client which I downloaded off the infinitecoin.org website. Some coins that I mined from coin-base.net I managed to send them to my wallet. The PPC diff algo is working beautifully, Nethash is sitting at a healthy 300mhash, coin-base pumping 100mhash and diff sitting at 1.05.

Everyone please upgrade to the 1.7 client, download the blockchain again and get back on the IFC rocket.

wish we kept this whole "correct blockchain" thing a secret...but here goes

before you do this back up your wallet.dat and .conf files, just delete THE BLOCKCHAIN...

1. delete old blockchain
2. make sure you have 1.7 client, if not download 1.7 client
3. download new blockchain through wallet, as of this moment there are 25 active connections
4. wallet should report that we are on block 251505 as of this post, which is what coin-base.net is reporting as well
5. voila! IFC is alive and well
6. get everyone to do the same thing so we can all get back to our regularly scheduled program.

special thanks to ortchi42 for updating coin-base and basically letting me rape IFC....today felt like hitting the jackpot at Vegas. I will never mine that many IFC ever again in my life. Also a big thanks to "monocolor" for shedding light on this whole "forked" chain debacle...I think this is the first time in alt-crypto history a coin has forked itself to THE CORRECT CHAIN.

From what I can see, IFC is now alive and running fine. The current block is: 251454

With v1.7 I am able to pick up the old blockchain, sync to current and solo mine, and I did *not* need to mass download any blockchains, nor even any special addnodes. (It found everything by itself). This is not a fork that monocolor plucked out of nowhere -- rather he found it on the network, probably from a solo miner(s) that turned on his wallet at the right time and managed to route around the stall, by computing enough blocks while they were synchronizing, to get ahead of it. This reflects a “working as designed” p2p recovery from the situation.

Note that if you had the wallet active right up to the stall, it's probably a good idea to delete the old block database and re-download (note: KEEP your wallet.dat and .conf files!). (and I mean download via the standard wallet sync-ing, not that file from mega.nz)

This pool is on the active chain:
http://coin-base.net/infinitecoin/

These pools are on the broken series:
http://infinite.netcoin.pl/
https://ifc.epools.org/
http://ifc.scryptmining.com/
Also remember that the block explorers, coin chooser sites, etc showing the old series may not even be upgraded to the v1.7 software yet.

The old stalled/bad block (246953/4) has little chance of proceeding because the diff is ultra-high and still climbing, and noone is mining at those stalled pools now anyways.

It seems probable that some big pools/miners/exchange sites, including Cryptsy were caught out by the rapid flurry of releases and did not upgrade fast enough to v1.7, which contributed to the forks.

If a few blocks got orphaned around 246953 (perhaps a total 5?), that's fairly inconsequential. From what I understand, for anyone who had txns inside those orphaned blocks, the txns will either be in the new blocks, or if they never registered then the coins will be back in your wallet. (might have to rescan/reindex wallet). The coins don't just disappear!

Also note: trades happening inside Cryptsy (with coins already there) are purely on those internal accounts, and don't affect the blockchain. I would recommend holding off any transfers to/from your exchange until confirmed they are on the active chain. (you can also send a small test amount first).

The new difficulty algorithm from PPCoin, active since block 248000, looks good and is oscillating up and down nicely so far, and climbing up.  Any coin is going to have problems with mass surge-waves of hashing - an easy, perfect solution to that is not known. Fisheater has done a commendable job of responding quickly, and the PPC algorithm should be a robust improvement.

I'm not sure more checkpoints will help right now, and it could induce yet another fork point if miners fail to upgrade in time. Depends on how strongly the community wants such a confidence booster from you, fisheater.

Why is the own IFC community not helping themselves by using the right client version? Unless there are troll about mining hard on an older version just to try and mess things up?

About time! No point trying to continue with transactions when not everyone is on the same chain.

just pointed bitjohn to this post and he has paused trading on IFC

I'd need to explore the monocolor blockchain to see if the address iLTo27RTdq6xwpmnNSe3JUfyZwFt7jyo3B still contains its 300 millions coins that were spend in block 246954.
The chain forked on block 246948. In this block, the coins still were in iLTo27RTdq6xwpmnNSe3JUfyZwFt7jyo3B. They arrived here in block 246822.
The only thing is that on the monocolor blockchain, the transactions in blocks 246949 to 246954 never occured. The coins are not lost.

block 246954 on the forked chain is not the same as block 246954 on the old chain, they contain different transactions. Find me the block on the forked chain that has the 1,057,817,529 in transactions, bet you can't.