[ANN][KARM] Karma / ₭ / X11

[thevictimofuktyranny]

I uploaded my peers.dat file if anyone is having issues connecting to the network.
peers.dat keeps track of a list of all connections you have made with other karma wallet users.
It does not contain any personal information and so can be deleted or overwritten without affecting your coin holdings.

in order to keep this file updated and running smoothly, you should run our wallet and allow it to fully sync at least once a month.

https://www.dropbox.com/s/dkkxrslilob9pwa/peers.dat?dl=0

please make sure you backup your wallet.dat file ALWAYS before copying any files into your karma data folder.

Yep, that peers.dat file has sorted out the problem

[1713575499]

1713575499

[Alphi]

Yep, that peers.dat file has sorted out the problem

no problemo.. it usually does.. I like to keep my list of peers updated.

[batesresearch]

This is another one among the series I am planning to do:

Another great video!

[bondi]

Just sharing a video about Karma....

Great video.
Thanks for uploading.

[bondi]

This is another one among the series I am planning to do:

Good one.
Keep them coming

[easteagle13]

This is another one among the series I am planning to do:

Good job warf!

[socoban]

Just sharing a video about Karma....

What software did you use for that video creation? Expecially what software did you use to syntetize the voice? I am seeking for free voice syntetizer(Google translate has a voice syntetizer, but it is not officially available ).  Thanks

[Angora]

Need some help getting my windows wallet to sync.  Been running it non-stop for a week and can not get past block 636559.

client version : v0.8.6.5-beta
Open SSL version: OpenSSL 1.0.1h 5 Jun 2014
current block: 636559
total blocks: 748068

debug log:

2015-06-08 21:24:59 received block ec7f0fe68216f49888e9155394c7cd9ae5068eb0e9666ba938b96f42a3006dd4
2015-06-08 21:24:59 Difficulty Retarget - Kimoto Gravity Well
2015-06-08 21:24:59 PastRateAdjustmentRatio = 1.07017
2015-06-08 21:24:59 Before: 1c28b268  0000000028b26800000000000000000000000000000000000000000000000000
2015-06-08 21:24:59 After:  1c28ce95  0000000028ce954cbc955540b48f17ed8499c95fdd14d47be3d6a3d6baee0ab9
2015-06-08 21:25:00 InvalidChainFound: invalid block=ec7f0fe68216f49888e9155394c7cd9ae5068eb0e9666ba938b96f42a3006dd4  height=701317  log2_work=55.148925  date=2015-06-08 21:25:37
2015-06-08 21:25:00 InvalidChainFound:  current best=0744049604bea9d5953e94cbf044fecc291c8137e6f4a6576a33130fc7d4f9fc  height=636559  log2_work=55.121487  date=2015-04-23 23:33:00
2015-06-08 21:25:00 InvalidChainFound: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.
2015-06-08 21:25:00 ProcessBlock: ACCEPTED

PEERS INFO:

{
"addr" : "110.23.43.140:9432",
"services" : "00000003",
"lastsend" : 1433799032,
"lastrecv" : 1433799088,
"bytessent" : 443271,
"bytesrecv" : 7082683,
"blocksrequested" : 0,
"conntime" : 1433795525,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701280,
"banscore" : 0
},
{
"addr" : "92.222.38.197:9432",
"services" : "00000003",
"lastsend" : 1433799137,
"lastrecv" : 1433799086,
"bytessent" : 442389,
"bytesrecv" : 7079719,
"blocksrequested" : 0,
"conntime" : 1433795545,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701281,
"banscore" : 0
},
{
"addr" : "188.165.2.147:9432",
"services" : "00000003",
"lastsend" : 1433799063,
"lastrecv" : 1433799089,
"bytessent" : 578598,
"bytesrecv" : 9421922,
"blocksrequested" : 0,
"conntime" : 1433795545,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701281,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "24.15.13.38:9432",
"services" : "00000003",
"lastsend" : 1433799086,
"lastrecv" : 1433799086,
"bytessent" : 304592,
"bytesrecv" : 4753137,
"blocksrequested" : 0,
"conntime" : 1433795575,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701282,
"banscore" : 0
},
{
"addr" : "212.25.36.96:9432",
"services" : "00000003",
"lastsend" : 1433798984,
"lastrecv" : 1433799097,
"bytessent" : 162224,
"bytesrecv" : 2412196,
"blocksrequested" : 0,
"conntime" : 1433795581,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701282,
"banscore" : 0
},
{
"addr" : "125.237.57.107:9432",
"services" : "00000003",
"lastsend" : 1433799033,
"lastrecv" : 1433799087,
"bytessent" : 28990,
"bytesrecv" : 77519,
"blocksrequested" : 0,
"conntime" : 1433796310,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701290,
"banscore" : 0
},
{
"addr" : "188.165.82.228:9432",
"services" : "00000003",
"lastsend" : 1433799134,
"lastrecv" : 1433799088,
"bytessent" : 24839,
"bytesrecv" : 78260,
"blocksrequested" : 0,
"conntime" : 1433796679,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701293,
"banscore" : 0
},
{
"addr" : "192.95.29.153:9432",
"services" : "00000003",
"lastsend" : 1433799056,
"lastrecv" : 1433799133,
"bytessent" : 7325,
"bytesrecv" : 84532,
"blocksrequested" : 0,
"conntime" : 1433796688,
"version" : 70006,
"subver" : "/Satoshi:0.8.6.5/",
"inbound" : false,
"startingheight" : 701293,
"banscore" : 0
}
]

