Bitcoin Forum
September 17, 2019, 05:57:18 PM *
News: If you like a topic and you see an orange "bump" link, click it. More info.
 
   Home   Help Search Login Register More  
Pages: « 1 ... 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 [69] 70 71 72 73 74 75 76 77 78 79 80 81 82 »
  Print  
Author Topic: [ANN] Infinitecoin - IFC | V1.8 Released! *Mandatory Upgrade, upgrade ASAP*  (Read 199189 times)
c1010010
Sr. Member
****
Offline Offline

Activity: 275
Merit: 250



View Profile
September 27, 2013, 12:29:24 AM
 #1361

8 active.

Beauty.

         YOU TOO CAN BE A MILLIONAIRE – INFINITECOIN Infinite possibilities – http://infinitecointalk.org          
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Stouse49
Full Member
***
Offline Offline

Activity: 209
Merit: 100



View Profile
September 27, 2013, 01:41:38 AM
 #1362

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

BTC:
NaNaec
Full Member
***
Offline Offline

Activity: 128
Merit: 100


View Profile
September 27, 2013, 07:31:51 AM
 #1363

any news about time of start of trading on cryptsy?
wmikrut
Hero Member
*****
Offline Offline

Activity: 632
Merit: 500



View Profile WWW
September 27, 2013, 05:46:35 PM
 #1364

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:

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

I will NEVER ask for any kind of funds up front in a buy/sale of anything on bitcointalk.

BM-2cTFihJKmSwusMAoYuUHPvpx56Jozv64KK
monocolor
Hero Member
*****
Offline Offline

Activity: 766
Merit: 620


Own ONION


View Profile WWW
September 27, 2013, 06:27:47 PM
 #1365

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
    }

           ▀██▄ ▄██▀
            ▐█████▌
           ▄███▀███▄
         ▄████▄  ▀███▄
       ▄███▀ ▀██▄  ▀███▄
     ▄███▀  ▄█████▄  ▀███▄
   ▄███▀  ▄███▀ ▀███▄  ▀███▄
  ███▀  ▄████▌   ▐████▄  ▀███
 ███   ██▀  ██▄ ▄██  ▀██   ███
███   ███  ███   ███  ███   ███
███   ███   ███████   ███   ███
 ███   ███▄▄       ▄▄███   ███
  ███▄   ▀▀█████████▀▀   ▄███
   ▀████▄▄           ▄▄████▀
      ▀▀███████████████▀▀
DeepOnion
.Anonymous and Untraceable.
ANN  Whitepaper  Facebook  Twitter  Telegram  Discord 





      ▄▄██████████▄▄
    ▄███▀▀      ▀▀█▀   ▄▄
   ███▀              ▄███
  ███              ▄███▀   ▄▄
 ███▌  ▄▄▄▄      ▄███▀   ▄███
▐███  ██████   ▄███▀   ▄███▀
███▌ ███  ███▄███▀   ▄███▀
███▌ ███   ████▀   ▄███▀
███▌  ███   █▀   ▄███▀  ███
▐███   ███     ▄███▀   ███
 ███▌   ███  ▄███▀     ███
  ███    ██████▀      ███
   ███▄             ▄███
    ▀███▄▄       ▄▄███▀
      ▀▀███████████▀▀
.
erk
Hero Member
*****
Offline Offline

Activity: 812
Merit: 500


View Profile
September 27, 2013, 06:30:26 PM
 #1366

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
Hero Member
*****
Offline Offline

Activity: 766
Merit: 620


Own ONION


View Profile WWW
September 27, 2013, 07:26:27 PM
 #1367

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.

           ▀██▄ ▄██▀
            ▐█████▌
           ▄███▀███▄
         ▄████▄  ▀███▄
       ▄███▀ ▀██▄  ▀███▄
     ▄███▀  ▄█████▄  ▀███▄
   ▄███▀  ▄███▀ ▀███▄  ▀███▄
  ███▀  ▄████▌   ▐████▄  ▀███
 ███   ██▀  ██▄ ▄██  ▀██   ███
