Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

Recommended Minimum Hash Speed.

Discussion in 'Mining' started by Propulsion, Apr 13, 2014.

  1. Propulsion

    Propulsion The buck stops here.

    Joined:
    Feb 26, 2014
    Messages:
    1,008
    Likes Received:
    467
    Trophy Points:
    183
    Dash Address:
    XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
    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
     
  2. chaeplin

    chaeplin Active Member
    Core Developer

    Joined:
    Mar 29, 2014
    Messages:
    749
    Likes Received:
    356
    Trophy Points:
    133
    https://litecointalk.org/index.php?topic=3980.0


    p2pool-drk patched with https://github.com/donSchoe/p2pool-n/pull/6.
     
  3. Propulsion

    Propulsion The buck stops here.

    Joined:
    Feb 26, 2014
    Messages:
    1,008
    Likes Received:
    467
    Trophy Points:
    183
    Dash Address:
    XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
    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?
     
  4. chaeplin

    chaeplin Active Member
    Core Developer

    Joined:
    Mar 29, 2014
    Messages:
    749
    Likes Received:
    356
    Trophy Points:
    133
    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
     
  5. vertoe

    vertoe Three of Nine

    Joined:
    Mar 28, 2014
    Messages:
    2,573
    Likes Received:
    1,652
    Trophy Points:
    1,283
    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.
     
  6. vertoe

    vertoe Three of Nine

    Joined:
    Mar 28, 2014
    Messages:
    2,573
    Likes Received:
    1,652
    Trophy Points:
    1,283
    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.
     
  7. HammerHedd

    HammerHedd Member

    Joined:
    Mar 10, 2014
    Messages:
    182
    Likes Received:
    34
    Trophy Points:
    88
    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.
     
  8. Propulsion

    Propulsion The buck stops here.

    Joined:
    Feb 26, 2014
    Messages:
    1,008
    Likes Received:
    467
    Trophy Points:
    183
    Dash Address:
    XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
    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?
     
  9. vertoe

    vertoe Three of Nine

    Joined:
    Mar 28, 2014
    Messages:
    2,573
    Likes Received:
    1,652
    Trophy Points:
    1,283
    Yes, the number looks real if compared with the connected worker rates here: http://q30.qhor.net:7903/

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

    Propulsion The buck stops here.

    Joined:
    Feb 26, 2014
    Messages:
    1,008
    Likes Received:
    467
    Trophy Points:
    183
    Dash Address:
    XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
    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.
     
  11. vertoe

    vertoe Three of Nine

    Joined:
    Mar 28, 2014
    Messages:
    2,573
    Likes Received:
    1,652
    Trophy Points:
    1,283
    The retarget is always done by the pool so I guess its a pool bug.
     
  12. scorpio18

    scorpio18 New Member

    Joined:
    Apr 27, 2014
    Messages:
    25
    Likes Received:
    3
    Trophy Points:
    3
    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