[CryptoJohn]

Wow, I have not checked karma in months. Good to see activity still exists.

[Alphi]

Need some help getting my windows wallet to sync.  Been running it non-stop for a week and can not get past block 636559.

backup your wallet.dat
delete your blocks, database and chainstate directories from the wallet directory (default is C:\Users\[YOUR_USER_ID]\AppData\Roaming\Karma)
update your peers.dat file (as per details above)
launch the app and sync again from the beginning (the block-chain is only a few hundred MB)

[soopy452000]

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298

Code:

// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~

[chrysophylax]

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298

Code:

// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~

hardfork and move on ...

get it back on track ...

#crysx

[soopy452000]

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298

Code:

// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~

hardfork and move on ...

get it back on track ...

#crysx

yup , everyone will need to agree on this.

[gjhiggins]

these characters contradict with many other coins

Indeed so:

https://github.com/search?p=9&q=unsigned+char+pchMessageStart%5B4%5D+%3D+%7B+0x70%2C+0x35%2C+0x22%2C+0x05+%7D%3B&type=Code&utf8=%E2%9C%93

Cheers

Graham

[BanzaiBTC]

Sighs... One of the basic things you need to change when forking a coin... How is it possible nobody noticed this sooner?  

Hardfork it is then..

edit:

How about we add a few more hardcoded seeds?




And are we certain these are Karma only? Or do other coins have these as well.. Google didnt help me much on this one



All located here: https://github.com/karmateam/karma/blob/master-0.8/src/net.cpp

[chrysophylax]

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298

Code:

// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~

hardfork and move on ...

get it back on track ...

#crysx

yup , everyone will need to agree on this.

as a community - i agree ...

as a fork for the coin - not really ...

the coin for the moment is going nowhere ( as far as development is concerned - not by means of trading which is doing ok ) ...

so for those who have mined and bought and baghold - this is a dead end unless something is done ...

everyone needs to voice their opinions - and i have mine ...

im for the hardfork ... so count my vote as 1 ...

#crysx

[Alphi]

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298

Code:

// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~

hardfork and move on ...

get it back on track ...

#crysx

yup , everyone will need to agree on this.

I am not convinced that a hard fork is necessary.. as stated in the post above, those magic bytes appear in many many other coins so if it was that serious a problem then ALL of those other coins will also be experiencing it.

From what I understand of the problem some people are experiencing a situation where there wallet is attempting to connect to nodes from other coins..  the majority (people who keep their wallets peers.dat file updated) do not appear to have this problem

As a software developer with more than 12 years solid commercial experience I can tell you that making fundamental changes to a piece of software forcing EVERYONE to either update or be locked out of the network (i.e. a Hardfork) is the absolute last resort option. Just imagine if windows and android operating systems forced users to update their entire operating system to the latest version and shut off connection the internet to anyone who did not update, every time they found a security flaw.. that is essentially what a hard fork is.

What I would like to know is that since the default port number for each coin is different such that very few coins actually share the same port number, then how and why is it possible for peers to be showing up from other coin networks?

Surely we should be looking at how this is possible and how we can prevent it from happening.
for example.. is there some code we could add to the peer handling mechanism which would only accept peers that connect via the valid port numbers and reject all others?.

You should not be able to "Addnode" peers with invalid port numbers for example.

And also regarding the suggestion from others about hard forking to hard code seed nodes.. not a very good idea.. since seed nodes come and go over time you will inevitably end up with hard coded seed node links that are broken. Of course nothing is stopping people from compiling their own wallets with additional seed nodes (this does not require a had fork).. and of course nothing is stopping people from simply using a peers.dat file which has update peer information already contained within.

the last time this coin hard forked we became bombarded with complaints from people who had not updated their wallets and were either looking for missing coins or had been mining on the wrong fork for many weeks and lost their newly mined coins as a result.

therefore I will not support any hard fork unless I can be convinced that there is a fatal flaw in the software which cannot be fixed by any other method than a hard fork and I am also convinced that the relevant testing is done on the test-net before switching over to the main network.

let me just remind you all that those magic bytes have been with the coin since day one.. and the coin network has been running successful since day one.

[soopy452000]

Hello All,

I have investigated the matter further and identified the cause of this issue and came to the conclusion that the Blockchain magic of KarmaCoin Here:

At Line :

