[ANN][KARM] Karma / ₭ / X11

[cryptowho]

new wallet is not syncing for me.

• windows
• not my first wallet upgrade but very frustrating non the less
• backed up wallet.dat
• installed new wallet
• deleted roaming files(although not really necessary because of name change)
• pasted wallet.dat in new roaming files

wallet opens and shows history but does not connect to network.

good job with the trying to moving the coin forward. To be honest I had given up on Karma myself but someone on the Poloniex site in the troll box re-sparked my interest enough to read about the changes.
Been mining again and have a couple million on pool site but cant move with broken wallet.

Thanks

same here, not syncing and it's already more than 24 hours.
Tried at 2 pcs, one with win 7 no conf and another one win 8.1 with conf.
Checked the log and all the connection to the nodes are "time out".

Anybody have same problem ?

Same here as I haven't been able find an active node since I decided to retrieve some freshly purchased karma yesterday evening (5/5) using the latest Karma-v0.8.6.2.5 Windows wallet on Win7, 32bit. Also unsucessfully tried adding "addnode=" entries in karma.conf from two old postings (one in the the original bitcointalk thread and another in the cryptocointalk forum) with debug.log showing time-outs and lastseen=70-100 mins for all entries. Presumeably other nodes are syncing therefore if anyone could share a few active nodes to add to karma.conf (which I believe was renamed from karmacoin.conf). that would be greatly appreciated.

On another note, Greetings ALL, this is my first bitcointalk posting. Doing good with Karma really resonates and there's a cause close to home I'd like to consider funding. Hopefully I can get my wallet syncing to retrieve my karma and possibly participate in Karmashares which I understand needs to be funded from a private wallet. Any help would be greatly appreciated.

Welcome. You should subscribe on reddit subforums. There a different kind of activity there.

as far as not synching. can you all try to add these nodes and tell me if you were able to connect?

addnode=54.201.183.106:9432
addnode=148.251.70.194:9432
addnode=76.23.205.36:9432
addnode=115.28.129.207:9432
addnode=173.74.26.226:9432
addnode=95.85.48.77:9432
addnode=188.165.194.96:9432

post back here if you need help adding them to the config file

now that i think about it. it could be your problems with firewalls. most likely window firewall prevents certain port numbers to recieve information. Here is that you should do.

manually edit the karma's .conf file

1. go to \AppData\Roaming\karmacoin folder

2. in there you should see a config file. if you do, just edit to with the info below

3. this is adding a new configuration file. what you do is you open a new text file. (right click--new--"text document")
 
you open this with a text editor. most likely notepad.
make sure there is nothing in the document. then add all these lines

rpcuser=karma
rpcpassword=karmaisawesome
port=9754
rpcport=9755
rpcallowip=127.0.0.1
rpcallowip=192.168.0.*
daemon=1
server=1
addnode=81.157.60.163
addnode=151.228.221.61
addnode=107.150.7.246
addnode=64.121.119.180
addnode=67.169.239.87
addnode=37.251.42.238
addnode=91.61.69.254
addnode=174.131.83.65
addnode=217.119.117.131
addnode=93.79.24.77
addnode=178.41.10.214
addnode=54.201.183.106:9432
addnode=148.251.70.194:9432
addnode=76.23.205.36:9432
addnode=115.28.129.207:9432
addnode=173.74.26.226:9432
addnode=95.85.48.77:9432
addnode=188.165.194.96:9432

4. all the red color text are options you can change . the blue color port number is the text you need to choose from : 8800's - 9999. You chose a port number that you will not use it by other devices and more importantly by other coins.
for expample karma port : 9755 , bitcoin port : 9788 , litecoin port: 8867 etc.

5. then save the document as karmacoin.conf and make sure our select from the drop down menu of "save type as" : All files(*). this is important. this will save the file as config file and not as a text file. if you see "karmacoin.conf.txt" file = bad  if you see "karmacoin.conf" file = good

6. close the wallet if it was opened an then open it again.


Most likely why some of you are not syncing is because the port the wallet is trying to use is above the range i mention in step 4 and window firewall is preventing your computer from receiving any outside data. you prevent this by using a port range between 8000's - 9000's

Hopefully this should do the trick

[Alphi]

now that i think about it. it could be your problems with firewalls. most likely window firewall prevents certain port numbers to recieve information. Here is that you should do.

