after removing
addnode=71.105.130.10
from my config and deleting the blockchain i got transactions again
what's the meaning of this?
Topic: âš’[CGA] Cryptographic Anomaly - The Elusive Coinâš’ - page 138. (Read 226291 times)
Thanks, the "-p x" command worked... 
i mined all night yesterday on cryptochomper, will i get my coin when it come back online tomorow?
Just got my payout from Crypto Chompers, FYI for those that still have coins there.
Hi everyone , it seems things are moving right along over the past couple of days. I've been away working and left my miners pointing at Cryptochomper and Poolnetwork as fallover.....needless to say the miner has been chugging away but to no avail...Hopefully we can get theese pools sorted out. I tried to connect to the P2P pool today but it wouldnt connect with cgminer. It seems to have a problem with the lack of a Password. Do you, if I take the -p out of the command line it rejects the connection and if I leave it in but blank it shuts down with an "unexpected command" or something. How do I configure the .bat to connect to the pool? I also tried to do a little Solo mining but the wallet won't start in server mode, it tells me I need to add a rpc password in the .conf file whish is already there...it won't see it for some reason. Any suggestions?
My cgminer command line looks like this:
cgminer --scrypt -o stratum+tcp://anomalypool.com:2124 -u
Change the bits between
That seems to work fine. Hope it helps.
yeah just put the -p in there with any old password
I just set up another node on a dedicated server in the US to help stabilize the network and spread the load. The IP is: 184.154.116.146
Thanks, added to my nodes.Sawedoff: Update time is fine with me, will update all nodes. Is there anything we should keep in mind, some "main node" which shuts down last and starts first or something?
I would recommend that all pool and node owners direct connect to 71.105.130.10 during the update in order to reduce risk of forking. Once everything looks like it is in order you can go back to your normal configs. 71.105.130.10 will be the first node to be updated.
Hi everyone , it seems things are moving right along over the past couple of days. I've been away working and left my miners pointing at Cryptochomper and Poolnetwork as fallover.....needless to say the miner has been chugging away but to no avail...Hopefully we can get theese pools sorted out. I tried to connect to the P2P pool today but it wouldnt connect with cgminer. It seems to have a problem with the lack of a Password. Do you, if I take the -p out of the command line it rejects the connection and if I leave it in but blank it shuts down with an "unexpected command" or something. How do I configure the .bat to connect to the pool? I also tried to do a little Solo mining but the wallet won't start in server mode, it tells me I need to add a rpc password in the .conf file whish is already there...it won't see it for some reason. Any suggestions?
My cgminer command line looks like this:
cgminer --scrypt -o stratum+tcp://anomalypool.com:2124 -u
Change the bits between
That seems to work fine. Hope it helps.
Hi everyone , it seems things are moving right along over the past couple of days. I've been away working and left my miners pointing at Cryptochomper and Poolnetwork as fallover.....needless to say the miner has been chugging away but to no avail...Hopefully we can get theese pools sorted out. I tried to connect to the P2P pool today but it wouldnt connect with cgminer. It seems to have a problem with the lack of a Password. Do you, if I take the -p out of the command line it rejects the connection and if I leave it in but blank it shuts down with an "unexpected command" or something. How do I configure the .bat to connect to the pool? I also tried to do a little Solo mining but the wallet won't start in server mode, it tells me I need to add a rpc password in the .conf file whish is already there...it won't see it for some reason. Any suggestions?
For ordinary users, is there anything to the update, except a new wallet to install?
There shouldn't be anything else you need to do but I recommend re-syncing your blockchain after you update to clean up the network.
For ordinary users, is there anything to the update, except a new wallet to install?
I just set up another node on a dedicated server in the US to help stabilize the network and spread the load. The IP is: 184.154.116.146
Thanks, added to my nodes.Sawedoff: Update time is fine with me, will update all nodes. Is there anything we should keep in mind, some "main node" which shuts down last and starts first or something?
I just set up another node on a dedicated server in the US to help stabilize the network and spread the load. The IP is: 184.154.116.146
You can add this to your configuration file like any other node, or open the debug console and type in:
addnode 184.154.116.146 add
The max connections right now is 125, but I could easily raise that as long as it doesn't kill my CPU or RAM.
You can add this to your configuration file like any other node, or open the debug console and type in:
addnode 184.154.116.146 add
The max connections right now is 125, but I could easily raise that as long as it doesn't kill my CPU or RAM.
I am thinking of doing the update at noon PST (8pm GMT) Feb 6th. I tried to coordinate the time with pool owners but PoolNetwork and CryptoChomper have been hard to get in touch with. So I'm just going to go with it and hope they get the word.
SOooo....
SOooo....
MANDATORY UPDATE TO VERSION 0.1.1.2 ON FEB 6th 8PM GMT!
There are 5790+ blocks in my wallet, what consequences will I get? How to fix it? What node has the right chain?
You seem to be on the right one
There are 5790+ blocks in my wallet, what consequences will I get? How to fix it? What node has the right chain?
I believe you are right but I realized this morning that my wallet was on the wrong chain and I think most of everyone else was connecting to me. I am now on block 5783 and moving, I will be hard coding the seed nodes in the update in hope to keep this from happening again.
Sounds great!I checked the first node, but I didn't get a connection to it. Wallet's debug.log wrote "connection timeout", therefore I thought the node was down. If you can write the nodes directly into the client, this would be awesome.
I am thinking of doing the update at noon PST (8pm GMT) Feb 6th. I tried to coordinate the time with pool owners but PoolNetwork and CryptoChomper have been hard to get in touch with. So I'm just going to go with it and hope they get the word.
SOooo....
SOooo....
MANDATORY UPDATE TO VERSION 0.1.1.2 ON FEB 6th 8PM GMT!
Giveway coming soon! I received a donation of 25 CGA for giveaways but I want to wait until the update is complete.
Logo contest is some what funded and currently has 11+ CGA in the pot, but no submissions yet.
I'm hoping that the new update will fix some of the problems we are having, I also believe that an exchange is waiting for the update before they list CGA. So my main focus is the update.
Good news and now waiting for the update.
Giveway coming soon! I received a donation of 25 CGA for giveaways but I want to wait until the update is complete.
Logo contest is some what funded and currently has 11+ CGA in the pot, but no submissions yet.
I'm hoping that the new update will fix some of the problems we are having, I also believe that an exchange is waiting for the update before they list CGA. So my main focus is the update.
I don't belive that an update fixes the problem that we have too less stable nodes. Logo contest is some what funded and currently has 11+ CGA in the pot, but no submissions yet.
I'm hoping that the new update will fix some of the problems we are having, I also believe that an exchange is waiting for the update before they list CGA. So my main focus is the update.
yea update would be good, 3 of the 4 pool are not working
I think 2 of 4 are working? I think this is not the fault of the client software but was an issue with the CGA network (unstable due to weak/insufficient nodes).Please correct me if I'm wrong.
yea update would be good, 3 of the 4 pool are not working
Jump to: