Is the pool paying out right? For 500,000-coin blocks, shouldn't I have more than 50K in my account?
being looked at as we speak I can confirm this is an issue on my account as well, seems my balance is off by 3 decimal places. |
|
|
|
I noticed when scantime was 1 the threads/khash updated fast. When I had it set to 99 it updated MUCH slower, but I got more of the following with -H:
[2013-08-17 20:03:10] DEBUG: hash > target (false positive)
Hash: 000000c097ceb4fc80c0f2b4f5df5e5e5485e27f7ba0e128fe32db6c9c9ef33c
Target: 00000001d5780000000000000000000000000000000000000000000000000000
Any ideas?
Pretty sure those are orphans. Also, sent you a 5555 qrk for your advice in the other thread. Thanks again. |
|
|
|
Thanks, I got it to work. I didn't see the README. How do you know when you've found a block?
accepted: 1/1 (100.00%), 896.91 khash/s (yay!!!) I have compiled in Linux and used the precompiled windows versions here, and they are abysmally slow for me. On a single core, the wallet gives me 120Kh/s. The cpuminer version gives me about 6Kh/s. I've tried the AVX and AVX2 versions on both Ivy-Bridge and Haswell Xeons to no avail. Using no options on the command line, and --benchmark gives me the same slow h/s. Any ideas? Make sure you have -a quark added to the line that runs minerd. I knew I was missing something simple, what's your qrk address, let me hook you up with some coins! |
|
|
|
Thanks, I got it to work. I didn't see the README. How do you know when you've found a block?
accepted: 1/1 (100.00%), 896.91 khash/s (yay!!!) I have compiled in Linux and used the precompiled windows versions here, and they are abysmally slow for me. On a single core, the wallet gives me 120Kh/s. The cpuminer version gives me about 6Kh/s. I've tried the AVX and AVX2 versions on both Ivy-Bridge and Haswell Xeons to no avail. Using no options on the command line, and --benchmark gives me the same slow h/s. Any ideas? |
|
|
|
Honestly, once these hit an exchange and we get some liquidity, the price is going to be solid in my opinion. They are a pain in the ass to mine  |
|
|
|
|
Anyone having success getting this to work well with the new N change? If so, please post your config and speeds.
Thanks
|
|
|
|
can someone please post the GPU source code link?
Hit up ig0tik3d, it's his build, I wish he'd post source as well. |
|
|
|
And out come the premines on the not premined coin.
1000 Premine is nothing, especially compared to almost every alt. In the first week there are over 50k mined, so the creator has 2% of current circulation, big deal! |
|
|
|
This is the release I've been waiting for. I can now run all of my 10 core Ivy Bridge Xeons with genproclimit set to -1 and no crashes! (and it appears better performance too!) |
|
|
|
|
Extremely low invalids (<.5%), need more miners here! I've doubled my pennies rate from my solo mining.
|
|
|
|
However it doesn't start at all on my low-end PC, so I'm not going to post it in the main thread yet until I've got that sorted out. Shouldn't be an issue on medium to high end systems though. If it is, please post details about your system.
I can't comment on stability yet since I just installed it on all 3 machines. I have had crashes (many, many times) on all machines before, so I hope I can bring some good news later. I can comment on stability now: still not very stable  All 3 my machines went down at block 2060 so it looks as if there are still some problems with grant-block processing. As I mentioned before, once the problem is solved that you can load the blockchain while mining, this will prove the client is stable enough to run without crashing. I have been stable for days, the trick for me was to specify using only the amount of real CPU cores you have with genproclimit=# in your memorycoin.conf file. I have 5 machines running 24x7 now with no issues. |
|
|
|
Go scan a clean bitcoin binary and see how it comes back They're too damn lazy to actually pick up the malicious code and somehow always just find anything to do with mining code is a virus..... |
|
|
|
Bummer, this no longer runs on Wine just FYI. Crashes saying it doesn't like the new .dlls. |
|
|
|
|
Using it now, .5% invalids, nice work!
|
|
|
|
new pool launched: and here are the rules: 1. you setup your miners and point them to the pool 2. pool fee is 1% 3. auto payout threshold is set between 10 and 50 pennies and you will get php floor function of your balance e.g. if you earned 10.1 and your threshold is set to 10 you will receive 10 and 0.1 is going to the pool wallet - don't ask to change it 4. same rules for manual payouts - if you have 1.99 penny on your account and you will decide to cash out you will receive 1 and 0.99 goes to pool wallet feeleep Well done, now we're cooking with oil! Feeleep, you should make a new thread for this so it gets noticed though imo. |
|
|
|
It only works for me if I specify genproclimit=<real number of cores>. If I specify -1 trying to use Hyperthreading, it crashes.
Thanks - and what range of numbers can you specify? Is it only the exact number of cores that works? I have 4 core Ivy bridge, 8 core Sandy bridge Xeon, and 10 core Ivy Bridge. Anything over 4 cores and I have to specify or it crashes. |
|
|
|
|
It only works for me if I specify genproclimit=<real number of cores>. If I specify -1 trying to use Hyperthreading, it crashes.
|
|
|
|
|
For comparison's sake, using the GPU miner earlier in this thread, at this difficulty on 6 x 7950's (about 11Mh/s) I am getting about 12 pennies an hour on average. I believe a single 4core sandy bridge is getting about 125Kh/s IIRC.
|
|
|
|
Transactions could be a minimum of X pennies.
Say 100 pennies, with a 1% fee = 1 penny. It's a start anyway.
This is what I believe the launch on an exchange to be like, agreed. |
|
|
|
|
Show Posts
