Pages:
Author

Topic: [ANN][KARM] Karma / ₭ / X11 - page 47. (Read 583250 times)

legendary
Activity: 1274
Merit: 1000
June 17, 2015, 12:40:11 PM
Hi my friends,
i installed my wallet, but it dont sync.. put settings in appdata but dont work.. Any ideas?

im not infront of the wallet at the moment - so can only go off what i can remember - and most wallets offer this procedure ...

find some active nodes from here - https://chainz.cryptoid.info/karm/#!network ...

click on the 'node list' of the version of wallet you have ...

open up the debug console ( in the top menu of the wallet ) - click onto the console and type - addnode xxx.xxx.xxx.xxx add ... replacing all the xxx with the ip of the active nodes ...

you can do this a few times with different ip's ...

close the console - and wait for the wallet to sync with that node - and the rest should sync fine ...

you only need one active node to start the sync - and the wallet does the rest ...

at least - that is what i can remember ...

the other way is to add that node in the .conf file in the 'roaming' folder in windows - or the ~/.karmacoin folder in lunux ... by adding - addnode=xxx.xxx.xxx.xxx - in the .conf file ...

hope this helps - even just a little bit ...

#crysx

Code:
addnode=104.243.34.106
addnode=110.23.43.140
addnode=125.237.57.107
addnode=148.251.126.241
addnode=148.251.41.117
addnode=167.114.27.241
addnode=178.125.166.118
addnode=178.232.201.130
addnode=183.12.138.186
addnode=183.154.4.218
addnode=184.175.11.218
addnode=186.50.82.147
addnode=188.165.2.147
addnode=188.165.82.228
addnode=188.226.194.191
addnode=192.95.29.153
addnode=2.49.251.171
addnode=204.11.237.233
addnode=24.102.90.154
addnode=24.15.13.38
addnode=2607:5300:60:2c99::
addnode=2a01:4f8:201:9174::301
addnode=2a02:8109:a080:7ac:11b4:faf7:7adf:cddc
addnode=2a02:8109:a080:7ac:847e:5b85:2e59:9bfd
addnode=2a02:8109:a080:7ac:b4e6:6c:20e4:f43b
addnode=46.10.239.70
addnode=5.101.96.124
addnode=54.84.231.224
addnode=69.254.221.152
addnode=70.91.146.141
addnode=72.128.205.97
addnode=74.93.25.97
addnode=76.10.167.12
addnode=76.95.178.229
addnode=78.193.40.205
addnode=78.206.12.70
addnode=80.202.40.153
addnode=80.219.200.141
addnode=82.136.104.15
addnode=83.104.61.47
addnode=86.97.250.141
addnode=89.11.228.207
addnode=91.66.213.253
addnode=92.99.211.214
addnode=95.133.31.159
addnode=96.58.166.85
addnode=97.79.53.55
addnode=98.253.241.33
hero member
Activity: 711
Merit: 500
CLOAK Trustless Anonymous Cryptocurrency
June 17, 2015, 12:20:23 PM
Team has a new plan? Huh



If there are any plans, only few people know.And who is in the team?

legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
June 17, 2015, 12:16:08 PM
Hi my friends,
i installed my wallet, but it dont sync.. put settings in appdata but dont work.. Any ideas?

im not infront of the wallet at the moment - so can only go off what i can remember - and most wallets offer this procedure ...

find some active nodes from here - https://chainz.cryptoid.info/karm/#!network ...

click on the 'node list' of the version of wallet you have ...

open up the debug console ( in the top menu of the wallet ) - click onto the console and type - addnode xxx.xxx.xxx.xxx add ... replacing all the xxx with the ip of the active nodes ...

you can do this a few times with different ip's ...

close the console - and wait for the wallet to sync with that node - and the rest should sync fine ...

you only need one active node to start the sync - and the wallet does the rest ...

at least - that is what i can remember ...

the other way is to add that node in the .conf file in the 'roaming' folder in windows - or the ~/.karmacoin folder in lunux ... by adding - addnode=xxx.xxx.xxx.xxx - in the .conf file ...

hope this helps - even just a little bit ...

#crysx
sr. member
Activity: 889
Merit: 253
June 17, 2015, 11:52:13 AM
Team has a new plan? Huh
newbie
Activity: 71
Merit: 0
June 17, 2015, 11:48:51 AM
Hi my friends,
i installed my wallet, but it dont sync.. put settings in appdata but dont work.. Any ideas?
hero member
Activity: 711
Merit: 500
CLOAK Trustless Anonymous Cryptocurrency
June 17, 2015, 10:00:55 AM
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. Cheesy


