Official YACOIN Orphan Blocks Thread

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

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

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.

[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

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?

[MrWizard]

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

i can "beat" that:

Pinging 82.211.30.212 with 32 bytes of data:
Reply from 82.211.30.212: bytes=32 time=175ms TTL=46
Request timed out.
Reply from 82.211.30.212: bytes=32 time=173ms TTL=46
Request timed out.

Ping statistics for 82.211.30.212:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)
Approximate round trip times in milli-seconds:
    Minimum = 173ms, Maximum = 175ms, Average = 174ms

50% lost packets!!!

[tyrion70]

The Netherlands.. And I have a 100MBit fiber connection which might help a bit ;-)

[tyrion70]

i can "beat" that:

Pinging 82.211.30.212 with 32 bytes of data:
Reply from 82.211.30.212: bytes=32 time=175ms TTL=46
Request timed out.
Reply from 82.211.30.212: bytes=32 time=173ms TTL=46
Request timed out.

Ping statistics for 82.211.30.212:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss)
Approximate round trip times in milli-seconds:
    Minimum = 173ms, Maximum = 175ms, Average = 174ms

50% lost packets!!!

Ouch.. hope your found blocks weren't in those packets ;-)

[MuErTe]

3 orphans here

[ymer]

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  

[Sondey10mg]

6 orphans - 1 accepted
AMD phenom II x4 B55
6 hours
High speed internet - Belgium

Ping to 82.211.30.212 ~200ms  

[achillez]

25+ orphans, only 9 accepted

[tyrion70]

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?

[ymer]

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.

[ymer]

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.

[tyrion70]

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..

[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.

Third person with high success rate on linux.

So far no one with windows has reported high rate of good blocks.

I only had a problem after encrypting my wallet [1]. Oh, and I had to copy the peers
for the later setups since there was a connection problem. After this, I would say the coin
runs pretty flawless and the bad words about it are not justified.


[1] https://bitcointalk.org/index.php?topic=196196.msg2075564#msg2075564

[ymer]

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.

[DryPowder]

I have a cable 10M/s connection, 3 Xeon´s and 2 AMD FX-8, 6 hour mining and 89 orphans and not a single block.

[Sondey10mg]

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.

That's it. Downloading linux

[Goldmember]

18 valid, 67 orphans

Checked my ping, ~40 ms, but 19% packet loss...

[jdebunt]

just had a popup for a block, but it's another orphan...goddamnit

11 valid, 21 orphaned so far

[tyrion70]

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

Code:

netstat -tan -p tcp

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