the first time you run any internet enabled application the windows firewall (in windows 7 and im assuming 8 ) asks you if you want to allow that application to talk to the internet.
if you say yes then those ports are opened up automatically, if you say no then the app is dead in the water and windows wont ask you again next time you run it.

if you run a new version of the client from a different folder windows will ask you again if you want to allow the app to talk to the internet..

also you don't need RPC port and Daemon = 1 and Server=1 for running the client as a wallet only.

they are used when the client app is running as a daemon so you can do funky things like run mining pools and web services against and tell it to do things remotely etc.

all of the RPC settings should be kept TIGHTLY under lock and key (ie dont tell anyone) because if someone has those settings and your IP address they can tell your client to do things like send money remotely (if your wallet is unencrypted, which it is by default for every new wallet)....

if those are your RPC username and password then I suggest you change them since you just told everyone..

[cryptowho]

now that i think about it. it could be your problems with firewalls. most likely window firewall prevents certain port numbers to recieve information. Here is that you should do.

the first time you run any internet enabled application the windows firewall (in windows 7 and im assuming 8 ) asks you if you want to allow that application to talk to the internet.
if you say yes then those ports are opened up automatically, if you say no then the app is dead in the water and windows wont ask you again next time you run it.

if you run a new version of the client from a different folder windows will ask you again if you want to allow the app to talk to the internet..

also you don't need RPC port and Daemon = 1 and Server=1 for running the client as a wallet only.

they are used when the client app is running as a daemon so you can do funky things like run mining pools and web services against and tell it to do things remotely etc.

all of the RPC settings should be kept TIGHTLY under lock and key (ie dont tell anyone) because if someone has those settings and your IP address they can tell your client to do things like send money remotely (if your wallet is unencrypted, which it is by default for every new wallet)....

if those are your RPC username and password then I suggest you change them since you just told everyone..

normally yes. but it doesnt right away. if you install a wallet and the wallet has the port at 10000. firewall will block it with out a prompt. if you re-start your comp and then run the wallet you will get the prompt

by introducing a new configuere file and set the port to more firewall friendly ports between 8800-9999 then you can synch up with out having to create firewalls prompts

only the rpcpassword is dangerous to share. (of course i didnt show my pass nor the port i am using )  But the level of you getting hack its not that great. those port are port that windows firewall and antivirus monitor hevely. especially port lower , like pools use. I am not worried.

but since these users just recently installed the wallet. they must have not restarted their comps yet. or windows firewall does not give the promt to unblock. it just blocks it for them automatically. I am confident that if they put the addnodes i suggested and use a port number between 8000-9999 they will synch right way.

also by setting up the configure file i also solve any future question if they want to solomine : )

[Alphi]

now that i think about it. it could be your problems with firewalls. most likely window firewall prevents certain port numbers to recieve information. Here is that you should do.

the first time you run any internet enabled application the windows firewall (in windows 7 and im assuming 8 ) asks you if you want to allow that application to talk to the internet.
if you say yes then those ports are opened up automatically, if you say no then the app is dead in the water and windows wont ask you again next time you run it.

if you run a new version of the client from a different folder windows will ask you again if you want to allow the app to talk to the internet..

also you don't need RPC port and Daemon = 1 and Server=1 for running the client as a wallet only.

they are used when the client app is running as a daemon so you can do funky things like run mining pools and web services against and tell it to do things remotely etc.

all of the RPC settings should be kept TIGHTLY under lock and key (ie dont tell anyone) because if someone has those settings and your IP address they can tell your client to do things like send money remotely (if your wallet is unencrypted, which it is by default for every new wallet)....

if those are your RPC username and password then I suggest you change them since you just told everyone..

normally yes. but it doesnt right away. if you install a wallet and the wallet has the port at 10000. firewall will block it with out a prompt. if you re-start your comp and then run the wallet you will get the prompt

by introducing a new configuere file and set the port to more firewall friendly ports between 8800-9999 then you can synch up with out having to create firewalls prompts

only the rpcpassword is dangerous to share. (of course i didnt show my pass nor the port i am using )  But the level of you getting hack its not that great. those port are port that windows firewall and antivirus monitor hevely. especially port lower , like pools use. I am not worried.

but since these users just recently installed the wallet. they must have not restarted their comps yet. or windows firewall does not give the promt to unblock. it just blocks it for them automatically. I am confident that if they put the addnodes i suggested and use a port number between 8000-9999 they will synch right way.

