I think the problem is low difficulty and shit location of the main node, leaves almost all of us with very high pings, the ones with good pings are getting most of the blocks.
Technically speaking there is no main node, but almost everyone connected him because of the startpost.. If I'm not mistaking a group of miners with low latency could theoretically be at an advantage. So if a few ppl with high hashpower and good latency happen to be close together no one else stands a chance.. Yea this + it seems that the windows module is not optimized or something, relm9 ( https://bitcointalk.org/index.php?topic=196196.msg2076277#msg2076277 ) reports very good results with 400KH/s and he's also on linux. I've had the same issue on Windows with BitBar and CNC.. I think in my case it has something to do with the fact that a lot of QT clients are running on my Windows desktop. They all have a number of connections open to the different coin networks. If I do a I get a shitload of open connections. Especially if you have uPNP enables this might hog your windows PC and maybe your internet router causing a lot of misery. May I suggest you reboot your PC, restart your internet router and see how your latency is then? Also, you might want to spend some time enabling CGminer for YaCoin.. If you are the first to do that, you might get rich ;-) It sucks I can't do any of that now because I'm at work, I'm only checking my home miners with logmein, I don't want to reboot my router or my miners because if somethig goes wrong my GPU mining will be gone until I'm back from work.
|
|
|
I have a cable 10M/s connection, 3 Xeon´s and 2 AMD FX-8, 6 hour mining and guess what … not a single block. This sucks. Let me guess, you are running the windows client from megaupload? nothing wrong with that client, i've found 11 blocks with it what's your orphan/success ratio and ping to 82.211.30.212 ? 11 valid, 21 orphans ping : 25% packetloss, 18,19,29 ms for valid packets That's a pretty low rate. Most Linux ones are getting at least 75% good ones
|
|
|
I have a cable 10M/s connection, 3 Xeon´s and 2 AMD FX-8, 6 hour mining and guess what … not a single block. This sucks. Let me guess, you are running the windows client from megaupload? nothing wrong with that client, i've found 11 blocks with it what's your orphan/success ratio and ping to 82.211.30.212 ?
|
|
|
I have a cable 10M/s connection, 3 Xeon´s and 2 AMD FX-8, 6 hour mining and guess what … not a single block. This sucks. Let me guess, you are running the windows client from megaupload?
|
|
|
I think the problem is low difficulty and shit location of the main node, leaves almost all of us with very high pings, the ones with good pings are getting most of the blocks.
Technically speaking there is no main node, but almost everyone connected him because of the startpost.. If I'm not mistaking a group of miners with low latency could theoretically be at an advantage. So if a few ppl with high hashpower and good latency happen to be close together no one else stands a chance.. Yea this + it seems that the windows module is not optimized or something, relm9 ( https://bitcointalk.org/index.php?topic=196196.msg2076277#msg2076277 ) reports very good results with 400KH/s and he's also on linux.
|
|
|
The Netherlands.. And I have a 100MBit fiber connection which might help a bit ;-)
Just checked again but from the 2nd location (I checked this one at work with a crap DSL connection) I checked from home with a fiber connection where the i5 3330 miner is and the ping is 1000ms That's even worse!! Lower is better with ping... That means it takes a second to reach that IP address!! Where are u from Ymer? I know, 1000ms = 1 second delay. I just shutdown the miners, it's not worth at all knowing that I will not get any blocks at this difficulty because it's so low my blocks get too late.
|
|
|
I think the problem is low difficulty and shit location of the main node, leaves almost all of us with very high pings, the ones with good pings are getting most of the blocks.
|
|
|
The Netherlands.. And I have a 100MBit fiber connection which might help a bit ;-)
Just checked again but from the 2nd location (I checked this one at work with a crap DSL connection) I checked from home with a fiber connection where the i5 3330 miner is and the ping is 1000ms
|
|
|
As my good friend Achmed used to say: Location Location Location (look it up it's funny :p) ping 82.211.30.212 PING 82.211.30.212 (82.211.30.212) 56(84) bytes of data. 64 bytes from 82.211.30.212: icmp_req=1 ttl=52 time=17.3 ms 64 bytes from 82.211.30.212: icmp_req=2 ttl=52 time=24.4 ms 64 bytes from 82.211.30.212: icmp_req=3 ttl=52 time=46.5 ms 64 bytes from 82.211.30.212: icmp_req=4 ttl=52 time=15.0 ms
Try this... if u see scores higher than that: Good luck mining.. If lower you still stand a chance ;-) This is what I get Respuesta desde 82.211.30.212: bytes=32 tiempo=229ms TTL=57 Respuesta desde 82.211.30.212: bytes=32 tiempo=222ms TTL=57 Respuesta desde 82.211.30.212: bytes=32 tiempo=223ms TTL=57 Respuesta desde 82.211.30.212: bytes=32 tiempo=220ms TTL=57
Ymer, than that is the issue.. When we both find a block you are 200ms slower in reporting it.. Because of the short timespan between the blocks it's a combination of network speed and hash speed that makes the difference. Hash speed makes u find blocks faster; network speed makes you report them to other nodes faster. Only thing that might help is finding nodes near you and add them with addnode option. Where are you located?
|
|
|
Getting blocks every minute or so here on 400kh/s
Are you running windows or linux?
|
|
|
Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz, 8 GB RAM
gethashespersec 212019
this one solved some blocks during the day. 2 orphans/16 blocks, client compiled on a linux client.
Third person with high success rate on linux. So far no one with windows has reported high rate of good blocks.
|
|
|
As my good friend Achmed used to say: Location Location Location (look it up it's funny :p) ping 82.211.30.212 PING 82.211.30.212 (82.211.30.212) 56(84) bytes of data. 64 bytes from 82.211.30.212: icmp_req=1 ttl=52 time=17.3 ms 64 bytes from 82.211.30.212: icmp_req=2 ttl=52 time=24.4 ms 64 bytes from 82.211.30.212: icmp_req=3 ttl=52 time=46.5 ms 64 bytes from 82.211.30.212: icmp_req=4 ttl=52 time=15.0 ms
Try this... if u see scores higher than that: Good luck mining.. If lower you still stand a chance ;-) This is what I get Respuesta desde 82.211.30.212: bytes=32 tiempo=229ms TTL=57 Respuesta desde 82.211.30.212: bytes=32 tiempo=222ms TTL=57 Respuesta desde 82.211.30.212: bytes=32 tiempo=223ms TTL=57 Respuesta desde 82.211.30.212: bytes=32 tiempo=220ms TTL=57
|
|
|
i5 2500k stock, 8GB RAM, client compiled on Linux. I think my overall ratio is like 10 accepted - 2 not accepted, which is fine. I restarted a couple times, old rejects aren't in the list anymore.
I think you and JimmyFL are the ones with the best ratios and both are running Linux. Is there a chance that there's a problem with the windows build?
|
|
|
If you guys all posted your hashrate I think you would see the answer staring you in the face.
O RLY? JimmyFL says he has 500KH/s Any mid-range CPU (i3) gets at least 100KH/s which is 1/5 of JimmyFL hashing power. I have 300KH/s in total and my result is 0% good blocks.
|
|
|
I don't get why people are helping the other people who can't get it working....This isn't pooled mining, more miners, means less blocks for me
It's not a good coin if it isn't fair, that's the whole point of the game.
|
|
|
Lol, obvious ScamCoin.
Why do you guys promote it so much?
I could just go out and release my own scamCoin and make a fortune.
Please post your information here Official YACoin Orphan Blocks ThreadPLEASE KEEP POSTING YOUR RESULTS. I want to have a lot more input before calling Shenannigans on this coin
|
|
|
PLEASE KEEP POSTING YOUR RESULTS.
I want to have a lot more input before calling Shenannigans on this coin
|
|
|
Debug window - listtransactions
Okay, now I'm really scared. It lists most of the Transactions as "orphan". Please tell me the client automatically omits the reward for orphan blocks when calculating the balance if you have the full valid chain already downloaded then yes it omits them. You can easily count the non orphan blocks, multiply by 60 and compare with your balance.
|
|
|
Update:
14 Orphans / 0 Valid Blocks
|
|
|
|