███   ███  ███   ███  ███   ███
███   ███   ███████   ███   ███
 ███   ███▄▄       ▄▄███   ███
  ███▄   ▀▀█████████▀▀   ▄███
   ▀████▄▄           ▄▄████▀
      ▀▀███████████████▀▀
DeepOnion
.Anonymous and Untraceable.
ANN  Whitepaper  Facebook  Twitter  Telegram  Discord 





      ▄▄██████████▄▄
    ▄███▀▀      ▀▀█▀   ▄▄
   ███▀              ▄███
  ███              ▄███▀   ▄▄
 ███▌  ▄▄▄▄      ▄███▀   ▄███
▐███  ██████   ▄███▀   ▄███▀
███▌ ███  ███▄███▀   ▄███▀
███▌ ███   ████▀   ▄███▀
███▌  ███   █▀   ▄███▀  ███
▐███   ███     ▄███▀   ███
 ███▌   ███  ▄███▀     ███
  ███    ██████▀      ███
   ███▄             ▄███
    ▀███▄▄       ▄▄███▀
      ▀▀███████████▀▀
.
wmikrut
Hero Member
*****
Offline Offline

Activity: 632
Merit: 500



View Profile WWW
September 28, 2013, 04:48:07 AM
 #1368


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  Roll Eyes

I will NEVER ask for any kind of funds up front in a buy/sale of anything on bitcointalk.

BM-2cTFihJKmSwusMAoYuUHPvpx56Jozv64KK
rapidfire187
Sr. Member
****
Offline Offline

Activity: 252
Merit: 250


!!!INCAKOIN!!!


View Profile
September 28, 2013, 06:32:55 AM
 #1369

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

www.incakoin.com   http://nka.dencoinpools.com
NKA:NN1sE6odEKrbKpBqt56vw5jJoitDrCn9HD
▂▃▅▇█▓▒░۩۞۩ ۩۞۩░▒▓█▇▅▃▂
killdemon
Full Member
***
Offline Offline

Activity: 212
Merit: 100


View Profile
September 28, 2013, 08:09:55 AM
Last edit: September 28, 2013, 08:21:52 AM by killdemon
 #1370

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

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


anoncuber
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
September 28, 2013, 03:03:23 PM
Last edit: September 28, 2013, 03:20:13 PM by anoncuber
 #1371

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

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



Fantastic .. another bit of strip-mining in progress I think! The pool has now not found a single block in over 2 hours and the hashrate has jumped to nearly 300MH (now 416MH just a few mins later!) from a peaceful 40 odd  Angry
killdemon
Full Member
***
Offline Offline

Activity: 212
Merit: 100


View Profile
September 28, 2013, 03:24:05 PM
 #1372

pool was down.

yugo23
Sr. Member
****
Offline Offline

Activity: 476
Merit: 252


View Profile
September 28, 2013, 03:39:39 PM
 #1373

Any news when IFC will be back on Cryptsy?
tokyoghetto
Legendary
*
Offline Offline

Activity: 1232
Merit: 1000


View Profile
September 28, 2013, 04:13:22 PM
 #1374

seems like http://coin-base.net/infinitecoin/index.php is still down. I think this is the only pool running 1.7 client. I wish ifc.scryptmining.com and other IFC pools would update their clients.
killdemon
Full Member
***
Offline Offline

Activity: 212
Merit: 100


View Profile
September 28, 2013, 05:15:27 PM
 #1375

you can mine at  http://treasurequarry.com:9844 also updated with v1.7

fisheater
Hero Member
*****
Offline Offline

Activity: 770
Merit: 602



View Profile
September 28, 2013, 06:01:05 PM
 #1376

The IFC blockchain and mining is going on fine, no problem. I hope cryptsy will soon restore the trading of IFC.
zackclark70
Legendary
*
Offline Offline

Activity: 840
Merit: 1000

ADT developer


View Profile
September 28, 2013, 06:08:45 PM
 #1377

