Recommended Minimum Hash Speed.

Propulsion

Propulsion

The buck stops here.
What is the recommended hash speed for P2P pool mining? I know there is a minimum recommended speed for scrypt as seen here. http://ltc.noshit.pl/p2pool
My question is how and why did they come to the conclusion that that is the minimum and recommended speed? Thanks!:D
 
https://litecointalk.org/index.php?topic=3980.0

Problem with p2pool for small LTC Miners
http://ltc.block-explorer.com/block/f969ae9e8e5eaf5563c0a07ca3fc5d7ea3b49192179136e2b9793a58836e157b
Here is a typical p2pool LTC block where there are often 500-600 payouts. This is fine for the bigger miners who receive like 0.1 LTC per block, but it becomes increasingly problematic for the smaller miners as payout amounts per block become tinier and tinier. As many of you know, spending the tiny p2pool dust can be very expensive in fees, or annoyingly time consuming if you use the free tx combining method.
Click to expand...


p2pool-drk patched with https://github.com/donSchoe/p2pool-n/pull/6.
Instead of small miners getting assigned share diff targets based on the node's local hash rate, it will use the payment addresses' hash rate. Thus a small miner on a big public node has the same diff target as if they ran their own node instead.
Click to expand...

DRK AddressHashrateDOA Hashrate (DOA %)Share difficultyTime to sharePredicted payout
Xf6txyXmmxVtRaWAmprD1nMGrEAJkGCTjR 249.56 KH/s0.00 H/s (0.00%)0.791 (51.83 K)3h 46m 52s0.01231954 DRK
XdeUrJen8KMxF3z4yjXT88SjfZfPj9Ufeu 452.13 KH/s11.94 KH/s (2.64%)0.851 (55.78 K)2h 14m 44s0.09636128 DRK
Click to expand...
 
p2p.png


So the only reason they recommend a higher hash rate is to avoid a lower frequency of being payed?

It seems that my hashrate is so low that I am unable to submit a share before moving on to the next work share. With a regular pool I do not run into this issue. Is there anyway to reduce the work restarts?
 
Propulsion said:
View attachment 52

So the only reason they recommend a higher hash rate is to avoid a lower frequency of being payed?

It seems that my hashrate is so low that I am unable to submit a share before moving on to the next work share. With a regular pool I do not run into this issue. Is there anyway to reduce the work restarts?
Click to expand...

work restart is common in p2pool.

you can use custom difficuly, -u address+0.004 (example).

regular pool : target never changed between blocks
p2pool : share chain target changed between blocks

https://en.bitcoin.it/wiki/P2Pool
P2Pool creates a new block chain in which the difficulty is adjusted so a new block is found every 30 seconds. The blocks that get into the P2Pool block chain (called the "share chain") are the same blocks that would get into the Bitcoin block chain, only they have a lower difficulty target. Whenever a peer announces a new share found (new block in the P2Pool block chain), it is received by the other peers, and the other peers verify that this block contains payouts for all the previous miners who found a share (and announced it) that made it into the P2Pool share chain. This continues until some peer finds a block that has a difficulty that meets the Bitcoin network's difficulty target. This peer announces this block to the Bitcoin network and miners who have submitted shares for this block are paid in the generation transaction, proportionally to how many shares they have found in the last while. - Unknown author
Click to expand...
 
Propulsion said:
What is the recommended hash speed for P2P pool mining? I know there is a minimum recommended speed for scrypt as seen here. http://ltc.noshit.pl/p2pool
My question is how and why did they come to the conclusion that that is the minimum and recommended speed? Thanks!:D
Click to expand...
The minimum recommended hashrate is a bit difficult to calculate.

It is based on
  • the p2pool share target difficulty (Currently: 0.868773 / 56.9k),
  • the p2pool spread (DRK P2Pool: 30 Blocks)
Let's assume you want to get regular 24/7 payouts without any blocks paying you nothing. Therefore you have to solve at least one hash with the diff higher than p2pool share target diff (56k) every 30 blocks (which is around 23h at current p2pool hashrate). Now you can simply break this down on which hashrate you need to find at least one such share every 23 hours.

Not sure on the exact formula, but for Darkcoin this should be not very high. If anyone want to do the math, these are the variables.

The main difference to Litecoin is basicly the p2pool spread which is only 3 blocks for the LTC network. Therefore you need to solve a p2pool target share of 4.047421 (265k) diff every 3 p2pool blocks, and this is resulting in a pretty high minimum recommended hashrate.

