Good news people!
A new dev is going to work on the coin, ensure maintenance and add new features. It's not 100% official yet but should be confirmed in the coming hours/days. Also we will be working on a new promotional plan and potentially new services.
Edit: people who promised to give some coins (I think it was about 50 million), be prepared to keep your promises!
Is one of the items updating the wallet? I am still having issues where it will not stake. Also is there a master list of people who pledged? I can't remember if I did or not it's been so long. I guess that is what happens when you get old.
|
|
|
So any idea about how much coins per MN? Just a guesstimate.
|
|
|
Sorry for the noobie question, cannot solo mine this coin, getting 500 Internal Server error on tsiv nvidia miner... Any ideas? spreadcoin.conf used: rpcuser=jpouza rpcpassword=cash rpcallowip=127.0.0.1 rpcallowip=192.168.1.* rpcport=41677 port=41678 gen=0 server=1 Miner: spreadminer -o http://127.0.0.1:41677 -u jpouza -p cash Never solo mined before, my network internal IP range is 192.168.1.x, Wallet full syncronized and open... Fixed! The only way to unlock the wallet is mining with the CPU? Just pointed 1 core to the cpu mining and GPU miner is now allowed. Cheers I am not a Pro but try this. First if you using the same computer to solo mine with and you have the latest wallet you do not need a cinfig file. Everything is in the Wallet. You can not gpu mine if the wallet is locked. It must be unlocked. It can still be encrypted but it must be unlocked. In your config file you have 2 rpcallowip. I don't believe you need that second one. Delete it. Restart the wallet then unlock if encrypted let it resync and restart bat for miner. By the way what type of card are you using?
|
|
|
So a weird problem for me.
Mining and the message in the task bar just pooped up that I found a block. I see in the miner the block was found and accepted at 2015-01-08 01:01:30. When I look in the wallet it is no where to be found. Not in the unconfirmed or in the transaction tab. Last block in transaction tab is at 1/7/2015 15:05.
Any ideas? Mining on Windows 7 64bit with Nvidia cards.
|
|
|
But how to point 2nd PC? It seems running 2nd wallet is required? Even if coins will go to same address :/
the how-to steps are all in the readme.txt file,plz read it. It seems you either never read the readme, or misunderstand the question. May I run gpu miner on PC1 pointing it to wallet of PC2? the problem is that: By default, the wallet listens on 127.0.0.1 By default the gpu miner connects to 127.0.0.1
All readmes I found so far, explain how to mine on same PC which is running the wallet. Changing the address. No explanation how to connect gpu miner to other PCNever mind I found the answer : https://bitcointalk.org/index.php?topic=715435.msg9980210;topicseen#msg9980210At work and on my phone but yes you can run multiple rigs to one wallet. For example I sometimes run all 4 of my rigs to wallet on Rig #1. I did not post how to do it because the way I do it isn't considered the best and safest way but it works for me. Right now I am mining with Rig #1 and Rig #2 both mining into Rig #1. So yes you can mine from a computer at work and have it mine into your wallet at home. There are safer ways than the way I do it but I have never set it up any other way. And by safer I mean not leaving your ports open to the outside world. It's a risk that I run that I don't have to I just do it cut I am lazy to set it up the correct way. That is why I did not go into full detail in the other post.
|
|
|
I have no problem with the crowd funding.
Think about this. With out this the Neoscrypt is left to only AMD.
Sure there is the open cl AMD miner that works for Nvidia cards but it is not optimized at all and not worth using.
|
|
|
I sent some EAGS to lazycoins one hour ago but is not deposited into lazy account yet. What is the problem?
The exchange is Lazy. Sorry could not resist. Give it time it will show up.
|
|
|
Just doing a quick guestimate here so don't hold me to this as 100% accurate. But why would some one do that when they will make about 3 times that? That figure was just with your 200 Mh/s in the thread.
|
|
|
That really sucks. Everyone needs to start taking their local security very seriously. Please stop downloading clients from unreputable sources. Every client you download from someone that is not trusted is just asking for this to happen. There are a lot of smart people here and, unfortunately, some of them use their knowledge maliciously. These people can put anything they want into the client, knowing people will blindly download it. Please...I feel for your loss, but everyone has to be very careful and extremely diligent on securing your personal wealth. Don't rely on anything except your own judgement. This is not the first time a client has allowed access via TeamViewer, and unfortunately, I'm sure it won't be the last as long as people keep jumping the gun and downloading garbage I very highly suggest an immediate backing up of important data, reformat, and starting your OS from scratch, or this will continue to happen I know this might be bad to say (pool owners) but this is the main reason why I stopped trying to solo mine new coins (or wait a few days if no pools available) and use the pools to hold my coins until the wallet is been out for a few days or send the coins straight to an exchange to sell, especially if the coin only has a few days of POW. I understand the above was a little different as the wallet came from a secondary source.
|
|
|
Here are the top miners (at least 100 mined blocks) I have never figured this out but how do we get our main address to look up things like this?
|
|
|
So with Beta 3 and Beta 4 I would get my miner completely stopped after mining for a few hours and would have to restart it.
I finally looked at the log this time. I highlighted the message I think is causing it. Could I change the Expiry to fix the problem?
[2015-01-05 10:24:33] 74.0 C F: 80%(2972RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 72% P: 0% [2015-01-05 10:24:34] [thread 0: 196608 hashes, 179.7 khash/sec] [2015-01-05 10:24:35] [thread 0: 196608 hashes, 173.3 khash/sec] [2015-01-05 10:24:35] 74.0 C F: 80%(2962RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 71% P: 0% [2015-01-05 10:24:36] [thread 0: 196608 hashes, 180.2 khash/sec] [2015-01-05 10:24:37] [thread 0: 196608 hashes, 181.8 khash/sec] [2015-01-05 10:24:37] 74.0 C F: 80%(2957RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 71% P: 0% [2015-01-05 10:24:38] [thread 0: 196608 hashes, 176.4 khash/sec] [2015-01-05 10:24:39] [thread 0: 196608 hashes, 178.9 khash/sec] [2015-01-05 10:24:39] (5s):182.5K (avg):174.5Kh/s | A:30 R:0 HW:0 WU:0.8/m [2015-01-05 10:24:40] 75.0 C F: 80%(2962RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 71% P: 0% [2015-01-05 10:24:40] [thread 0: 212992 hashes, 191.8 khash/sec] [2015-01-05 10:24:41] [thread 0: 196608 hashes, 169.7 khash/sec] [2015-01-05 10:24:42] Work stale due to expiry [2015-01-05 10:24:42] Discarded work [2015-01-05 10:24:42] Work stale due to expiry [2015-01-05 10:24:42] Discarded 1 stales that didn't match current hash [2015-01-05 10:24:42] Popping work from get queue to get work [2015-01-05 10:24:42] Waiting for work to be available from pools. [2015-01-05 10:25:12] Pool 0 difficulty set to 1.000000
EDIT: Can't change --expiry and CGWatcher doesn't work with miner, or at least I could not get it going with it.
I don't think it is related to expiry. It is easy to test. Just copy the 'kshare320-546-uint2{GPUNAME}v1w256I4.bin' file compiled in Beta4 that has OpenCL optimization disabled to the folder with Beta2 and test this kernel with Beta2. 280X=147K? I have gotten as high as 230 kh/s. Could possibly be higher but I am also CPU mining.
|
|
|
So with Beta 3 and Beta 4 I would get my miner completely stopped after mining for a few hours and would have to restart it.
I finally looked at the log this time. I highlighted the message I think is causing it. Could I change the Expiry to fix the problem?
[2015-01-05 10:24:33] 74.0 C F: 80%(2972RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 72% P: 0% [2015-01-05 10:24:34] [thread 0: 196608 hashes, 179.7 khash/sec] [2015-01-05 10:24:35] [thread 0: 196608 hashes, 173.3 khash/sec] [2015-01-05 10:24:35] 74.0 C F: 80%(2962RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 71% P: 0% [2015-01-05 10:24:36] [thread 0: 196608 hashes, 180.2 khash/sec] [2015-01-05 10:24:37] [thread 0: 196608 hashes, 181.8 khash/sec] [2015-01-05 10:24:37] 74.0 C F: 80%(2957RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 71% P: 0% [2015-01-05 10:24:38] [thread 0: 196608 hashes, 176.4 khash/sec] [2015-01-05 10:24:39] [thread 0: 196608 hashes, 178.9 khash/sec] [2015-01-05 10:24:39] (5s):182.5K (avg):174.5Kh/s | A:30 R:0 HW:0 WU:0.8/m [2015-01-05 10:24:40] 75.0 C F: 80%(2962RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 71% P: 0% [2015-01-05 10:24:40] [thread 0: 212992 hashes, 191.8 khash/sec] [2015-01-05 10:24:41] [thread 0: 196608 hashes, 169.7 khash/sec] [2015-01-05 10:24:42] Work stale due to expiry [2015-01-05 10:24:42] Discarded work [2015-01-05 10:24:42] Work stale due to expiry [2015-01-05 10:24:42] Discarded 1 stales that didn't match current hash [2015-01-05 10:24:42] Popping work from get queue to get work [2015-01-05 10:24:42] Waiting for work to be available from pools. [2015-01-05 10:25:12] Pool 0 difficulty set to 1.000000
EDIT: Can't change --expiry and CGWatcher doesn't work with miner, or at least I could not get it going with it.
I don't think it is related to expiry. It is easy to test. Just copy the 'kshare320-546-uint2{GPUNAME}v1w256I4.bin' file compiled in Beta4 that has OpenCL optimization disabled to the folder with Beta2 and test this kernel with Beta2. Off to work but I moved the .bin file to the Beta 2 folder and it has been holding up fine for now. Will check it when I get back. Only issue of course is the loss of speed.
|
|
|
So with Beta 3 and Beta 4 I would get my miner completely stopped after mining for a few hours and would have to restart it.
I finally looked at the log this time. I highlighted the message I think is causing it. Could I change the Expiry to fix the problem?
[2015-01-05 10:24:33] 74.0 C F: 80%(2972RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 72% P: 0% [2015-01-05 10:24:34] [thread 0: 196608 hashes, 179.7 khash/sec] [2015-01-05 10:24:35] [thread 0: 196608 hashes, 173.3 khash/sec] [2015-01-05 10:24:35] 74.0 C F: 80%(2962RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 71% P: 0% [2015-01-05 10:24:36] [thread 0: 196608 hashes, 180.2 khash/sec] [2015-01-05 10:24:37] [thread 0: 196608 hashes, 181.8 khash/sec] [2015-01-05 10:24:37] 74.0 C F: 80%(2957RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 71% P: 0% [2015-01-05 10:24:38] [thread 0: 196608 hashes, 176.4 khash/sec] [2015-01-05 10:24:39] [thread 0: 196608 hashes, 178.9 khash/sec] [2015-01-05 10:24:39] (5s):182.5K (avg):174.5Kh/s | A:30 R:0 HW:0 WU:0.8/m [2015-01-05 10:24:40] 75.0 C F: 80%(2962RPM) E: 1100MHz M: 1500Mhz V: 1.200V A: 71% P: 0% [2015-01-05 10:24:40] [thread 0: 212992 hashes, 191.8 khash/sec] [2015-01-05 10:24:41] [thread 0: 196608 hashes, 169.7 khash/sec] [2015-01-05 10:24:42] Work stale due to expiry [2015-01-05 10:24:42] Discarded work [2015-01-05 10:24:42] Work stale due to expiry [2015-01-05 10:24:42] Discarded 1 stales that didn't match current hash [2015-01-05 10:24:42] Popping work from get queue to get work [2015-01-05 10:24:42] Waiting for work to be available from pools. [2015-01-05 10:25:12] Pool 0 difficulty set to 1.000000
EDIT: Can't change --expiry and CGWatcher doesn't work with miner, or at least I could not get it going with it.
|
|
|
Oh, the infamous libpdcurses.dll crash.
I usually get it on systems with more than 1 GPU or, when I use the --debug option. The same crash happens with sgminer, BTW.
If you still get this crash without the --debug option then, try the --real-quiet option. The screen isn't going to look as nice as the curses version but, you won't get the crash anymore.
Yep. Removing the --debug log fixed it. Thanks.
|
|
|
nVidia doesn't support ADL
Is this a new feature in Beta 4? I updated existing ADL code using what I found in the latest sgminer. Are you saying temp monitoring worked on your nVidia cards in Beta3? No, temo monitor did nor work, but the miner worked. It ran. It does nothing at all now. http://s7.postimg.org/8yhymn59n/New_2.png
|
|
|
nVidia doesn't support ADL
Is this a new feature in Beta 4?
|
|
|
Anyone else having issue in Beta 4 where no stats show in the bottom part of the cgminer screen? The "rolling" part of the miner.
EDIT: Also I can't get it to run on Nvidia cards now. It just pops a message "cgminer has stopped working".
[2015-01-04 22:30:22] Started cgminer 3.7.6 [2015-01-04 22:30:22] CL Platform 0 vendor: NVIDIA Corporation [2015-01-04 22:30:22] CL Platform 0 name: NVIDIA CUDA [2015-01-04 22:30:22] CL Platform 0 version: OpenCL 1.1 CUDA 6.5.30 [2015-01-04 22:30:22] Platform 0 devices: 4 [2015-01-04 22:30:22] 0 GeForce GTX 970 [2015-01-04 22:30:22] 1 GeForce GTX 750 Ti [2015-01-04 22:30:22] 2 GeForce GTX 750 Ti [2015-01-04 22:30:22] 3 GeForce GTX 750 Ti [2015-01-04 22:30:22] Number of ADL devices: 4 [2015-01-04 22:30:22] Unable to load ATI ADL library. [2015-01-04 22:30:22] Probing for an alive pool [2015-01-04 22:30:22] Popping work to stage thread
WORE, I just caught that also. It works fine on the Beta 3 version.
|
|
|
Anyone else having issue in Beta 4 where no stats show in the bottom part of the cgminer screen? The "rolling" part of the miner.
Got a screenshot? Sorry don't know how to post pics. http://s27.postimg.org/qpbh3lqs3/New.pngDo menus show up? Press G for example. Yes pressing G has the menus.
|
|
|
Anyone else having issue in Beta 4 where no stats show in the bottom part of the cgminer screen? The "rolling" part of the miner.
Got a screenshot? Sorry don't know how to post pics. http://s27.postimg.org/qpbh3lqs3/New.png
|
|
|
Anyone else having issue in Beta 4 where no stats show in the bottom part of the cgminer screen? The "rolling" part of the miner.
EDIT: Also I can't get it to run on Nvidia cards now. It just pops a message "cgminer has stopped working".
[2015-01-04 22:30:22] Started cgminer 3.7.6 [2015-01-04 22:30:22] CL Platform 0 vendor: NVIDIA Corporation [2015-01-04 22:30:22] CL Platform 0 name: NVIDIA CUDA [2015-01-04 22:30:22] CL Platform 0 version: OpenCL 1.1 CUDA 6.5.30 [2015-01-04 22:30:22] Platform 0 devices: 4 [2015-01-04 22:30:22] 0 GeForce GTX 970 [2015-01-04 22:30:22] 1 GeForce GTX 750 Ti [2015-01-04 22:30:22] 2 GeForce GTX 750 Ti [2015-01-04 22:30:22] 3 GeForce GTX 750 Ti [2015-01-04 22:30:22] Number of ADL devices: 4 [2015-01-04 22:30:22] Unable to load ATI ADL library. [2015-01-04 22:30:22] Probing for an alive pool [2015-01-04 22:30:22] Popping work to stage thread
|
|
|
|