The IFC blockchain and mining is going on fine, no problem. I hope cryptsy will soon restore the trading of IFC.

they paused it due to your request just tell them you are happy its all working now and they can un pause it

ADT donation address >ALMA4h9mQLPTQu96AFwgNu6jjviHBowonk
BTC donation address >17KZ9E1PmTUMmosfb1xcapGRoQSKew8M3P
Petr1fied
Hero Member
*****
Offline Offline

Activity: 630
Merit: 502


View Profile
September 28, 2013, 06:21:26 PM
 #1378

The IFC blockchain and mining is going on fine, no problem. I hope cryptsy will soon restore the trading of IFC.

I've attempted syncing from nothing with v1.7 at least 5 times now and I cannot get past block 248,093 no matter how many times I try:

Code:
received block 6e79edc0751588e349dd
  nActualTimespan = 3049  before bounds
GetNextWorkRequired RETARGET
nTargetTimespan = 3600    nActualTimespan = 3049
Before: 1e0fffff  00000fffff000000000000000000000000000000000000000000000000000000
After:  1e0d8d14  00000d8d14c55555555555555555555555555555555555555555555555555555
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 86.150.227.43:9321
Disconnected 86.150.227.43:9321 for misbehavior (score=100)

It looks to me like there may be an issue in the blockchain you've all manually downloaded and being building upon.
fisheater
Hero Member
*****
Offline Offline

Activity: 770
Merit: 602



View Profile
September 28, 2013, 06:23:26 PM
 #1379

The IFC blockchain and mining is going on fine, no problem. I hope cryptsy will soon restore the trading of IFC.

they paused it due to your request just tell them you are happy its all working now and they can un pause it

I just sent them another email stating that everything is running smooth and the previous issues have been resolved. I asked them to restore the trading for IFC.
fisheater
Hero Member
*****
Offline Offline

Activity: 770
Merit: 602



View Profile
September 28, 2013, 06:33:29 PM
 #1380

The IFC blockchain and mining is going on fine, no problem. I hope cryptsy will soon restore the trading of IFC.

I've attempted syncing from nothing with v1.7 at least 5 times now and I cannot get past block 248,093 no matter how many times I try:

Code:
received block 6e79edc0751588e349dd
  nActualTimespan = 3049  before bounds
GetNextWorkRequired RETARGET
nTargetTimespan = 3600    nActualTimespan = 3049
Before: 1e0fffff  00000fffff000000000000000000000000000000000000000000000000000000
After:  1e0d8d14  00000d8d14c55555555555555555555555555555555555555555555555555555
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
disconnecting node 86.150.227.43:9321
Disconnected 86.150.227.43:9321 for misbehavior (score=100)

It looks to me like there may be an issue in the blockchain you've all manually downloaded and being building upon.

Block 248093 is not where it has problem, the problem was long ago (246953). You already passed that point. Please try to sync with these nodes using addnode (from my peers):

    {
        "addr" : "68.42.103.11:9321",
        "services" : "00000001",
        "lastsend" : 1380393168,
        "lastrecv" : 1380393168,
        "conntime" : 1380392845,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 259331,
        "banscore" : 0
    },
    {
        "addr" : "86.150.227.43:9321",
        "services" : "00000001",
        "lastsend" : 1380393168,
        "lastrecv" : 1380393168,
        "conntime" : 1380392850,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 259331,
        "banscore" : 0
    },
    {
        "addr" : "71.218.181.245:9321",
        "services" : "00000001",
        "lastsend" : 1380393156,
        "lastrecv" : 1380393168,
        "conntime" : 1380392851,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 259331,
        "banscore" : 0
    },
    {
        "addr" : "76.110.255.33:9321",
        "services" : "00000001",
        "lastsend" : 1380393162,
        "lastrecv" : 1380393168,
        "conntime" : 1380392941,
        "version" : 60001,
        "subver" : "/Satoshi:1.7.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 259337,
        "banscore" : 0
    },
Pages: « 1 ... 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 [69] 70 71 72 73 74 75 76 77 78 79 80 81 82 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!