also by setting up the configure file i also solve any future question if they want to solomine : )

yep but I think you missed my point about RPC settings (including RPC port) being only used when the client is used as a daemon/RPC Server its not used by the client and its peers for transaction processing at all.
They all use the same hard coded port address..

you can change the Port number using the "port=" parameter  (not to be confused with RPC port, port= is there so you can move onto a testnet) but then it wont be able to talk to any of the other peers.

https://litecoin.info/Litecoin.conf

also the risk of getting "hacked" isn't so great at the moment because its still under the radar. the fact that Karma is so small that few people want to toy with it is no reason at all to get complacent.

[easteagle13]

new wallet is not syncing for me.

• windows
• not my first wallet upgrade but very frustrating non the less
• backed up wallet.dat
• installed new wallet
• deleted roaming files(although not really necessary because of name change)
• pasted wallet.dat in new roaming files

wallet opens and shows history but does not connect to network.

good job with the trying to moving the coin forward. To be honest I had given up on Karma myself but someone on the Poloniex site in the troll box re-sparked my interest enough to read about the changes.
Been mining again and have a couple million on pool site but cant move with broken wallet.

Thanks

same here, not syncing and it's already more than 24 hours.
Tried at 2 pcs, one with win 7 no conf and another one win 8.1 with conf.
Checked the log and all the connection to the nodes are "time out".

Anybody have same problem ?

Same here as I haven't been able find an active node since I decided to retrieve some freshly purchased karma yesterday evening (5/5) using the latest Karma-v0.8.6.2.5 Windows wallet on Win7, 32bit. Also unsucessfully tried adding "addnode=" entries in karma.conf from two old postings (one in the the original bitcointalk thread and another in the cryptocointalk forum) with debug.log showing time-outs and lastseen=70-100 mins for all entries. Presumeably other nodes are syncing therefore if anyone could share a few active nodes to add to karma.conf (which I believe was renamed from karmacoin.conf). that would be greatly appreciated.

On another note, Greetings ALL, this is my first bitcointalk posting. Doing good with Karma really resonates and there's a cause close to home I'd like to consider funding. Hopefully I can get my wallet syncing to retrieve my karma and possibly participate in Karmashares which I understand needs to be funded from a private wallet. Any help would be greatly appreciated.

Welcome. You should subscribe on reddit subforums. There a different kind of activity there.

as far as not synching. can you all try to add these nodes and tell me if you were able to connect?

addnode=54.201.183.106:9432
addnode=148.251.70.194:9432
addnode=76.23.205.36:9432
addnode=115.28.129.207:9432
addnode=173.74.26.226:9432
addnode=95.85.48.77:9432
addnode=188.165.194.96:9432

post back here if you need help adding them to the config file

now that i think about it. it could be your problems with firewalls. most likely window firewall prevents certain port numbers to recieve information. Here is that you should do.

manually edit the karma's .conf file

1. go to \AppData\Roaming\karmacoin folder

2. in there you should see a config file. if you do, just edit to with the info below

3. this is adding a new configuration file. what you do is you open a new text file. (right click--new--"text document")
 
you open this with a text editor. most likely notepad.
make sure there is nothing in the document. then add all these lines

rpcuser=karma
rpcpassword=karmaisawesome
rpcport=9755
rpcallowip=127.0.0.1
rpcallowip=192.168.0.*
daemon=1
server=1
addnode=81.157.60.163
addnode=151.228.221.61
addnode=107.150.7.246
addnode=64.121.119.180
addnode=67.169.239.87
addnode=37.251.42.238
addnode=91.61.69.254
addnode=174.131.83.65
addnode=217.119.117.131
addnode=93.79.24.77
addnode=178.41.10.214
addnode=54.201.183.106:9432
addnode=148.251.70.194:9432
addnode=76.23.205.36:9432
addnode=115.28.129.207:9432
addnode=173.74.26.226:9432
addnode=95.85.48.77:9432
addnode=188.165.194.96:9432

4. all the red color text are options you can change . the blue color port number is the text you need to choose from : 8800's - 9999. You chose a port number that you will not use it by other devices and more importantly by other coins.
for expample karma port : 9755 , bitcoin port : 9788 , litecoin port: 8867 etc.

5. then save the document as karmacoin.conf and make sure our select from the drop down menu of "save type as" : All files(*). this is important. this will save the file as config file and not as a text file. if you see "karmacoin.conf.txt" file = bad  if you see "karmacoin.conf" file = good

6. close the wallet if it was opened an then open it again.


Most likely why some of you are not syncing is because the port the wallet is trying to use is above the range i mention in step 4 and window firewall is preventing your computer from receiving any outside data. you prevent this by using a port range between 8000's - 9000's

Hopefully this should do the trick

+1 ! You rock making tutorial cryptowho!

[cryptowho]

now that i think about it. it could be your problems with firewalls. most likely window firewall prevents certain port numbers to recieve information. Here is that you should do.

the first time you run any internet enabled application the windows firewall (in windows 7 and im assuming 8 ) asks you if you want to allow that application to talk to the internet.
if you say yes then those ports are opened up automatically, if you say no then the app is dead in the water and windows wont ask you again next time you run it.

if you run a new version of the client from a different folder windows will ask you again if you want to allow the app to talk to the internet..

also you don't need RPC port and Daemon = 1 and Server=1 for running the client as a wallet only.

they are used when the client app is running as a daemon so you can do funky things like run mining pools and web services against and tell it to do things remotely etc.

all of the RPC settings should be kept TIGHTLY under lock and key (ie dont tell anyone) because if someone has those settings and your IP address they can tell your client to do things like send money remotely (if your wallet is unencrypted, which it is by default for every new wallet)....

if those are your RPC username and password then I suggest you change them since you just told everyone..

normally yes. but it doesnt right away. if you install a wallet and the wallet has the port at 10000. firewall will block it with out a prompt. if you re-start your comp and then run the wallet you will get the prompt

by introducing a new configuere file and set the port to more firewall friendly ports between 8800-9999 then you can synch up with out having to create firewalls prompts

only the rpcpassword is dangerous to share. (of course i didnt show my pass nor the port i am using )  But the level of you getting hack its not that great. those port are port that windows firewall and antivirus monitor hevely. especially port lower , like pools use. I am not worried.

but since these users just recently installed the wallet. they must have not restarted their comps yet. or windows firewall does not give the promt to unblock. it just blocks it for them automatically. I am confident that if they put the addnodes i suggested and use a port number between 8000-9999 they will synch right way.

also by setting up the configure file i also solve any future question if they want to solomine : )

yep but I think you missed my point about RPC settings (including RPC port) being only used when the client is used as a daemon/RPC Server its not used by the client and its peers for transaction processing at all.
They all use the same hard coded port address..

you can change the Port number using the "port=" parameter  (not to be confused with RPC port, port= is there so you can move onto a testnet) but then it wont be able to talk to any of the other peers.

https://litecoin.info/Litecoin.conf

also the risk of getting "hacked" isn't so great at the moment because its still under the radar. the fact that Karma is so small that few people want to toy with it is no reason at all to get complacent.

ahh.. you are correct. i will edit. i meant to say change the Port. and therefore also the RPCport to be almost the same. usually the Port # + 1 , so it is easy to remember...

[tim14]

I tried setting up conf file/addnode as per instructions above and still zero connect. Any other ideas or nodes?

[cryptowho]

either way. most likely the new addnodes should solve their problems. rpc port will allow them to solomine if they want to. use a 12 unit long password to be safe. encrypt the wallet with password to be supper safe  : )

[cryptowho]

I tried setting up conf file/addnode as per instructions above and still zero connect. Any other ideas or nodes?

give it some time(30 mins)

if nothing. restart comp.

if nothing again. back up your wallet (wallet.dat) then delete everything in the karmacoin folder except the wallet.dat file. and reinstall the wallet

[tim14]

I tried setting up conf file/addnode as per instructions above and still zero connect. Any other ideas or nodes?

give it some time(30 mins)

if nothing. restart comp.

if nothing again. back up your wallet (wallet.dat) then delete everything in the karmacoin folder except the wallet.dat file. and reinstall the wallet

I will try that, Thanks.

[Alphi]

ahh.. you are correct. i will edit. i meant to say change the Port. and therefore also the RPCport to be almost the same. usually the Port # + 1 , so it is easy to remember...