https://github.com/karmateam/karma/blob/master-0.8/src/main.cpp#L3298

Code:

// The message start string is designed to be unlikely to occur in normal data.
// The characters are rarely used upper ASCII, not valid as UTF-8, and produce
// a large 4-byte int at any alignment.
unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb }; // Karma: increase each by adding 2 to bitcoin's value.

These Magic Bytes should be unique but unfortunately in this case these characters contradict with many other coins thus you guys are experiencing the sync issue.

To correct this problem would require a hardfork and the community will need to agree on that.

Warm Regards,
~SoopY~

hardfork and move on ...

get it back on track ...

#crysx

yup , everyone will need to agree on this.

I am not convinced that a hard fork is necessary.. as stated in the post above, those magic bytes appear in many many other coins so if it was that serious a problem then ALL of those other coins will also be experiencing it.

From what I understand of the problem some people are experiencing a situation where there wallet is attempting to connect to nodes from other coins..  the majority (people who keep their wallets peers.dat file updated) do not appear to have this problem

as a software developer with more than 12 years solid commercial experience I can tell you that making fundamental changes to a piece of software forcing EVERYONE to either update or be locked out of the network (i.e. a Hardfork) is the absolute last resort option.

what I would like to know is that since the default port number for each coin is different such that very few coins actually share the same port number, then how and why is it possible for peers to be showing up from other coin networks?

surely we should be looking at how this is possible and how we can prevent it from happening.
for example.. is there some code we could add to the peer handling mechanism which would only accept peers that connect via the valid port numbers and reject all others?.

You should not be able to "Addnode" peers with invalid port numbers for example.

And also regarding the suggestion from others about hard forking to hard code seed nodes.. not a very good idea.. since seed nodes come and go over time you will inevitably end up with hard coded seed node links that are broken. Of course nothing is stopping people from compiling their own wallets with additional seed nodes (this does not require a had fork).. and of course nothing is stopping people from simply using a peers.dat file which has update peer information already contained within.

the last time this coin hard forked we became bombarded with complaints from people who had not updated their wallets and were either looking for missing coins or had been mining on the wrong fork for many weeks and lost their newly mined coins as a result.

therefore I will not support any hard fork unless I can be convinced that there is a serious flaw in the software which cannot be fixed by any other method than a hard fork and I am also convinced that the relevant testing is done on the test-net before switching over to the main network.

let me just remind you all that those magic bytes have been with the coin since day one.. and the coin network has been running successful since day one.

Thank you for your thoughts mate , but it is with my experience being on the Crypto scene that I'm telling or more suggesting and pointing where the issue is, I've seen this issue commonly on many coins and that too most due to the above said issue. Anyhow I m not here to make or force the community or anyone here to hardfork and as such , I was asked to look into the code provide a fix , I found the error , has notified the community and it is upto the community to do whats best for the coin and themselves. And about the magic bytes being there since the first day and that it wasn't a problem back then is not the case mate , the issue comes when the blockchain matures, not in the beginning.

I didn't mean to disrespect anyone's opinion or ideas guys , I just shared my views on the matter as I was asked to , it is upto the community on doing whatever is needed.

Thank you so very much Alphi for your kind inputs regards to the same and opening up a conversation related to the matter and opening door for further discussions within the community.

Warm Regards,
~SoopY~

[Alphi]

I didn't mean to disrespect anyone's opinion or ideas guys , I just shared my views on the matter as I was asked to , it is upto the community on doing whatever is needed.

Thank you so very much Alphi for your kind inputs regards to the same and opening up a conversation related to the matter and opening door for further discussions within the community.

Warm Regards,
~SoopY~[/b]

It's cool, your not disrespecting anyone. your inputs and advice are very much appreciated. I have just seen too many coins reach for the hard fork option when it really isn't necessary most of the time. we need to always remember that whenever we hard fork, individuals, exchanges and pools, statistic websites etc that are not up to date are effectively locked out of the system until they update..  with a coin like Karma there are so many people who disappear for 6 months and then come back and yell WTF when their wallet is not working.

We also need to acknowledge the economic reality that if a coin is too much hassle for an exchange to support then they will drop it. Cryptsy just recently had problems with their Karma wallet which took them weeks to fix, they have fixed it now but I wonder how long it would take them to update their wallet if we hard forked. I don't like the idea of cryptsy's (or any other exchange's) karma wallet going offline again because they were too busy or simply couldn't be bothered fixing it...

I'm also wondering if those people who are unable to sync are still having the problem after they update their karma peers.dat file from someone who has kept it updated. I know its only a band-aid fix but it seems to have worked well in the past.

P.S. I am not against fixing the problem.. just against hard forking.. so if we have a temporary fix that works for now then we could always change the magic bytes to something more appropriate the next time we actually need to do a hard fork.

[warfwarf]

Here is a rap song dedicated to Karma... Enjoy everyone -- all will go well!

https://i.imgur.com/MSdP6MA.png