To be honest I dont understand why Litecoin changed the spread from initially 12 to 3. This only benefits big miners.
 
Ok, I tried to do the maths.

Code: 
# Current snapshot:
diff_block  =         345.275983 # Network difficulty (22.6M)
diff_share  =           1.006326 # P2pool share difficulty (66.0k)
hash_netwrk = 11800000000.0      # Network hashrate (11.8GH/s)
hash_p2pool =   822000000.0      # P2pool hashrate (822MH/s)
block_24hr  =          43.4      # Expected blocks per day
block_sprd  =          30.0      # P2Pool blocks payout spread

# Time to p2pool target share
solve_time  =  block_sprd / block_24hr * 24hr
solve_time  =        30.0 /       43.4 * 24.0
solve_time  =           16.590  # one target share every 16 hours

# Difficulty; Blocktime; Hashrate
345.275983; 150; 11800000000
1.006326; 59723.502; ???

# Hashrate to find a block every 16 hours
59723.502 / 150 = 398.157
11800000000 / 398.157 = 29636574.074   # 29.6MH/s

# Hashrate to find a p2pool target share every 16 hours
345.275983 / 1.006326 = 343.105
29636574.074 / 343.105 = 86377.439     # 86.4kH/s

Currently the minimum recommended hashrate should be 86.4kH/s. But I'm not sure if I'm missing anything.
 
vertoe said:
Ok, I tried to do the maths.

Code: 
# Current snapshot:
diff_block  =         345.275983 # Network difficulty (22.6M)
diff_share  =           1.006326 # P2pool share difficulty (66.0k)
hash_netwrk = 11800000000.0      # Network hashrate (11.8GH/s)
hash_p2pool =   822000000.0      # P2pool hashrate (822MH/s)
block_24hr  =          43.4      # Expected blocks per day
block_sprd  =          30.0      # P2Pool blocks payout spread

# Time to p2pool target share
solve_time  =  block_sprd / block_24hr * 24hr
solve_time  =        30.0 /       43.4 * 24.0
solve_time  =           16.590  # one target share every 16 hours

# Difficulty; Blocktime; Hashrate
345.275983; 150; 11800000000
1.006326; 59723.502; ???

# Hashrate to find a block every 16 hours
59723.502 / 150 = 398.157
11800000000 / 398.157 = 29636574.074   # 29.6MH/s

# Hashrate to find a p2pool target share every 16 hours
345.275983 / 1.006326 = 343.105
29636574.074 / 343.105 = 86377.439     # 86.4kH/s

Currently the minimum recommended hashrate should be 86.4kH/s. But I'm not sure if I'm missing anything.
Click to expand...

I follow the math - I hope you are right, because that basically means that almost anyone with a CPU can still mine DRK via P2Pool.
 
Is there a good custom difficulty setting for smaller miners, less then 1mh/s to avoid so many work restarts?
Also does using a custom difficulty negatively affect the network in any way?
 
HammerHedd said:
I follow the math - I hope you are right, because that basically means that almost anyone with a CPU can still mine DRK via P2Pool.
Click to expand...
Yes, the number looks real if compared with the connected worker rates here: http://q30.qhor.net:7903/

Propulsion said:
Is there a good custom difficulty setting for smaller miners, less then 1mh/s to avoid so many work restarts? Also does using a custom difficulty negatively affect your profit in any way? Thanks!
Click to expand...
Work restarts are "the normalest" thing you can get with p2pool and does not affect your mining. Its just a technical detail spamming your sgminer. Ignore it :)

Try +0.001 with 1 MH/s. Decrease the number if you don't like the results. You will see you get a lower share difficulty assigned and more accepted shares. Don't set it too low, this might spam the server and you get more rejects. Just play with that number until you like it.
 
Doing [p2pool address]+0.001 works very nicely. Seems that there is a bug in SPH-sgminer 4.1 though. When switching to a regular pool from the same config file, it keeps the same p2pool difficulty and doesn't retarget.
 
This is the settings for the Manual Share Difficulty based on your rig hash rate

Reccomended Share Difficulty
1 +0.00000116

5 +0.00000582

10 +0.00001164

50 +0.00005821

100 +0.00011641

250 +0.00029103

500 +0.00058207

750 +0.00087310

1000 +0.00116414

Add this number to the end of your username (wallet address)

Example: If you have 10 MH/s then will be like this 10000 KH/S * 0.00000116 = 0.0116 so your settings will be like this -u walletaddress+0.0116

P.S You need to have a good latency to whit the p2pool node
 
You must log in or register to reply here.
Back
Top