[ANN] INFINITECOIN - UPDATE TO 1.8.8 visit INFINITECOIN.COM - page 183.

X68N

hero member

Activity: 672

Merit: 500

Quote from: TECSHARE on December 15, 2013, 08:03:41 AM

Quote from: X68N on December 14, 2013, 05:56:31 PM

is there any handover or official info that the new dev is legit and trustworthy?

no offence, i just want an info.

greetings

https://bitcointalksearch.org/topic/m.3816575

I appointed the current lead developer.

cool

Happy to see.

bitsta

hero member

Activity: 518

Merit: 500

r00t-dev

MAC Wallet not working! -> please fix

TECSHARE

legendary

Activity: 3318

Merit: 2008

First Exclusion Ever

Quote from: X68N on December 14, 2013, 05:56:31 PM

is there any handover or official info that the new dev is legit and trustworthy?

no offence, i just want an info.

greetings

https://bitcointalksearch.org/topic/m.3816575

I appointed the current lead developer.

TECSHARE

legendary

Activity: 3318

Merit: 2008

First Exclusion Ever

Quote from: rapidfire187 on December 09, 2013, 07:31:13 PM

With the 2.0 upgrade please do not go crazy with the tx fee's. Ty in advance Cheesy

IFC:
iHgw3Gc3YSK4N3uhkB3x3nkeKyCqZBGQ9s

What do you think is fair then? No one is telling me what they think....

X68N

hero member

Activity: 672

Merit: 500

is there any handover or official info that the new dev is legit and trustworthy?

no offence, i just want an info.

greetings

crazyearner

legendary

Activity: 1820

Merit: 1001

Quote from: TECSHARE on December 11, 2013, 09:14:10 AM

Does anyone have any suggestions for client features for 2.0? We need to know this as soon as possible so we can integrate them into the next version of the client. What do you want to see in it? Please post here or at www.infinitecointalk.org

feel free to add a feature to allow custom install of data to install on different parts of hdd rather than installing to app data would be a nice added feature.

huyha123

full member

Activity: 126

Merit: 100

the above link seem wrong. I post it again. not sure where I should direct the link to though so I post the main link.

http://www.infinitecointalk.org/

TECSHARE

legendary

Activity: 3318

Merit: 2008

First Exclusion Ever

Does anyone have any suggestions for client features for 2.0? We need to know this as soon as possible so we can integrate them into the next version of the client. What do you want to see in it? Please post here or at www.infinitecointalk.org

uRndUsr

newbie

Activity: 3

Merit: 0

Quote from: TreasureSeeker on December 10, 2013, 12:55:55 AM

Quote from: Jude Austin on December 08, 2013, 03:11:16 PM

Have the message start bits been changed from 1.8.0 to 1.8.5?

I can't get P2Pool to connect to the P2P port of the client and this typically happens when the "magic bits" aren't correct.

Ever since I upgraded to 1.8.5 I have not been able to connect.

I've just tried upgrading TreasureQuarry's P2Pool to 1.8.5 and have had the same problem...failure to connect between p2pool and Infinitecoind on 127.0.0.1:9321

After some downtiime whilst the pool reloaded the blockchain for 1.8.5, I've had to put the pool back to version 1.8 now.

My best guess was that part of the new code is refusing connections from anything that it doesn't recognise as another version of Infinitecoin 1.8.5 . I see the following new code in main.cpp ...

Code:

// A check to make sure only the most recent versions of infinitecoin can connect
   // this is a temporary hack for the time being and will be corrected in the next version
   if( pfrom->strSubVer.find( "Satoshi:1.8" ) == std::string::npos )
   {

   printf("peer %s not using Infinitecoin, Client: %s Protocol %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->strSubVer.c_str(), pfrom->nVersion);
   pfrom->Misbehaving(100);
   pfrom->fDisconnect = true;
   return false;
   }

However, on reading through that code I'm not sure whether this has anything to do with it or not?

TECSHARE/uRrndUsr, could this be looked into, otherwise we may not be able to have any p2pools for IFC in future versions.

Sorry about this, I did not think about P2Pool when making this change. Either way it was needed to clear out non IFC clients.

I have you tried looking at the P2Pool code?

https://github.com/forrestv/p2pool/blob/master/p2pool/bitcoin/p2p.py#L35
https://github.com/forrestv/p2pool/blob/master/p2pool/p2p.py#L61

You could try forcing it to Satoshi:1.8.5, I am unsure if this would break p2pool in anyway tho.

TECSHARE

legendary

Activity: 3318

Merit: 2008

First Exclusion Ever

Quote from: Jude Austin on December 10, 2013, 05:25:31 PM

Quote from: TreasureSeeker on December 10, 2013, 12:55:55 AM

Quote from: Jude Austin on December 08, 2013, 03:11:16 PM

Have the message start bits been changed from 1.8.0 to 1.8.5?

I can't get P2Pool to connect to the P2P port of the client and this typically happens when the "magic bits" aren't correct.

Ever since I upgraded to 1.8.5 I have not been able to connect.

I've just tried upgrading TreasureQuarry's P2Pool to 1.8.5 and have had the same problem...failure to connect between p2pool and Infinitecoind on 127.0.0.1:9321

After some downtiime whilst the pool reloaded the blockchain for 1.8.5, I've had to put the pool back to version 1.8 now.

My best guess was that part of the new code is refusing connections from anything that it doesn't recognise as another version of Infinitecoin 1.8.5 . I see the following new code in main.cpp ...

Code:

// A check to make sure only the most recent versions of infinitecoin can connect
   // this is a temporary hack for the time being and will be corrected in the next version
   if( pfrom->strSubVer.find( "Satoshi:1.8" ) == std::string::npos )
   {

   printf("peer %s not using Infinitecoin, Client: %s Protocol %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->strSubVer.c_str(), pfrom->nVersion);
   pfrom->Misbehaving(100);
   pfrom->fDisconnect = true;
   return false;
   }

However, on reading through that code I'm not sure whether this has anything to do with it or not?

TECSHARE/uRrndUsr, could this be looked into, otherwise we may not be able to have any p2pools for IFC in future versions.

Thank you for stepping in.

Seems when I have an inquiry it doesn't matter.

Is it that your inquiry doesn't matter or that not enough people are contributing with support? I will add tech support to the long list of things everyone expects me to do by myself.

Jude Austin

legendary

Activity: 1140

Merit: 1000

The Real Jude Austin

Quote from: TreasureSeeker on December 10, 2013, 12:55:55 AM

Quote from: Jude Austin on December 08, 2013, 03:11:16 PM

Have the message start bits been changed from 1.8.0 to 1.8.5?

I can't get P2Pool to connect to the P2P port of the client and this typically happens when the "magic bits" aren't correct.

Ever since I upgraded to 1.8.5 I have not been able to connect.

I've just tried upgrading TreasureQuarry's P2Pool to 1.8.5 and have had the same problem...failure to connect between p2pool and Infinitecoind on 127.0.0.1:9321

After some downtiime whilst the pool reloaded the blockchain for 1.8.5, I've had to put the pool back to version 1.8 now.

My best guess was that part of the new code is refusing connections from anything that it doesn't recognise as another version of Infinitecoin 1.8.5 . I see the following new code in main.cpp ...

Code:

// A check to make sure only the most recent versions of infinitecoin can connect
   // this is a temporary hack for the time being and will be corrected in the next version
   if( pfrom->strSubVer.find( "Satoshi:1.8" ) == std::string::npos )
   {

   printf("peer %s not using Infinitecoin, Client: %s Protocol %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->strSubVer.c_str(), pfrom->nVersion);
   pfrom->Misbehaving(100);
   pfrom->fDisconnect = true;
   return false;
   }

However, on reading through that code I'm not sure whether this has anything to do with it or not?

TECSHARE/uRrndUsr, could this be looked into, otherwise we may not be able to have any p2pools for IFC in future versions.

Thank you for stepping in.

Seems when I have an inquiry it doesn't matter.

Hampuz

full member

Activity: 140

Merit: 100

You can trade ifc at www.bter.com , Good volume and good prices.

TECSHARE

legendary

Activity: 3318

Merit: 2008

First Exclusion Ever

Quote from: TreasureSeeker on December 10, 2013, 12:55:55 AM

Quote from: Jude Austin on December 08, 2013, 03:11:16 PM

Have the message start bits been changed from 1.8.0 to 1.8.5?

I can't get P2Pool to connect to the P2P port of the client and this typically happens when the "magic bits" aren't correct.

Ever since I upgraded to 1.8.5 I have not been able to connect.

I've just tried upgrading TreasureQuarry's P2Pool to 1.8.5 and have had the same problem...failure to connect between p2pool and Infinitecoind on 127.0.0.1:9321

After some downtiime whilst the pool reloaded the blockchain for 1.8.5, I've had to put the pool back to version 1.8 now.

My best guess was that part of the new code is refusing connections from anything that it doesn't recognise as another version of Infinitecoin 1.8.5 . I see the following new code in main.cpp ...

Code:

// A check to make sure only the most recent versions of infinitecoin can connect
// this is a temporary hack for the time being and will be corrected in the next version
if( pfrom->strSubVer.find( "Satoshi:1.8" ) == std::string::npos )
{

printf("peer %s not using Infinitecoin, Client: %s Protocol %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->strSubVer.c_str(), pfrom->nVersion);
pfrom->Misbehaving(100);
pfrom->fDisconnect = true;
return false;
}

However, on reading through that code I'm not sure whether this has anything to do with it or not?

TECSHARE/uRrndUsr, could this be looked into, otherwise we may not be able to have any p2pools for IFC in future versions.

Unfortunately because of the bugs in previous clients, until we update to 2.0 we may not be able to support p2p pools.The new client will be out soon and we should be able to put all these updates behind us for good (because it will finally be done right). Unfortunately 1.8.5 was just an interim step so that users could get back to using the client quickly while the remaining client issues are solved correctly and completely. Sorry for this inconvenience.

TECSHARE

legendary

Activity: 3318

Merit: 2008

First Exclusion Ever

Quote from: ?? on ??

Quote

Maybe it is the same number as the number of shills it takes to shill a coin? The network is fine. Just because cryptsy doesn't know how to run an exchange doesn't mean INFINITECOIN is the one with issues. The issues you are crying about are over... move along now, back under the bridge you go...

Techshare is SUPPOSED to be helping you here, but his intention is to lambast someone, instead.

Maybe he'll actually help and answer your question, instead of harrassing me, and calling me names.

If not, maybe his real name is BIG VERN................

troll this, techshare

Yes all I have done is organized an paid for the client fix you are enjoying.

AWSOM

member

Activity: 90

Merit: 10

Can someone pleaaaase tell me how to fix this my ifc client. I downloaded 1.8.5 but it is still not syncing -.-

TreasureSeeker

sr. member

Activity: 455

Merit: 251

Quote from: Jude Austin on December 08, 2013, 03:11:16 PM

Have the message start bits been changed from 1.8.0 to 1.8.5?

I can't get P2Pool to connect to the P2P port of the client and this typically happens when the "magic bits" aren't correct.

Ever since I upgraded to 1.8.5 I have not been able to connect.

I've just tried upgrading TreasureQuarry's P2Pool to 1.8.5 and have had the same problem...failure to connect between p2pool and Infinitecoind on 127.0.0.1:9321

After some downtiime whilst the pool reloaded the blockchain for 1.8.5, I've had to put the pool back to version 1.8 now.

My best guess was that part of the new code is refusing connections from anything that it doesn't recognise as another version of Infinitecoin 1.8.5 . I see the following new code in main.cpp ...

Code:

// A check to make sure only the most recent versions of infinitecoin can connect
   // this is a temporary hack for the time being and will be corrected in the next version
   if( pfrom->strSubVer.find( "Satoshi:1.8" ) == std::string::npos )
   {

   printf("peer %s not using Infinitecoin, Client: %s Protocol %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->strSubVer.c_str(), pfrom->nVersion);
   pfrom->Misbehaving(100);
   pfrom->fDisconnect = true;
   return false;
   }

However, on reading through that code I'm not sure whether this has anything to do with it or not?

TECSHARE/uRrndUsr, could this be looked into, otherwise we may not be able to have any p2pools for IFC in future versions.

rapidfire187

sr. member

Activity: 252

Merit: 250

!!!INCAKOIN!!!

With the 2.0 upgrade please do not go crazy with the tx fee's. Ty in advance Cheesy

IFC:
iHgw3Gc3YSK4N3uhkB3x3nkeKyCqZBGQ9s

everd1213

newbie

Activity: 2

Merit: 0

Version 1.8.5 presents me the following message:

EXCEPTION: 11DbException
Db::put: Not enough space
C:\infinitecoin-1.8.5-win32\infinitecoin-qt.exe in ProcessMessage()

Now what...
Btw, got 620GB free diskspace.

Edit: Restored 1.8.0 and all is working again.

limek93

member

Activity: 69

Merit: 10

no i bought 1 mil for 5 dollars. lol and 1 mil is worth 2 ltc on cryptsy at the moment..

limek93

member

Activity: 69

Merit: 10

lol asshole pond..

anyways.. I bought 1mil infinitecoins on ebay a month ago. The user sent them to me and sent me the transaction id.

http://exploretheblocks.com:2750/tx/5b439f8a2014d9fbd6bd0d84d042c72af4eb1f1df24123beb21757bb8c55ff53

The thing is my IFC qt wasn't synced so I never received the coins and kind of forgot about them. Now that they are worth something I got my wallet synced by following the guide and when it finished syncing I still never got my transaction. It doesn't say anything in the qt, not even unconfirmed transaction. So how do I go about getting my 1mil coins in my wallet? I have the wallet.dat for the wallet I used previously. On the link above, it shows that it is a "Not yet reedemed" transaction. What do I do to get my coins? Thanks Smiley

10k ifc to the user who solves this for me

Topic: [ANN] INFINITECOIN - UPDATE TO 1.8.8 visit INFINITECOIN.COM - page 183. (Read 155194 times)