Show Posts
|
Pages: « 1 2 3 4 5 [6]
|
^^^ again thats not evidence.
You don't know what coins or processor is doing that mining. Not saying its not true just that that's not real evidence.
Ok. What are you can accept as evidence? Other words, what you want to see? A screen shot of simpleminer if its an optimized version would suffice next to screenshot of the system screen showing the CPU. If its a complete separate miner a screen shot of that miner including the command used to start it which should show an MRO address. Failing that, the source code will do Sorry, very big... One i5 and One e5 connected to local pool:
|
|
|
^^^ again thats not evidence.
You don't know what coins or processor is doing that mining. Not saying its not true just that that's not real evidence.
Ok. What are you can accept as evidence? Other words, what you want to see? Source code would be good (and useful!). Alternately, I guess, you could have a trusted person test it. Heh ) How are you think, how high difficulty will grow up after? BTW my source additions are too ugly to show others - I'm not a pro ) But it works )
|
|
|
^^^ again thats not evidence.
You don't know what coins or processor is doing that mining. Not saying its not true just that that's not real evidence.
Ok. What are you can accept as evidence? Other words, what you want to see?
|
|
|
Evidence?
I posted it earlier: Yes, I remember that. Some person on the Internet saying that some other unnamed person said he did something hardly constitutes evidence. I'm not even doubting that optimized asm code could make a big difference. Just not sure how to know whether this is real or not. Rumors and FUD are rampant, so it is just hard to tell. You don't see a lot of evidence for it in the hash rate. Currently a 20 H/sec computer mines about 2 coins a day, worth about $1, and uses very roughly 30c of electricity (15c/kwh rate). So it is still quite profitable to mine this coin using a regular computer and the standard miner. It does require extreme patience though, with no pools available yet. Yes, I can't prove that, I didn't see any proofs. But I don't think that he lied us. There is no reasons. i5 [2014-05-16 13:54:57] accepted: 48/48 (100.00%), 137.72 hashes/s (yay!!!) [2014-05-16 13:54:57] thread 2: 7 hashes, 21.35 hashes/s [2014-05-16 13:54:58] accepted: 49/49 (100.00%), 121.27 hashes/s (yay!!!) [2014-05-16 13:54:58] thread 2: 7 hashes, 21.49 hashes/s [2014-05-16 13:54:58] thread 0: 40 hashes, 26.60 hashes/s [2014-05-16 13:54:59] thread 1: 88 hashes, 30.90 hashes/s [2014-05-16 13:54:59] accepted: 50/50 (100.00%), 110.51 hashes/s (yay!!!) [2014-05-16 13:54:59] thread 2: 7 hashes, 36.26 hashes/s [2014-05-16 13:55:00] accepted: 51/51 (100.00%), 125.27 hashes/s (yay!!!) [2014-05-16 13:55:00] accepted: 52/52 (100.00%), 125.27 hashes/s (yay!!!) [2014-05-16 13:55:01] accepted: 53/53 (100.00%), 125.27 hashes/s (yay!!!) [2014-05-16 13:55:01] thread 2: 7 hashes, 21.45 hashes/s [2014-05-16 13:55:01] accepted: 54/54 (100.00%), 110.46 hashes/s (yay!!!) [2014-05-16 13:55:02] thread 3: 159 hashes, 32.07 hashes/s [2014-05-16 13:55:02] thread 0: 40 hashes, 30.40 hashes/s [2014-05-16 13:55:02] thread 2: 7 hashes, 24.43 hashes/s [2014-05-16 13:55:02] accepted: 55/55 (100.00%), 117.80 hashes/s (yay!!!) [2014-05-16 13:55:03] accepted: 56/56 (100.00%), 117.80 hashes/s (yay!!!) [2014-05-16 13:55:03] thread 2: 7 hashes, 21.39 hashes/s [2014-05-16 13:55:04] thread 0: 40 hashes, 27.27 hashes/s [2014-05-16 13:55:04] thread 1: 88 hashes, 28.45 hashes/s [2014-05-16 13:55:04] accepted: 57/57 (100.00%), 109.18 hashes/s (yay!!!) [2014-05-16 13:55:05] accepted: 58/58 (100.00%), 109.18 hashes/s (yay!!!) [2014-05-16 13:55:05] thread 2: 43 hashes, 37.23 hashes/s [2014-05-16 13:55:05] accepted: 59/59 (100.00%), 125.02 hashes/s (yay!!!) [2014-05-16 13:55:06] accepted: 60/60 (100.00%), 125.02 hashes/s (yay!!!) [2014-05-16 13:55:06] thread 3: 162 hashes, 33.04 hashes/s [2014-05-16 13:55:08] thread 3: 23 hashes, 21.37 hashes/s [2014-05-16 13:55:08] thread 2: 43 hashes, 23.45 hashes/s [2014-05-16 13:55:08] accepted: 61/61 (100.00%), 100.53 hashes/s (yay!!!) [2014-05-16 13:55:09] accepted: 62/62 (100.00%), 100.53 hashes/s (yay!!!) [2014-05-16 13:55:09] thread 3: 23 hashes, 27.27 hashes/s [2014-05-16 13:55:10] accepted: 63/63 (100.00%), 106.44 hashes/s (yay!!!) e5 [2014-05-16 13:55:40] thread 9: 11 hashes, 14.14 hashes/s [2014-05-16 13:55:41] accepted: 83/83 (100.00%), 196.97 hashes/s (yay!!!) [2014-05-16 13:55:41] accepted: 84/84 (100.00%), 196.97 hashes/s (yay!!!) [2014-05-16 13:55:41] thread 4: 13 hashes, 15.87 hashes/s [2014-05-16 13:55:42] accepted: 85/85 (100.00%), 200.53 hashes/s (yay!!!) [2014-05-16 13:55:42] thread 8: 66 hashes, 14.64 hashes/s [2014-05-16 13:55:43] thread 10: 86 hashes, 17.07 hashes/s [2014-05-16 13:55:43] thread 11: 91 hashes, 17.54 hashes/s [2014-05-16 13:55:43] accepted: 86/86 (100.00%), 198.35 hashes/s (yay!!!) [2014-05-16 13:55:43] thread 3: 93 hashes, 17.88 hashes/s [2014-05-16 13:55:43] thread 2: 81 hashes, 15.38 hashes/s [2014-05-16 13:55:43] thread 7: 89 hashes, 16.61 hashes/s [2014-05-16 13:55:43] thread 0: 85 hashes, 15.82 hashes/s [2014-05-16 13:55:43] accepted: 87/87 (100.00%), 195.78 hashes/s (yay!!!) [2014-05-16 13:55:43] thread 0: 2 hashes, 13.63 hashes/s [2014-05-16 13:55:43] thread 6: 89 hashes, 15.28 hashes/s [2014-05-16 13:55:44] accepted: 88/88 (100.00%), 191.45 hashes/s (yay!!!) [2014-05-16 13:55:44] thread 0: 2 hashes, 13.00 hashes/s [2014-05-16 13:55:44] thread 1: 35 hashes, 16.89 hashes/s [2014-05-16 13:55:45] accepted: 89/89 (100.00%), 189.38 hashes/s (yay!!!) [2014-05-16 13:55:45] thread 0: 2 hashes, 12.28 hashes/s [2014-05-16 13:55:45] thread 3: 22 hashes, 12.19 hashes/s [2014-05-16 13:55:45] accepted: 90/90 (100.00%), 182.96 hashes/s (yay!!!) [2014-05-16 13:55:46] accepted: 91/91 (100.00%), 182.96 hashes/s (yay!!!) [2014-05-16 13:55:47] accepted: 92/92 (100.00%), 182.96 hashes/s (yay!!!) [2014-05-16 13:55:47] thread 0: 2 hashes, 12.71 hashes/s [2014-05-16 13:55:48] thread 11: 64 hashes, 14.06 hashes/s [2014-05-16 13:55:48] thread 5: 77 hashes, 15.58 hashes/s [2014-05-16 13:55:48] accepted: 93/93 (100.00%), 180.41 hashes/s (yay!!!) [2014-05-16 13:55:48] thread 0: 2 hashes, 10.20 hashes/s
|
|
|
When a block is found, no one will be paid.
I'll point my miners there. The result of not getting paid is about what happens when I solo mine too looks like pool is working in testnet )
|
|
|
how many coins did guys mine so far?
3942001.45259522 I mined 12305000, haha what a joke maybe he is true, i wonder that who mined first 450 blocks in 15 minutes by solo mining at launch of coin... 4 million too high but 1 million is possible... that's total money supply ) now is 4012502.36651674
|
|
|
WTS 500 DNotes = 0.05 BTC. or 500 DNotes = 2 LTC.
PM me.
|
|
|
WTS 500 DNotes = 0.05 BTC. or 500 DNotes = 2 LTC.
PM me.
|
|
|
Last 24 hour average block size for pools: From 8 pm 2/16/14 to 8 pm 2/17/14 (PST timezone) karma.hashstrike.com = 247 blocks/448009.8825910931 avg http://pool.karmacoin.info = 237 blocks/456402.3839662447 avg http://karm.idcray.com = 103 blocks/717014.3203883495 avg For a total average of 587 blocks/498600.1379897785 avg That is where the hell my claim comes from. I don't want to argue but please research first. This is way out of the range of luck isn't it? The attacker is getting massive block sizes somehow compared to the pools. Hmm... Don't understand... What a coin is mined by karm.idcray.com? One miner with 1Mhs Last Hour 34 Avg. Diff 0.0273 Amount 27659463 Seems looks like a fake...
|
|
|
I've a question. Look's like a large private pool is connected to network... At this time is 1400Mhs network hashrate. pool.karmacoin.info - 387Mhs karma.hashstrike.com - 296Mhs other officially announced at start page ~ 10-20Mhs Black hole: ~700Mhs Next. Block 17840-17845 generated by K7SBPBYDkEPpDqpARgE9xBes7f1FZ6w68Z with total amount of 4869397,001 KARMAs. 811566,1668 average per block. Higher than other pools... Ok... Some investigations in block explorer... http://explorer.karmacoin.info/tx/d02563e283e1b438b9d02c19bddcad584fd661384b8346bea625f41df3f936feK7SBPBYDkEPpDqpARgE9xBes7f1FZ6w68Z sent appx 27517929.016 to KUMpz7KSH2ym3XVDFws3YhqapcA26JdQW5 Ok... Sent, sent and sent... And voila: Address KUMpz7KSH2ym3XVDFws3YhqapcA26JdQW5 Details Balance 2589363996.56565243 KAR Transactions in 742 Received 6955117377.22357766 KAR Transactions out 336 Sent 4365753380.65792523 KAR
omg... 2.6 billion... 77btc at 3e-8... And yes, only K7SBPBYDkEPpDqpARgE9xBes7f1FZ6w68Z sent to KUMpz7KSH2ym3XVDFws3YhqapcA26JdQW5. May be I'm wrong, but... And now my question: is it possible 51% attack at KARMA network?add/ From block 18100 to 18143 all blocks with reward > 1mio except one was generated by K7SBPBYDkEPpDqpARgE9xBes7f1FZ6w68Z, and smallest reward was appx 0.65mio. So lucky )))
|
|
|
Refunded all my UTC, NYAN and almost LTC. As promised. Thank you.
|
|
|
|