[ANN] Infinitecoin - IFC | V1.8 Released! *Mandatory Upgrade, upgrade ASAP*

[myweblife]

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

[1715305718]

1715305718

[1715305718]

1715305718

[1715305718]

1715305718

[Ephebus]

Is everyone upto the same blocks?

http://coinbomb.biz/ifcblocks/

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).

[fisheater]

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

http://coinbomb.biz/infinitecoin/

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

Thanks Redcoin. They both work great.

[fisheater]

This is the email I sent to BigVern.

Hi BigVern,

This is fisheater, dev of IFC. I want to give you a summary on the current status of the IFC, and solution to the problem (please refer to the following bitcointalk post):

https://bitcointalk.org/index.php?topic=225891.msg3236835#msg3236835

This is what happened to IFC: IFC was using the standard pow linear retarget formula every 120 blocks (1 hr in normal conditions), to compute the diff retargets. This formula was exploited by some attackers who found that by pushing the diff high at retarget time they can skip the high diff zone and mine only the low diff zone. The oscillation of the diff become extreme and high diff zone (120 blocks) sometimes took a day to complete. In this case the miner community asked for retarget at each block, we made code change to retarget each block (with 120 blocks average) and kept the same formula. This has been proven to be a bad decision. The retarget each block using linear formula did not fix the problem but made the problem worse. To address the issue, we released another version (V1.7) of the client using the PPCoin retarget formula which retargets at every block. We set the switch block to be 248000 and asked everyone (including cryptsy) to upgrade.

Unfortunately before we reach the switch block, the blockchain is jammed due to extreme high diff at block 246953. It was jammed for 3 days, and during that time several forks are created to get around the problem. These forks were not created by the dev. In fact we were thinking to release a new client with immediate switch to the new PPCoin retarget formula. Anyway, from these forked blockchains one stood out and quickly adopted by people. This fork was forked out at block 246948, 5 blocks before the block point (so 5 blocks are lost by using this blockchain). The IFC miner community like the forked chain, possibly because soon it passed the switch block and the new PPCoin retarget formula kicked in, and diff retarget became smooth. Today if syncing from scratch, this is the blockchain that will be sync'd. It is current at block 253375, and the diff retarget is working fine with IFC client V1.7.

The choice of the blockchain was not from dev, in fact we have no control at all in the process. The choice was from the miner community. I think this choice is probably the best choice since it gets us out of the mess of the diff retarget in the last few weeks. I observed the mining on the new blockchain for a few hours, the designed block target (30 sec) is met, and diff retarget is smooth.

People also created block chain viewer and game which I tried and they work fine. So I recommend that we go with this blockchain (I don't see any other possibilities). I suggest cryptsy to observe the stability of the blockchain maybe for a day or so before restoring the trading of IFC.

Please let me know if you have any questions. The dev team of IFC will continue to support IFC community and will implement any improvements as needed.

fisheater

[c1010010]

Thanks fisheater!



So far, things seem to be moving along well.  I had to open up a new wallet (on a business trip and cannot get access to my other) so I can only confirm that a new-wallet works nicely with pools.

I'll have to check the other in a few days.


Also, appears that things are going well on the game front too.

Come play... and lets get some transactions out there!

http://coinbomb.biz/infinitecoin/

[c1010010]

I'm only ever getting "1 active connection to the infinitecoin network"

How does one improve that?

[TreasureSeeker]

I'm only ever getting "1 active connection to the infinitecoin network"

How does one improve that?

Do you have the addnodes from fisheater's first post in this thread in your infinitecoin.conf file?  If not, try adding them. 

[c1010010]

I'm only ever getting "1 active connection to the infinitecoin network"

How does one improve that?

Do you have the addnodes from fisheater's first post in this thread in your infinitecoin.conf file?  If not, try adding them. 

Yup, actually, quite a bit more:

addnode=111.161.77.213
addnode=67.193.198.104
addnode=85.217.147.117
addnode=66.87.67.255
addnode=108.62.211.7
addnode=66.63.176.231
addnode=80.7.165.182
addnode=24.144.220.244
addnode=192.241.222.102
addnode=98.18.252.73
addnode=192.249.59.81
addnode=75.152.93.200
addnode=95.170.82.34
addnode=67.177.3.56
addnode=80.234.71.58

[c1010010]

I'm only ever getting "1 active connection to the infinitecoin network"

How does one improve that?

Do you have the addnodes from fisheater's first post in this thread in your infinitecoin.conf file?  If not, try adding them. 

Yup, actually, quite a bit more:

addnode=111.161.77.213
addnode=67.193.198.104
addnode=85.217.147.117
addnode=66.87.67.255
addnode=108.62.211.7
addnode=66.63.176.231
addnode=80.7.165.182
addnode=24.144.220.244
addnode=192.241.222.102
addnode=98.18.252.73
addnode=192.249.59.81
addnode=75.152.93.200
addnode=95.170.82.34
addnode=67.177.3.56
addnode=80.234.71.58

OK, quick script... most of those are dead as a doornail.
http://pastie.org/8358637

The only ones that work:

addnode=85.217.147.117
addnode=66.63.176.231
addnode=98.18.252.73
addnode=192.249.59.81
addnode=95.170.82.34
addnode=67.177.3.56


If I strip the conf list to just those, no connections now.  Not one.

[fisheater]

I have a long list of peers, not sure all are good, but here they are (at block 254095 now):

   {
        "addr" : "92.195.101.215:52961",
        "services" : "00000001",
        "lastsend" : 1380236711,
        "lastrecv" : 1380236708,
        "conntime" : 1380236635,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "83.83.247.33:53665",
        "services" : "00000001",
        "lastsend" : 1380236708,
        "lastrecv" : 1380236713,
        "conntime" : 1380236637,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "76.110.255.33:9321",
        "services" : "00000001",
        "lastsend" : 1380236712,
        "lastrecv" : 1380236707,
        "conntime" : 1380236642,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "69.196.182.237:9321",
        "services" : "00000001",
        "lastsend" : 1380236712,
        "lastrecv" : 1380236711,
        "conntime" : 1380236642,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "121.73.174.13:52449",
        "services" : "00000001",
        "lastsend" : 1380236711,
        "lastrecv" : 1380236711,
        "conntime" : 1380236645,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "86.150.227.43:9321",
        "services" : "00000001",
        "lastsend" : 1380236712,
        "lastrecv" : 1380236686,
        "conntime" : 1380236647,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "192.99.2.38:35261",
        "services" : "00000001",
        "lastsend" : 1380236711,
        "lastrecv" : 1380236651,
        "conntime" : 1380236651,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 251576,
        "banscore" : 0
    },
    {
        "addr" : "94.189.239.110:63902",
        "services" : "00000001",
        "lastsend" : 1380236712,
        "lastrecv" : 1380236711,
        "conntime" : 1380236653,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "77.205.43.231:49839",
        "services" : "00000001",
        "lastsend" : 1380236710,
        "lastrecv" : 1380236712,
        "conntime" : 1380236655,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "95.170.82.34:9321",
        "services" : "00000001",
        "lastsend" : 1380236712,
        "lastrecv" : 1380236712,
        "conntime" : 1380236659,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 254505,
        "banscore" : 0
    },
    {
        "addr" : "46.147.138.65:51699",
        "services" : "00000001",
        "lastsend" : 1380236709,
        "lastrecv" : 1380236711,
        "conntime" : 1380236669,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "83.133.105.235:35842",
        "services" : "00000001",
        "lastsend" : 1380236713,
        "lastrecv" : 1380236713,
        "conntime" : 1380236686,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 254095,
        "banscore" : 0
    },
    {
        "addr" : "37.140.4.246:37889",
        "services" : "00000001",
        "lastsend" : 1380236712,
        "lastrecv" : 1380236712,
        "conntime" : 1380236691,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.4/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 59748,
        "banscore" : 0
    },
    {
        "addr" : "68.7.110.173:9333",
        "services" : "00000001",
        "lastsend" : 1380236712,
        "lastrecv" : 1380236712,
        "conntime" : 1380236698,
        "version" : 70002,
        "subver" : "/Satoshi:0.8.3.7/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 431752,
        "banscore" : 0
    }

[c1010010]

8 active.

Beauty.

[Stouse49]

Great work on fixing this coin and getting the correct chain that uses the new PPcoin difficulty retarget method.

[NaNaec]

any news about time of start of trading on cryptsy?

[wmikrut]

I'm only ever getting "1 active connection to the infinitecoin network"

How does one improve that?

Do you have the addnodes from fisheater's first post in this thread in your infinitecoin.conf file?  If not, try adding them. 

Yup, actually, quite a bit more:

addnode=111.161.77.213
addnode=67.193.198.104
addnode=85.217.147.117
addnode=66.87.67.255
addnode=108.62.211.7
addnode=66.63.176.231
addnode=80.7.165.182
addnode=24.144.220.244
addnode=192.241.222.102
addnode=98.18.252.73
addnode=192.249.59.81
addnode=75.152.93.200
addnode=95.170.82.34
addnode=67.177.3.56
addnode=80.234.71.58

OK, quick script... most of those are dead as a doornail.
http://pastie.org/8358637

The only ones that work:

addnode=85.217.147.117
addnode=66.63.176.231
addnode=98.18.252.73
addnode=192.249.59.81
addnode=95.170.82.34
addnode=67.177.3.56


If I strip the conf list to just those, no connections now.  Not one.

Everything seemed ok a couple days ago then the client stalled again.
I have wiped out my Appdata and loaded the 6 peers above.

I am syncing the client again and, fingers crossed, hope it goes all the way through in a few hours.

[monocolor]

It looks to me the blockchain is very stable now. Earlier sometimes I saw the client switch back and forth to some other chains, all the time it switched back after some time, as other chains are not sync'able. One of the chain is the Litecoin that I can recognize, this is probably that IFC (and many others at that time, such as NBL, FST, ALF etc) did not change the message channel, so it gets sync messages. It is not a problem, you can mine without any issues. As long as you have connections. Here are some of my peers FYI.

    {
        "addr" : "75.152.93.200:9321",
        "services" : "00000001",
        "lastsend" : 1380305794,
        "lastrecv" : 1380305782,
        "conntime" : 1380305686,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 256456,
        "banscore" : 0
    },
    {
        "addr" : "68.42.103.11:9321",
        "services" : "00000001",
        "lastsend" : 1380305840,
        "lastrecv" : 1380305770,
        "conntime" : 1380305692,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 256456,
        "banscore" : 0
    },
    {
        "addr" : "76.110.255.33:9321",
        "services" : "00000001",
        "lastsend" : 1380305840,
        "lastrecv" : 1380305805,
        "conntime" : 1380305693,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 256456,
        "banscore" : 0
    },
    {
        "addr" : "5.53.130.92:9321",
        "services" : "00000000",
        "lastsend" : 1380305840,
        "lastrecv" : 0,
        "conntime" : 1380305817,
        "version" : 0,
        "subver" : "",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : -1,
        "banscore" : 0
    },
    {
        "addr" : "86.132.75.90:9321",
        "services" : "00000001",
        "lastsend" : 1380305819,
        "lastrecv" : 1380305840,
        "conntime" : 1380305818,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 256457,
        "banscore" : 0
    },
    {
        "addr" : "86.150.227.43:9321",
        "services" : "00000001",
        "lastsend" : 1380305840,
        "lastrecv" : 1380305826,
        "conntime" : 1380305819,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 256457,
        "banscore" : 0
    },
    {
        "addr" : "95.170.82.34:9321",
        "services" : "00000001",
        "lastsend" : 1380305840,
        "lastrecv" : 1380305829,
        "conntime" : 1380305825,
        "version" : 60001,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 254505,
        "banscore" : 0
    },
    {
        "addr" : "96.127.231.164:9333",
        "services" : "00000001",
        "lastsend" : 1380305842,
        "lastrecv" : 1380305844,
        "conntime" : 1380305840,
        "version" : 70002,
        "subver" : "/Satoshi:0.8.3.7/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 432199,
        "banscore" : 0
    }

[erk]

It looks to me the blockchain is very stable now. Earlier sometimes I saw the client switch back and forth to some other chains, all the time it switched back after some time, as other chains are not sync'able. One of the chain is the Litecoin that I can recognize, this is probably that IFC (and many others at that time, such as NBL, FST, ALF etc) did not change the message channel, so it gets sync messages. It is not a problem, you can mine without any issues. As long as you have connections. Here are some of my peers FYI.

Which message channel, do you mean IRC?

[monocolor]

It looks to me the blockchain is very stable now. Earlier sometimes I saw the client switch back and forth to some other chains, all the time it switched back after some time, as other chains are not sync'able. One of the chain is the Litecoin that I can recognize, this is probably that IFC (and many others at that time, such as NBL, FST, ALF etc) did not change the message channel, so it gets sync messages. It is not a problem, you can mine without any issues. As long as you have connections. Here are some of my peers FYI.

Which message channel, do you mean IRC?

I don't know the details. I remember at the early stage of IFC sometimes we saw Litecoin upgrade messages. It was disabled in the code later in some fixes, this is not specific to IFC, saw it in many coins.

[wmikrut]

Everything seemed ok a couple days ago then the client stalled again.
I have wiped out my Appdata and loaded the 6 peers above.

I am syncing the client again and, fingers crossed, hope it goes all the way through in a few hours.

Sigh... all this time... 11% Synced.
I'll be back next week 

[rapidfire187]

Hey fisheater. I think It would be good to raise the IFC miners fee to 1 to 2 IFC for a transaction fee (Like DVC) to maintain Network Hashrate and to prevent pool Jumping
BTC

[killdemon]

Block chain and wallet are synchronized very well. I have currently 17 connections. New diff. algo is working great also.
Majority of the miners are at http://coin-base.net/infinitecoin and one coin jumping pool is jumping whenever diff get lover.
You can continue to mine and support this coin, i know i will .

You can trade your IFC at bter, deposit and withdraw is working. Trading at Cryptsy is still on hold, someone should wake up BigVern!