Hey alphi

yeah i contacted Soopy to check out our coin. i was hopping it was not a issue that would require hard fork but seems like we can't escape it.

Yes an other hard fork might hurt us but this is something we have to fix before it escalates to major issues that would really hurt our network. I don't think we should do it asap as i am still trying to return the lost coins to users before they will need to update. How ever this is something we should definitely start to consider and figure out if there is something else we need to modify. Sure we might risk having Cryptsy annoyed and delist us but i think it's better to find out if they will delist us out of annoyance rather then double spends and/or forks issues.

We , Karma users, have been through worse. Let's all come together one more time and openly find the best solution

It is clear that a hard fork is needed. Maybe, this can even be an opportunity to innovate....

KarmaKaguy


Can be transferred to the POS?
sr. member
Activity: 448
Merit: 250
June 17, 2015, 09:30:29 AM
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. Cheesy


Hey alphi

yeah i contacted Soopy to check out our coin. i was hopping it was not a issue that would require hard fork but seems like we can't escape it.

Yes an other hard fork might hurt us but this is something we have to fix before it escalates to major issues that would really hurt our network. I don't think we should do it asap as i am still trying to return the lost coins to users before they will need to update. How ever this is something we should definitely start to consider and figure out if there is something else we need to modify. Sure we might risk having Cryptsy annoyed and delist us but i think it's better to find out if they will delist us out of annoyance rather then double spends and/or forks issues.

We , Karma users, have been through worse. Let's all come together one more time and openly find the best solution

It is clear that a hard fork is needed. Maybe, this can even be an opportunity to innovate....

KarmaKaguy
legendary
Activity: 1274
Merit: 1000
June 16, 2015, 09:41:22 PM
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. Cheesy


Hey alphi

yeah i contacted Soopy to check out our coin. i was hopping it was not a issue that would require hard fork but seems like we can't escape it.

Yes an other hard fork might hurt us but this is something we have to fix before it escalates to major issues that would really hurt our network. I don't think we should do it asap as i am still trying to return the lost coins to users before they will need to update. How ever this is something we should definitely start to consider and figure out if there is something else we need to modify. Sure we might risk having Cryptsy annoyed and delist us but i think it's better to find out if they will delist us out of annoyance rather then double spends and/or forks issues.

We , Karma users, have been through worse. Let's all come together one more time and openly find the best solution
legendary
Activity: 1274
Merit: 1000
June 16, 2015, 09:30:24 PM

yes, thank you for opening that issue with us since back then. We have always had your issue in mind. I figured it needed to hard fork once again so we put it a side for the moment to see what else would pop up.

of course we saw also the hard seeds nodes were not added either. That was also something we knew we have to change.

another thing was the checkpoints. We were expecting HiroS to come back and do the final touches. He just disappeared out of the blue.


And now these finally came back to bite us! I guess the dns seed and checkpoints expiring triggered all these network spams
 
newbie
Activity: 19
Merit: 0
June 12, 2015, 06:27:37 PM

This is awesome! Keep the karma raining!
hero member
Activity: 711
Merit: 500
CLOAK Trustless Anonymous Cryptocurrency
June 11, 2015, 06:14:04 AM
Here is a rap song dedicated to Karma... Enjoy everyone -- all will go well!




Nice video !
newbie
Activity: 19
Merit: 0
June 11, 2015, 05:45:45 AM
Here is a rap song dedicated to Karma... Enjoy everyone -- all will go well!

https://i.imgur.com/MSdP6MA.png
hero member
Activity: 798
Merit: 1000
June 10, 2015, 12:40:18 PM
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. Cheesy
legendary
Activity: 1302
Merit: 1001
Founder - NavCoin Ⓝ
June 10, 2015, 12:16:49 PM
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~
hero member
Activity: 798
Merit: 1000
June 10, 2015, 12:04:19 PM
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.

legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
June 10, 2015, 05:33:35 AM
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 Smiley ...

#crysx
legendary
Activity: 1526
Merit: 1002
Chipcoin Developer
June 10, 2015, 05:27:43 AM
Sighs... One of the basic things you need to change when forking a coin... How is it possible nobody noticed this sooner?  Huh

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
legendary
Activity: 1302
Merit: 1001
Founder - NavCoin Ⓝ
June 10, 2015, 04:24:14 AM
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.
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
June 09, 2015, 10:53:46 PM
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
Pages:
Jump to: