Does that fix really solve anything?
I mean, if Cryptsy is not on that chain, how will it work?
If not pools are on that chain, what is the point?
I'm not asking passive aggressive questions here... I just don't understand how this works when it goes sour like this.
Topic: [ANN] Infinitecoin - IFC | V1.8 Released! *Mandatory Upgrade, upgrade ASAP* - page 17. (Read 199669 times)
September 25, 2013, 10:28:54 AM
September 25, 2013, 10:19:29 AM
it is now on my server
http://www.fraktion42.net/web/ifc-bc.rar
http://www.fraktion42.net/web/ifc-bc.rar
September 25, 2013, 09:39:10 AM
https://mega.co.nz/#!ZghiRIzT!GlZMiA2_Nv7MQ6V4QqwJRzgfSI5IgkKsnvnZbzJ2Pn4
Can someone put this on a file sharing site that doesn't force you to install spyware in order to download files?
I did message the dev and offer to host a copy on my sever and he declined the offer
September 25, 2013, 08:35:20 AM
https://mega.co.nz/#!ZghiRIzT!GlZMiA2_Nv7MQ6V4QqwJRzgfSI5IgkKsnvnZbzJ2Pn4
Can someone put this on a file sharing site that doesn't force you to install spyware in order to download files?
September 25, 2013, 08:10:35 AM
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.
Mining a coin isn't an attack, it is what it is there for.
IFC is in this situation due to a poorly coded difficulty adjustment algorithm.
While a bit harsh... I think this is the case.
The problem we are in now is due to a problem in 1.5 or 1.6, right?
Lets just get it fixed and move on.
September 25, 2013, 07:50:29 AM
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.
Mining a coin isn't an attack, it is what it is there for.
IFC is in this situation due to a poorly coded difficulty adjustment algorithm.
September 25, 2013, 07:45:10 AM
Nice solution without need of another release. If you want to mine using cpuminer you may use coin-base.net pool which reloaded the blockchain too and supports getwork without proxy. Current block 249962
September 25, 2013, 07:38:50 AM
Yes, I'd like to hear an official word on this... at this point I feel like any work is thrown away.
September 25, 2013, 07:32:36 AM
I can see my last block
http://exploretheblocks.com:2750/block/692c8c9c5f8bd61dc02733e8a09fb8f60b4b0b9cbaa9b9ee673f34489431776b
http://exploretheblocks.com:2750/block/692c8c9c5f8bd61dc02733e8a09fb8f60b4b0b9cbaa9b9ee673f34489431776b
so does this mean that monocolor found the official blockchain?
I suggest no one mine this blockchain until we receive some official word from fisheater.
September 25, 2013, 07:28:21 AM
September 25, 2013, 07:21:28 AM
I switched my miners to the blockchain monocolor suggested. I will continue to mine this blockchain until fisheater gives his blessing and cryptsy updates their client.
its a big gamble hopefully it pays off.
its a big gamble hopefully it pays off.
September 25, 2013, 07:15:18 AM
what blockchain are you on? the one that monocolor suggested?
yeah I think it's on the monocolor one. the current block number matches.
I think this is the best option.
I made tests on http://infinitedice.net and it's working good with this blockchain.
September 25, 2013, 07:03:46 AM
I have deleted all files except for wallet and conf. I have entered the new addnodes and then restarted infinited v1.7
I have 8 connections
I have 8 connections
September 25, 2013, 06:45:44 AM
what blockchain are you on? the one that monocolor suggested?
September 25, 2013, 06:45:25 AM
It's not on the main fork.
http://exploretheblocks.com:2750/chain/Infinitecoin
I wouldn't be mining IFC atm. You may loose all you mine. There needs to be a checkpoint set by the dev and a new version released.
September 25, 2013, 06:13:09 AM
New blocks, but the difficulty is almost at 0
http://coin-base.net/infinitecoin/
http://coin-base.net/infinitecoin/
September 25, 2013, 05:39:58 AM
Hi All,
I have a problem with my IFC client.
I transferred my IFC coins to someone and still it shows in pending and my wallet client continuously says out of sync. when I try to sync the progress goes till end and again comes back to the middle. Its nearly a day and I am seeing it in pending state.
Any suggestions please.
IFC is broken, you can't send coins atm, you may even loose them if you try. Next time read the thread, we have been talking about this for the last couple of pages.I have a problem with my IFC client.
I transferred my IFC coins to someone and still it shows in pending and my wallet client continuously says out of sync. when I try to sync the progress goes till end and again comes back to the middle. Its nearly a day and I am seeing it in pending state.
Any suggestions please.
September 25, 2013, 05:35:13 AM
Hi All,
I have a problem with my IFC client.
I transferred my IFC coins to someone and still it shows in pending and my wallet client continuously says out of sync. when I try to sync the progress goes till end and again comes back to the middle. Its nearly a day and I am seeing it in pending state.
Any suggestions please.
I have a problem with my IFC client.
I transferred my IFC coins to someone and still it shows in pending and my wallet client continuously says out of sync. when I try to sync the progress goes till end and again comes back to the middle. Its nearly a day and I am seeing it in pending state.
Any suggestions please.
September 25, 2013, 04:29:07 AM
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.
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.
great idea
i'm curious what fisheater thinks about this.
should we take this fork and forget about block 246953 ?
anyway i'll have a try on some wallet. i think this is the best option. include these nodes, reset the blockchain and sync to the new one.
EDIT : done it with some wallet. I get a new block every once in a while, so diff retarget is ok and works well ! it tries to sync to another blockchain now (which is at block 332379). Every transactions that I made while solving old blockchain 246953 block are confirmed in this blockchain.
I think this is a good way to somehow "fix" what the IFC is going through. If I mine, I'm not even sure to mine on this old blockchain, to say the truth. So how can we expect to find a block ?
I need to see what happens before upgrading InfiniteDice.net
And .. I hardly see Cryptsy and other exchanges do this without any more feedbacks.
September 25, 2013, 03:02:09 AM
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 ?
Well the withdrawal probably never left Cryptsy so get them to cancel it.So what do we do now ?
Jump to: