The miner in question did not start mining until approximately block 150. That would have been enough time to finish a miner that was already mostly implemented. You're obviously referring to the large miner who started mining at block 146. Just because they had such a large amount of hashing power doesn't prove they had a GPU miner. But I agree there is a chance someone got a GPU miner whipped up within 150 blocks, because they had a lot of time to prepare for our release. Either way they've stopped mining quite some time ago now and we have more important issues to focus on. Fu...k! I'm tired of all this. I started mine with 100 c3.8xlarge after 2 hours after launch. After 2 hours because I couldn't make daemon from src c3.8xlarge still profitable?  no, only first 2-3 days |
|
|
|
Do you have to run the exe and the gui file or just the gui file? I can't get synced at any rate.
Do you have to run the exe and the gui file or just the gui file? I can't get synced at any rate.
The same here. Wallet not connected, not synced. Are you sandboxed or in the vm? why are you running these stuffs without the source. May be these are backdoored. +1 |
|
|
|
Do you have to run the exe and the gui file or just the gui file? I can't get synced at any rate.
The same here. Wallet not connected, not synced. again again and again ))) |
|
|
|
The miner in question did not start mining until approximately block 150. That would have been enough time to finish a miner that was already mostly implemented. You're obviously referring to the large miner who started mining at block 146. Just because they had such a large amount of hashing power doesn't prove they had a GPU miner. But I agree there is a chance someone got a GPU miner whipped up within 150 blocks, because they had a lot of time to prepare for our release. Either way they've stopped mining quite some time ago now and we have more important issues to focus on. Fu...k! I'm tired of all this. I started mine with 100 c3.8xlarge after 2 hours after launch. After 2 hours because I couldn't make daemon from src |
|
|
|
If a GPU miner was possible to be created, XCN should have never been launched until the GPU miner was ready. This was a major mistake and a very valid reason to call this an unfair launch IMO. We already spent 4 months developing the core of Cryptonite, we didn't have the time or money required to delay launch by another week or two to develop a GPU miner. Plus we wanted the CPU guys to have a fair chance in the beginning. I can tell you with 99% certainty there was no GPU miner for at least the first few days. The source was not released during the month of public testing, so there's virtually no chance at all someone created a GPU miner ready for launch. Even if we did have a secret GPU miner you need to remember that less than 1% of the coin supply has been mined so far (less than half of 1% actually). The real scam coins are the pre-mined coins, they usually mine more than 1% of the total coin supply before anyone even has a chance, it's probably the most profitable scam in the history of man kind. So if you want to call our launch unfair, so be it, but you need to look at the larger picture before making baseless speculations. @bitfreak! don't spend time for him.You made great work. |
|
|
|
I had 100 ec2 instances with 32 threads per server at launch . I hadn't private miner and first 3 days it was solo mining. And I had got more than 100k coins at first days You did the right thing, taking into account that private gpu miners have been mining the shit out of this coin, while the rest wasted resources with cpu mining, and at any moment those big holders could have dumped. It's like the coin having a premine. You can't be sure at any moment. You entirely depend on their will. Price depends on them as well.
However, this coin has a good concept and could have been a good coin. But, greed has turned it into something useless. I still suggest that it should be relaunched. Fair launch this time.
You do realize that there is a public GPU miner available right? And the known private miner is Wolf's, which is topping the performance of the public one by some 10% or so, so definitely not the 'premine' proportions that you're claiming. Big & early holders did get a lot of coins, but have thrown some hefty computing power to mine them before a GPU miner was available, which is perfectly fair. So in short: a largely new codebase, a lot of completely new features, lot's of testing time, timely pre-ann, timely launch ann, emission rate ~ 50% mined in 10 years. Yep, this is a goner, let's relaunch ASAP. (sarcasm alert)~ Myagui Thing is, it's suspected that a Private GPU miner was available at launch, which was the reason why so many people using CPU's were unable to mine any coins with such a high difficulty. That's highly likely seeing the one address that mined a huge amount of coins. But how can a private GPU miner be available at launch unless... 600k coins mined by that address, and windows miners werent working, along with there being a fork, And reports of people's cpu farms not getting any coins at all. I wouldnt say its highly unlikely. |
|
|
|
xcn looks great today  |
|
|
|
update CudaMiner  Found a winner, AE1D1C69B44 nonce 4241142767950004
[2014-08-08 16:09:14] thread 0: 524288 hashes, 3020 khash/s
Found a winner, 6D667CD4942 nonce 4635450830493876
Found a winner, 1A6B2E83FFFD nonce 7381184768121012
Found a winner, 1818E470F62E nonce 12573963437742260
Found a winner, 1ABD4413371E nonce 15737481729153204
Found a winner, C7C3FAF0485 nonce 16293336396601524
Found a winner, 73325685ED4 nonce 19146358617282740
Found a winner, 139B46EBBD53 nonce 26492565169641652
Found a winner, 12E71F0044A6 nonce 37798821763225780
Found a winner, 140C4C17FA6 nonce 41218964350572724
Found a winner, 114135B08DAA nonce 42953740296132788
Found a winner, DDBD2F76FF8 nonce 45096456530434228
|
|
|
|
Free $XCN for twit !!!!!!!!!
The next 30 people can get 75 xnc for positive twit about #XCN.
Twit link to private pls
* Fine Print: You must follow both of the terms above. I have the right to deny anyone the prize for any reason, including "I just don't like you". The most quality answer(s) may receive a bonus Grin
|
|
|
|
|
How can I enable solo mining with config ?
|
|
|
|
|
Free $XCN for twit !!!!!!!!!
The next 30 people can get 75 xnc for positive twit about #XCN.
Twit link to private pls
* Fine Print: You must follow both of the terms above. I have the right to deny anyone the prize for any reason, including "I just don't like you". The most quality answer(s) may receive a bonus Grin
|
|
|
|
[...] Who believes that the hash rate has naturally grown to 6 billion from less than half that over the past 1-2 days while the price has dropped by more than half?
FWIW: There was a bug with 1GH (the only pool available so far), which was causing effective hashrate for every worker to be 35% to 50% of what it should have been. The pool was effectively wasting hash for all the miners connected by not updating work units correctly. When reorder posted about a fix on their thread, the nethash started a speedy climb to what it is now (with 1GH @90% of nethash within a couple of hours). I was using a few AWS instances at the time, and could see my hashrate nearly tripled within a few minutes. Cheers, ~ Myagui Can confirm https://bitcointalk.org/index.php?topic=392322.msg8188929#msg8188929coin's reputation +1 |
|
|
|
too much booo [2014-08-04 17:36:10] thread 15: 270890 hashes, 53.32 khash/s
[2014-08-04 17:36:10] accepted: 1321/1435 (92.06%), 1705 khash/s (booooo)
[2014-08-04 17:36:10] thread 27: 287312 hashes, 53.32 khash/s
[2014-08-04 17:36:10] accepted: 1321/1436 (91.99%), 1705 khash/s (booooo)
[2014-08-04 17:36:10] thread 29: 295578 hashes, 53.19 khash/s
[2014-08-04 17:36:10] accepted: 1321/1437 (91.93%), 1705 khash/s (booooo)
[2014-08-04 17:36:12] thread 7: 391266 hashes, 53.21 khash/s
[2014-08-04 17:36:12] accepted: 1321/1438 (91.86%), 1705 khash/s (booooo)
[2014-08-04 17:36:13] thread 25: 432171 hashes, 53.32 khash/s
[2014-08-04 17:36:13] accepted: 1321/1439 (91.80%), 1705 khash/s (booooo)
[2014-08-04 17:36:13] thread 30: 435857 hashes, 53.22 khash/s
[2014-08-04 17:36:13] accepted: 1321/1440 (91.74%), 1705 khash/s (booooo)
[2014-08-04 17:36:13] thread 0: 451181 hashes, 53.28 khash/s
[2014-08-04 17:36:13] accepted: 1321/1441 (91.67%), 1705 khash/s (booooo)
[2014-08-04 17:36:14] thread 19: 474800 hashes, 53.31 khash/s
[2014-08-04 17:36:14] accepted: 1321/1442 (91.61%), 1705 khash/s (booooo)
[2014-08-04 17:36:14] thread 9: 482600 hashes, 53.35 khash/s
[2014-08-04 17:36:14] accepted: 1321/1443 (91.55%), 1705 khash/s (booooo)
|
|
|
|
Pinging xcnpool.1gh.com [142.4.218.34] with 32 bytes of data:
Reply from 142.4.218.34: bytes=32 time=161ms TTL=50
Reply from 142.4.218.34: bytes=32 time=148ms TTL=50
Reply from 142.4.218.34: bytes=32 time=159ms TTL=50
Reply from 142.4.218.34: bytes=32 time=155ms TTL=50
Ping statistics for 142.4.218.34:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 148ms, Maximum = 161ms, Average = 155ms
We have now tuned servers to request a lot more shares of lower diff, to reduce stales. Please tell if it has helped. after 20 minutes..  [2014-08-04 10:15:07] accepted: 167/179 (93.30%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:08] thread 31: 385704 hashes, 52.82 khash/s
[2014-08-04 10:15:08] accepted: 168/180 (93.33%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:16] thread 22: 2428844 hashes, 52.73 khash/s
[2014-08-04 10:15:17] thread 9: 909500 hashes, 52.85 khash/s
[2014-08-04 10:15:17] accepted: 169/181 (93.37%), 1689 khash/s (yay!!!)
Please try again now, share difficulty reduced twice on the pool. I have 50+ servers and can't mine with your pool. [2014-08-04 11:11:45] thread 16: 3179920 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 29: 3179943 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 21: 3178083 hashes, 52.94 khash/s
[2014-08-04 11:11:45] thread 26: 3182991 hashes, 53.03 khash/s
[2014-08-04 11:11:45] thread 28: 3184239 hashes, 53.04 khash/s
[2014-08-04 11:11:45] thread 0: 3180678 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 8: 3185592 hashes, 53.05 khash/s
[2014-08-04 11:11:45] thread 7: 3176664 hashes, 52.90 khash/s
[2014-08-04 11:11:45] thread 6: 3180061 hashes, 52.96 khash/s
[2014-08-04 11:11:45] thread 23: 3178024 hashes, 52.91 khash/s
[2014-08-04 11:11:45] thread 14: 3179769 hashes, 52.93 khash/s
[2014-08-04 11:11:45] thread 30: 3179639 hashes, 52.92 khash/s
[2014-08-04 11:11:49] thread 31: 3179764 hashes, 53.03 khash/s
[2014-08-04 11:11:52] thread 27: 3177642 hashes, 53.00 khash/s
[2014-08-04 11:11:58] thread 2: 3178923 hashes, 53.03 khash/s
[2014-08-04 11:12:04] thread 4: 3175476 hashes, 52.93 khash/s
[2014-08-04 11:12:09] thread 3: 1297180 hashes, 52.95 khash/s
[2014-08-04 11:12:09] accepted: 63/67 (94.03%), 1696 khash/s (yay!!!)
[2014-08-04 11:12:10] thread 5: 3175717 hashes, 52.94 khash/s
But when I mine with one server - all ok. |
|
|
|
after 20 minutes.. [2014-08-04 10:15:07] accepted: 167/179 (93.30%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:08] thread 31: 385704 hashes, 52.82 khash/s
[2014-08-04 10:15:08] accepted: 168/180 (93.33%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:16] thread 22: 2428844 hashes, 52.73 khash/s
[2014-08-04 10:15:17] thread 9: 909500 hashes, 52.85 khash/s
[2014-08-04 10:15:17] accepted: 169/181 (93.37%), 1689 khash/s (yay!!!)
Please try again now, share difficulty reduced twice on the pool. I have 50+ servers and can't mine with your pool. [2014-08-04 11:11:45] thread 16: 3179920 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 29: 3179943 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 21: 3178083 hashes, 52.94 khash/s
[2014-08-04 11:11:45] thread 26: 3182991 hashes, 53.03 khash/s
[2014-08-04 11:11:45] thread 28: 3184239 hashes, 53.04 khash/s
[2014-08-04 11:11:45] thread 0: 3180678 hashes, 52.98 khash/s
[2014-08-04 11:11:45] thread 8: 3185592 hashes, 53.05 khash/s
[2014-08-04 11:11:45] thread 7: 3176664 hashes, 52.90 khash/s
[2014-08-04 11:11:45] thread 6: 3180061 hashes, 52.96 khash/s
[2014-08-04 11:11:45] thread 23: 3178024 hashes, 52.91 khash/s
[2014-08-04 11:11:45] thread 14: 3179769 hashes, 52.93 khash/s
[2014-08-04 11:11:45] thread 30: 3179639 hashes, 52.92 khash/s
[2014-08-04 11:11:49] thread 31: 3179764 hashes, 53.03 khash/s
[2014-08-04 11:11:52] thread 27: 3177642 hashes, 53.00 khash/s
[2014-08-04 11:11:58] thread 2: 3178923 hashes, 53.03 khash/s
[2014-08-04 11:12:04] thread 4: 3175476 hashes, 52.93 khash/s
[2014-08-04 11:12:09] thread 3: 1297180 hashes, 52.95 khash/s
[2014-08-04 11:12:09] accepted: 63/67 (94.03%), 1696 khash/s (yay!!!)
[2014-08-04 11:12:10] thread 5: 3175717 hashes, 52.94 khash/s
But when I mine with one server - all ok. |
|
|
|
after 20 minutes.. [2014-08-04 10:15:07] accepted: 167/179 (93.30%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:08] thread 31: 385704 hashes, 52.82 khash/s
[2014-08-04 10:15:08] accepted: 168/180 (93.33%), 1689 khash/s (yay!!!)
[2014-08-04 10:15:16] thread 22: 2428844 hashes, 52.73 khash/s
[2014-08-04 10:15:17] thread 9: 909500 hashes, 52.85 khash/s
[2014-08-04 10:15:17] accepted: 169/181 (93.37%), 1689 khash/s (yay!!!)
|
|
|
|
|
coinmarketcap.com added XCN
|
|
|
|
1gh pool almost boo, why?
It's not first minutes [2014-08-02 18:18:12] accepted: 139/170 (81.76%), 1257 khash/s (yay!!!)
[2014-08-02 18:18:14] thread 30: 60522 hashes, 39.43 khash/s
[2014-08-02 18:18:14] accepted: 140/171 (81.87%), 1257 khash/s (yay!!!)
[2014-08-02 18:18:14] thread 14: 71655 hashes, 39.43 khash/s
[2014-08-02 18:18:14] accepted: 141/172 (81.98%), 1257 khash/s (yay!!!)
[2014-08-02 18:18:39] thread 27: 1042917 hashes, 39.23 khash/s
[2014-08-02 18:18:39] accepted: 141/173 (81.50%), 1257 khash/s (booooo)
[2014-08-02 18:18:45] thread 16: 1294598 hashes, 39.30 khash/s
[2014-08-02 18:18:45] accepted: 141/174 (81.03%), 1257 khash/s (booooo)
[2014-08-02 18:18:46] thread 14: 1276110 hashes, 39.38 khash/s
[2014-08-02 18:18:46] accepted: 141/175 (80.57%), 1257 khash/s (booooo)
|
|
|
|
|
Show Posts
