Orphan blocks at mining pools

[enginera]

Hi,

I'm using some well-known mining pools with Scrpyt alg.  With rented rigs.
I see many orphan blocks.

For example; the total hash of the pool is 500 mh/s. And difficulty is low -like 0.0644 for Fastcoin.
I've joined with a hashspeed of 350 mh/s into that pool.
Is my high speed a reason for getting so much Orphans? What should I do?

Look at the linked screenshot please.
http://imgur.com/wbgpqKp

https://i.imgur.com/wbgpqKp.jpg

Thanks.

[tuaris]

Coins with short block times (less than a few minutes) and low difficulties will always generate lots of 'orphans' (stale blocks) before you factor in latency issues.  There is a lot that needs to be done in a short time with these very fast coins:

• Pool receives work from Coin network
• Pool sends work to miner
• Miner sends work to hardware
• Hardware find solution
• Hardware reports back to miner
• Miner verifies solution
• Miner reports back to pool
• Pool checks solution
• Pool submits solution to coin daemon
• Coin daemon checks solution
• Coin daemon submits to coin network
• Propagation

Between all that you have even more low level logic that adds additional time (TCP/IP handshake, disk access, string parsing, etc..).  It's amazing how much happens in a short period of time.

[jawitech]

Coins with short block times (less than a few minutes) and low difficulties will always generate lots of 'orphans' (stale blocks) before you factor in latency issues.  There is a lot that needs to be done in a short time with these very fast coins:

• Pool receives work from Coin network
• Pool sends work to miner
• Miner sends work to hardware
• Hardware find solution
• Hardware reports back to miner
• Miner verifies solution
• Miner reports back to pool
• Pool checks solution
• Pool submits solution to coin daemon
• Coin daemon checks solution
• Coin daemon submits to coin network
• Propagation

Between all that you have even more low level logic that adds additional time (TCP/IP handshake, disk access, string parsing, etc..).  It's amazing how much happens in a short period of time.

Like he said. There are some coins with low block times that cause lots of orphan blocks, like Fastcoin or 42coin. And of course, it also depends on the ratio pool hashrate / network hashrate from a certain coin. With that much hashrate, you better try some other coins or a multipool.

[enginera]

That was in Multipool and Fastcoin.

So; very low difficulties+big hashrates = orphans

I should choose harder coins next time.

[jawitech]

That was in Multipool and Fastcoin.
So; very low difficulties+big hashrates = orphans
I should choose harder coins next time.

Yes, with your hashrate you can easily mine other low-diff (probably diff between 1 and 10) coins with larger blocktimes. FST is known for that kind of problems.

If you are looking for a good multipool, i.e. for 42coin (less orphans than other pools), I can recommend Hash to Coins. They don't charge fees and have a good coin selection, you can mine with the autoswitcher or select a certain coin.

[enginera]

Now I try 12 hours.


42Coin 0,01944 for 12 hours. (160 mh/s)
Rental price 0.01844

only 0,00100 BTC profit if every calculation is correct

I cant trust

[jawitech]

Now I try 12 hours.


42Coin 0,01944 for 12 hours. (160 mh/s)
Rental price 0.01844

only 0,00100 BTC profit if every calculation is correct

I cant trust

The price of 42coin went down the last days, mostly ranged in 5-5.50 BTC per 1.0 coin. Or choose the autoswitcher which mines the most profitable coins (price, hashpower, difficulty) for the moment. Sell them i.e. on Cryptsy via autosell or collect and sell at higher prices.