Official YACOIN Orphan Blocks Thread

[eddyfitz]

13 orphans / 3 success

[bitdwarf]

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.

[JimmyFL]

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.

When did you start mining?

[Goldmember]

18 valid, 67 orphans

[Neverest]

I7 2600k, about 100k/s for over 6 hours. Zero valids, 10 Orphans.
I am out, waste of my CPU.

[ymer]

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?

[Rave]

Still 0 with about 480 k/s....hmmmm....

[mr_random]

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 can tell you hashrate is at least part of it because I've been using every computer in the house to mine it. For me the pattern has been the machines with high hashrate have gotten virtually no orphans, the machines with low hashrate all orphans. That's my experience.

[JimmyFL]

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?

I don't think so. We are the only one with a pretty good ratio AND posting on the forum. I'm sure there are many miners that don't bother to argue here...

[Wolf Rainer]

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.

When did you start mining?

I have 300kh/s too and i started mining only 1 hour later... And you show pictures about you taking 2 blocks in less than minute and that picture was 4 hours ago.

In 9 hours of mining with 300 khs i get 000000000000 yacoin.

[robotrebellion]

0 orphans (unless you count blocks generated while downloading the blockchain, then it's 2)
1 confirmed block

[megablue]

30 orphans 0 success.

[aikklond]

I have 1 top tier intel and one top tier amd i am getting about 20%-30% success which is good (i think)


BUT on a 2core-4 threaded mobile cpu, i got 4 out of 5 !!!!! 80%!

so I guess luck is a HUGE factor!

[JimmyFL]

for example, no block (or orphan) for me since 1hour

[tyrion70]

As my good friend Achmed used to say:

Location Location Location (look it up it's funny :p)

Code:

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 ;-)

[tyrion70]

O and Ymer, Linux definately has something to do with it..

DL-ing blockchain on Linux was 5 minutes work, on windows it went for 2 hours.. My two windows laptops have only orphanes and stales, my Linux machine has a lot of blocks

[ymer]

As my good friend Achmed used to say:

Location Location Location (look it up it's funny :p)

Code:

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

Code:

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

[clu]

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.

[ymer]

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.

[#R#a#u#t#e#]

18 accepted out of 48 in 9 hours with phenom 965 (special edition with 4 broken pins i resoldered lol)
2 out of 19 with i7...
and 1 notebook wich decided to surrender