sorry to be a pain but to be clear DO NOT CHANGE THE PORT PARAMETER in the Karma config file... if you do that then you will broadcast and listen on a port that nobody else is using so you wont be able to connect unless other people are using the same port. the port parameter is hard coded by the devs that is why that parameter is not needed in a config file. (this is done because each altcoin uses a different port). This is a limitation of Bitcoin, Litecoin and any other coin based on those coins.. because they don't use port ranges they can only talk and listen on one port at a time. the port parameter is only there so that people can switch to a different network like a testnet for development work.

If you change the RPC port parameter it will do nothing with regards to connecting to peers.

I think we should step back from getting people to hack their config files (because you can seriously break things if you don't know what your doing) and just upload a working Peers.dat file...

as far as I am aware the peers.dat file contains no personal information, its just a list of nodes (ip addresses) and whether they are active or how long they have been idle for.

sorry to be a stickler but this discussion has probably confused the crap out of any newbie trying to get their wallet working thats why i'm suggesting that we just put up a peers.dat file.. much simpler and easier to follow

[Delaforetnoire]

Alphi or cryptowho, can you make us a good peers.dat or .conf file with updated nodes with a little explanation ? I will post it on the first page of the thread.

Thank you 

[Alphi]

Alphi or cryptowho, can you make us a good peers.dat or .conf file with updated nodes with a little explanation ? I will post it on the first page of the thread.

Thank you  

sure thing.. do you have access to wherever the windows client download is located?  I'll put my peers.dat on my dropbox so you can copy it up to the server but I wont leave it up for long. just give me a few mins to update it

[Delaforetnoire]

Just Pm when you will have the link, I don't have access to the download location, kosmost has.

[easteagle13]

Alphi or cryptowho, can you make us a good peers.dat or .conf file with updated nodes with a little explanation ? I will post it on the first page of the thread.

Thank you  

sure thing.. do you have access to wherever the windows client download is located?  I'll put my peers.dat on my dropbox so you can copy it up to the server but I wont leave it up for long. just give me a few mins to update it

+1 !

[Alphi]

Just Pm when you will have the link, I don't have access to the download location, kosmost has.

Here you go guys...

if you are having trouble connecting to peers and  want to update your peers.dat file

https://www.dropbox.com/sh/ebjrqthy206rlaq/U70ksPbIep


I will leave the link up for a week.. please let the powers that be know so they can add it to alongside the windows client..

hope it works...

PS.. I do not use a config file and everything is working fine here... to check that your config file isn't causing a problem just move it or rename it and restart the client.. (you can always move it back after)

also make sure you are running the wallet with the logo that matches the front page of this thread... if it has the old logo then you are using the old wallet and you should update it

[Delaforetnoire]

Just Pm when you will have the link, I don't have access to the download location, kosmost has.

Here you go guys...

if you are having trouble connecting to peers and  want to update your peers.dat file

https://www.dropbox.com/sh/ebjrqthy206rlaq/U70ksPbIep


I will leave the link up for a week.. please let the powers that be know so they can add it to alongside the windows client..

hope it works...

PS.. I do not use a config file and everything is working fine here... to check that your config file isn't causing a problem just move it or rename it and restart the client.. (you can always move it back after)

also make sure you are running the wallet with the logo that matches the front page of this thread... if it has the old logo then you are using the old wallet and you should update it

Thank you Alphi !

[dingyuanchang]

10 X have been completed?

[altcoingood]

You can add this node to your karmacoin.conf if you have problems

addnode=altcoin.dk:9432

it's located in germany, has ~50 connections atm and can handle up to 1000 connections.

(if you are uneasy about adding my node, i also run the blockexplorer infrastructure)

[smokyho]

Just Pm when you will have the link, I don't have access to the download location, kosmost has.

Here you go guys...

if you are having trouble connecting to peers and  want to update your peers.dat file

https://www.dropbox.com/sh/ebjrqthy206rlaq/U70ksPbIep


I will leave the link up for a week.. please let the powers that be know so they can add it to alongside the windows client..

hope it works...

PS.. I do not use a config file and everything is working fine here... to check that your config file isn't causing a problem just move it or rename it and restart the client.. (you can always move it back after)

also make sure you are running the wallet with the logo that matches the front page of this thread... if it has the old logo then you are using the old wallet and you should update it

FINALLY!!!
Your peers.dat did it!!!
I just copied it and deleted the conf and now it's syncing. I wonder what is happening with karma network because my other coins wallet working fine without config file.
Thank you very very very much.