Merge pull request #704 from TheSerapher/issue-695
[CHANGE] Modified some page templates
This commit is contained in:
Sebastian Grewe
commit
ab1e19bfd4
@ -1,28 +0,0 @@
|
||||
<div class="block" style="clear:none;">
|
||||
<div class="block_head">
|
||||
<div class="bheadl"></div>
|
||||
<div class="bheadr"></div>
|
||||
<h1>About PPLNS Payout system, Facts and myths</h1>
|
||||
|
||||
</div>
|
||||
<div class="block_content" style="padding:10px;">
|
||||
<p>First of all if talking about PPLNS it is important to understand how it works. PPLNS is short for “Pay Per Last N Shares”. The current proportional reward system is round based. One round is the time between the first share after the last found block and the share which solves a block. PPLNS however means that we no longer consider valid shares of one round but we consider a number N of shares. No matter if they are part of the round or not. The number N is currently for each blockchain twice the difficulty (actually rounded down to an easy to calculate integer value).</p>
|
||||
<p>Let me illustrate PPLNS using the image below. One round has an arbitrary number of shares which is solely based on sheer luck. On proportional reward system only shares of one round are considered for calculating rewards. However with PPLNS a quite constant number N of shares is considered for calculating rewards. This number N changes only with the difficulty. Please have a look at the image below:</p>
|
||||
<p style="text-align: center;"><img class="size-full wp-image-150 aligncenter" title="PPLNS share per round" src="{$PATH}/images/shares_round.png" alt="PPLNS share per round" width="450" height="80"></p>
|
||||
<p>As you know the number of shares needed to solve a block within a round is different. Round one and three needed<em> (difficulty * 2)</em> shares to be solved. Round two and four are quite short rounds. There were less than <em>(difficulty * 2)</em> shares nessecary to solve them. Round five however is a very long round which means the pool needed more than <em>(difficulty * 2)</em> shares to solve the block. From this follows that:</p>
|
||||
<ul>
|
||||
<li>Rounds one and three are like proportional rounds. All of your shares from the given round are considered for reward calculations.</li>
|
||||
<li>For rounds two and four shares from the previous rounds are considered for calculations as well (marked green). In other words: regardless of round boundaries we always consider the last <em>(difficulty * 2)</em> shares. Your portion of the amount of shares is used to calculate your reward.</li>
|
||||
<li>Round five however is very long. In this round your lowermost shares (within the marked red part) are silently dropped if they are not within the last <em>(difficulty * 2)</em> shares.</li>
|
||||
</ul>
|
||||
<p><strong>Why do we need to switch the reward system at all?</strong></p>
|
||||
<p>PPLNS favors constant and/or occasional loyal pool members over pool hoppers. As you might have seen each time we find a LTC block the pools hashrate peaks instantly. This is due to pool hoppers starting to mine. They are betting for a “quick win” (like round two above) with low shares per round. If the round exceeds a certain amount of shares they “hop” to another proportional pool which started a new round more recently trying their luck on the other pool. This assures better rewards for pool hoppers over occasional or constant miners which are loyal to their pool. Pool hopping however implies that pool hoppers need to know when a round is started and how much shares are considered for reward. This is very easy with propotional reward system. Using PPLNS this is no longer true. On long rounds (like round five above) the pool hoppers shares won’t be considered for reward calculations in favor of loyal miners. This is due to the fact that pool hoppers only mine on the beginning of rounds. On short and normal rounds pool hoppers won’t loose their shares. But due to the fact that shares from previous rounds from loyal miners are considered twice (or even more often on extremely short rounds) the pool hopper won’t get the same reward as from proportional reward system.</p>
|
||||
<p><strong>I’m only an occasional miner. Will I loose shares if playing/being offline?</strong></p>
|
||||
<p>It depends. Even if you are a constant miner you’ll loose shares on very long rounds. On the other hand if you for example stop mining shortly before the end of round three from the image above you’ll be rewarded for round three. If you then start mining on the mid of round five you’ll be rewarded a bit for round four (despite the fact you haven’t submitted any shares as some of your shares from round three are considered for round four as well) and you’ll be fully rewarded for round five (you won’t loose any shares as you “skipped” the “red part” of shares which have been cut off due to the length of the round). The point however is no one (and thus the pool hopper as well) knows when a round ends in advance. Thus you deliberately can’t avoid cut offs. Sometimes you are lucky sometimes your are not. <em><strong>This however levels out over the time for non-hoppers</strong></em>. The important point is, that you as loyal pool member have an advantage over pool hoppers. Even if you are mining only occasionally in order to enjoy the silence within your mining room.</p>
|
||||
<p><strong>Isn’t it that you as pool operator earn more from PPLNS?</strong></p>
|
||||
<p>Short answer: No. As a pool operator I’ In fact for a pool operator it doesn’t matter at all which reward system is used. I expect rounds to become a bit longer after PPLNS is activated as the pool hoppers will start to avoid the Pool. Thus revenues for me will be lower. But there were some loyal pool members who clearly stated that they want to get rid of the pool hoppers and I respect their wish. Furthermore I’m too an occasional miner on the Pool as I don’t want the miners to be running at night and from time to time I need them to test new Pool versions on development systems. Thus being a miner like you I like PPLNS better than proportional. But speaking as pool operator there is no difference between the reward systems.</p>
|
||||
<p>Thanks to g2x3k/Poolx-eu for PPLNS description</p>
|
||||
</div>
|
||||
<div class="bendl"></div>
|
||||
<div class="bendr"></div>
|
||||
</div>
|
||||
@ -1,28 +0,0 @@
|
||||
<div class="block" style="clear:none;">
|
||||
<div class="block_head">
|
||||
<div class="bheadl"></div>
|
||||
<div class="bheadr"></div>
|
||||
<h1>About PPLNS Payout system, Facts and myths</h1>
|
||||
|
||||
</div>
|
||||
<div class="block_content" style="padding:10px;">
|
||||
<p>First of all if talking about PPLNS it is important to understand how it works. PPLNS is short for “Pay Per Last N Shares”. The current proportional reward system is round based. One round is the time between the first share after the last found block and the share which solves a block. PPLNS however means that we no longer consider valid shares of one round but we consider a number N of shares. No matter if they are part of the round or not. The number N is currently for each blockchain twice the difficulty (actually rounded down to an easy to calculate integer value).</p>
|
||||
<p>Let me illustrate PPLNS using the image below. One round has an arbitrary number of shares which is solely based on sheer luck. On proportional reward system only shares of one round are considered for calculating rewards. However with PPLNS a quite constant number N of shares is considered for calculating rewards. This number N changes only with the difficulty. Please have a look at the image below:</p>
|
||||
<p style="text-align: center;"><img class="size-full wp-image-150 aligncenter" title="PPLNS share per round" src="{$PATH}/images/shares_round.png" alt="PPLNS share per round" width="450" height="80"></p>
|
||||
<p>As you know the number of shares needed to solve a block within a round is different. Round one and three needed<em> (difficulty * 2)</em> shares to be solved. Round two and four are quite short rounds. There were less than <em>(difficulty * 2)</em> shares nessecary to solve them. Round five however is a very long round which means the pool needed more than <em>(difficulty * 2)</em> shares to solve the block. From this follows that:</p>
|
||||
<ul>
|
||||
<li>Rounds one and three are like proportional rounds. All of your shares from the given round are considered for reward calculations.</li>
|
||||
<li>For rounds two and four shares from the previous rounds are considered for calculations as well (marked green). In other words: regardless of round boundaries we always consider the last <em>(difficulty * 2)</em> shares. Your portion of the amount of shares is used to calculate your reward.</li>
|
||||
<li>Round five however is very long. In this round your lowermost shares (within the marked red part) are silently dropped if they are not within the last <em>(difficulty * 2)</em> shares.</li>
|
||||
</ul>
|
||||
<p><strong>Why do we need to switch the reward system at all?</strong></p>
|
||||
<p>PPLNS favors constant and/or occasional loyal pool members over pool hoppers. As you might have seen each time we find a LTC block the pools hashrate peaks instantly. This is due to pool hoppers starting to mine. They are betting for a “quick win” (like round two above) with low shares per round. If the round exceeds a certain amount of shares they “hop” to another proportional pool which started a new round more recently trying their luck on the other pool. This assures better rewards for pool hoppers over occasional or constant miners which are loyal to their pool. Pool hopping however implies that pool hoppers need to know when a round is started and how much shares are considered for reward. This is very easy with propotional reward system. Using PPLNS this is no longer true. On long rounds (like round five above) the pool hoppers shares won’t be considered for reward calculations in favor of loyal miners. This is due to the fact that pool hoppers only mine on the beginning of rounds. On short and normal rounds pool hoppers won’t loose their shares. But due to the fact that shares from previous rounds from loyal miners are considered twice (or even more often on extremely short rounds) the pool hopper won’t get the same reward as from proportional reward system.</p>
|
||||
<p><strong>I’m only an occasional miner. Will I loose shares if playing/being offline?</strong></p>
|
||||
<p>It depends. Even if you are a constant miner you’ll loose shares on very long rounds. On the other hand if you for example stop mining shortly before the end of round three from the image above you’ll be rewarded for round three. If you then start mining on the mid of round five you’ll be rewarded a bit for round four (despite the fact you haven’t submitted any shares as some of your shares from round three are considered for round four as well) and you’ll be fully rewarded for round five (you won’t loose any shares as you “skipped” the “red part” of shares which have been cut off due to the length of the round). The point however is no one (and thus the pool hopper as well) knows when a round ends in advance. Thus you deliberately can’t avoid cut offs. Sometimes you are lucky sometimes your are not. <em><strong>This however levels out over the time for non-hoppers</strong></em>. The important point is, that you as loyal pool member have an advantage over pool hoppers. Even if you are mining only occasionally in order to enjoy the silence within your mining room.</p>
|
||||
<p><strong>Isn’t it that you as pool operator earn more from PPLNS?</strong></p>
|
||||
<p>Short answer: No. As a pool operator I’ In fact for a pool operator it doesn’t matter at all which reward system is used. I expect rounds to become a bit longer after PPLNS is activated as the pool hoppers will start to avoid the Pool. Thus revenues for me will be lower. But there were some loyal pool members who clearly stated that they want to get rid of the pool hoppers and I respect their wish. Furthermore I’m too an occasional miner on the Pool as I don’t want the miners to be running at night and from time to time I need them to test new Pool versions on development systems. Thus being a miner like you I like PPLNS better than proportional. But speaking as pool operator there is no difference between the reward systems.</p>
|
||||
<p>Thanks to g2x3k/Poolx-eu for PPLNS description</p>
|
||||
</div>
|
||||
<div class="bendl"></div>
|
||||
<div class="bendr"></div>
|
||||
</div>
|
||||
@ -1,89 +1,45 @@
|
||||
<div class="block" style="clear:none;">
|
||||
<div class="block_head">
|
||||
<div class="bheadl"></div>
|
||||
<div class="bheadr"></div>
|
||||
<h1>Getting Started</h1>
|
||||
</div>
|
||||
<div class="block_content" style="padding:10px;">
|
||||
|
||||
<p>
|
||||
</p><ol>
|
||||
<li><strong>Create account.</strong>
|
||||
<br>
|
||||
<ul>
|
||||
<li>Register <a href="{$smarty.server.PHP_SELF}?page=register">here</a>, or login if you already have account</li>
|
||||
<li>Create a <a href="{$smarty.server.PHP_SELF}?page=account&action=workers">worker</a> that will be used by the miner to login</li>
|
||||
</ul>
|
||||
|
||||
</li><li><strong>Download a miner.</strong>
|
||||
<ul>
|
||||
<li><em>Windows users:</em> download a "batteries" included package for
|
||||
<a href="http://www.mediafire.com/?l8i99fbyn41n97a">64-bit</a> or
|
||||
<a href="http://www.mediafire.com/?9nt43ahwpt1sefx">32-bit</a> Windows.
|
||||
These packages include Pooler's cpuminer 2.1.2 and Matoking's GUI r6, updated 2012-02-03.<br>
|
||||
Extract the files into a folder and start the included ScryptMiner.<br>
|
||||
If you don't want a graphical user interface, you can download an optimized command-line miner
|
||||
<a href="https://bitcointalk.org/index.php?topic=55038.msg654850#msg654850">here</a>.</li>
|
||||
<li><em>Linux users:</em> download and compile <a href="https://github.com/pooler/cpuminer">cpuminer</a>.
|
||||
Under Debian and Ubuntu, you can use the following recipe:
|
||||
<pre> sudo apt-get install make automake build-essential git libcurl4-openssl-dev
|
||||
git clone git://github.com/pooler/cpuminer.git
|
||||
cd cpuminer
|
||||
./autogen.sh
|
||||
./configure CFLAGS="-O3"
|
||||
make
|
||||
./minerd --url http://pool.grewe.ca:8337/ --userpass <em>Weblogin</em>.<em>Worker</em>:<em>Worker password</em>
|
||||
</pre></li>
|
||||
<li><em>Mac OS X users:</em> precompiled binaries are available <a href="https://bitcointalk.org/index.php?topic=55038.msg654850#msg654850">here</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li><strong>Configure your miner.</strong>
|
||||
<br>
|
||||
Start your miner using the following parameters:
|
||||
<table>
|
||||
<tbody><tr><td>URL:</td><td><kbd>http://pool.grewe.ca/</kbd></td></tr>
|
||||
<tr><td>PORT:</td><td><kbd>8337</kbd></td></tr>
|
||||
<tr><td>Username:</td><td><kbd><em>Weblogin</em>.<em>Worker</em></kbd></td></tr>
|
||||
<tr><td>Password:</td><td><kbd>Worker Password</kbd></td></tr>
|
||||
</tbody></table>
|
||||
If you use a command-line miner, type:
|
||||
<pre> ./minerd --url http://pool.grewe.ca:8337/ --userpass <em>Weblogin</em>.<em>Worker</em>:<em>Worker password</em>
|
||||
</pre>
|
||||
If you want, you can create additional workers with usernames and passwords of your choice <a href="{$smarty.server.PHP_SELF}?page=account&action=workers">Here<br></a><br>
|
||||
</li>
|
||||
<li><strong>Create a Litecoin address to recieve payments.</strong>
|
||||
<ul>
|
||||
<li> Downloading the client & block chain: Download the Litecoin client from the <a href="http://www.litecoin.org/">official site</a><br>.
|
||||
Generate a new address and input it on your account page to receive payments.
|
||||
</li>
|
||||
<li> Using Instawallet: visit the <a href="http://wallet.it.cx">LTC Instawallet</a> and create a new wallet... keep the link as it is tied to your address/balance essentially your accout<br>
|
||||
<i>downloading the client and maintaining your own wallet.dat is always safest</i>
|
||||
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
</li><li>Optional (linux): <strong>Keeping miner updated</strong></li>
|
||||
<ul>
|
||||
<li>Updateting manual:
|
||||
<pre> cd cpuminer
|
||||
git pull
|
||||
make clean
|
||||
./configure CFLAGS="-O3"
|
||||
make
|
||||
./minerd --url http://pool.grewe.ca:8337/ --userpass <em>Weblogin</em>.<em>Worker</em>:<em>Worker Password</em>
|
||||
</pre>
|
||||
</li>
|
||||
|
||||
{include file="global/block_header.tpl" BLOCK_HEADER="Getting Started Guide" BLOCK_STYLE="clear:none;"}
|
||||
<li>1. <strong>Create account.</strong>
|
||||
<ul>
|
||||
<li>Register <a href="{$smarty.server.PHP_SELF}?page=register">here</a>, or login if you already have account</li>
|
||||
<li>Create a <a href="{$smarty.server.PHP_SELF}?page=account&action=workers">worker</a> that will be used by the miner to login</li>
|
||||
</ul>
|
||||
<br><br>Thanks alot to <b>Pooler</b> for all his work on the minerd, <a href="https://github.com/pooler/cpuminer">@Github</a> & <a href="https://bitcointalk.org/index.php?action=profile;u=43931">@bitcointalk</a>
|
||||
|
||||
|
||||
</ol>
|
||||
|
||||
|
||||
</div> <!-- nested block ends -->
|
||||
<div class="bendl"></div>
|
||||
<div class="bendr"></div>
|
||||
</div>
|
||||
</li>
|
||||
<li>2. <strong>Download a miner.</strong>
|
||||
<ul>
|
||||
<li><em>Windows:</em> <a href="http://ck.kolivas.org/apps/cgminer/3.4/cgminer-3.4.3-windows.zip">Cgminer for Windows</a></li>
|
||||
<li><em>Linux:</em> <a href="http://ck.kolivas.org/apps/cgminer/3.4/cgminer-3.4.3-x86_64-built.tar.bz2">Cgminer for Linux (64bit)</a></li>
|
||||
<li><em>Mac OS X:</em> precompiled binaries are available <a href="https://bitcointalk.org/index.php?topic=55038.msg654850#msg654850">here</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>3. <strong>Configure your miner.</strong>
|
||||
<p>Settings for Stratum (recommended):</p>
|
||||
<table width="50%">
|
||||
<tbody>
|
||||
<tr><td>STRATUM:</td><td><kbd>stratum+tcp://{$smarty.server.SERVER_NAME}</kbd></td></tr>
|
||||
<tr><td>PORT:</td><td><kbd>3333</kbd></td></tr>
|
||||
<tr><td>Username:</td><td><kbd><em>Weblogin</em>.<em>Worker</em></kbd></td></tr>
|
||||
<tr><td>Password:</td><td><kbd>Worker Password</kbd></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>If you use a command-line miner, type:</p>
|
||||
<pre>./cgminer --scrypt -o stratum+tcp://{$smarty.server.SERVER_NAME}:3333 -u <em>Weblogin</em>.<em>Worker</em> -p <em>Worker password</em></pre>
|
||||
<p>If you want, you can create additional workers with usernames and passwords of your choice <a href="{$smarty.server.PHP_SELF}?page=account&action=workers">Here</a></p>
|
||||
</li>
|
||||
<li>4. <strong>Create a Litecoin address to recieve payments.</strong>
|
||||
<ul>
|
||||
<li> Downloading the client & block chain: Download the Litecoin client from the <a href="http://www.litecoin.org/">here</a>.
|
||||
<p>Generate a new address and input it on your account page to receive payments.</p>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>5. <strong>Advanced cgminer settings / FAQ</strong>
|
||||
<ul>
|
||||
<li><a href="https://github.com/ckolivas/cgminer/blob/master/SCRYPT-README">Scrypt readme</a></li>
|
||||
<li>Don't set <b>intensity</b> too high, I=11 is standard and safest. Higher intensity takes more GPU RAM. Check for <b>hardware errors</b> in cgminer (HW). HW=0 is good, otherwise lower intensity :)</li>
|
||||
<li>Set shaders according to the readme (or look at your graphic cards specifications). Cgminer uses this value at first run to calculate <b>thread-concurrency</b>. Easiest way to get this optimized is to use same settings as others have used here: <a href="http://litecoin.info/Mining_Hardware_Comparison">here</a>.</li>
|
||||
<li>There's also an interesting project which gives you a GUI for cgminer. Windows only it seems.</li>
|
||||
<li>Here's a great <a href="https://docs.google.com/document/d/1Gw7YPYgMgNNU42skibULbJJUx_suP_CpjSEdSi8_z9U/preview?sle=true">guide</a> how to get up and running with Xubuntu.</li>
|
||||
</ul>
|
||||
</li>
|
||||
{include file="global/block_footer.tpl"}
|
||||
|
||||
@ -1,25 +0,0 @@
|
||||
<article class="module width_full">
|
||||
<header><h3>About PPLNS Payout system, Facts and myths</h3></header>
|
||||
<div class="module_content">
|
||||
<table width="100%">
|
||||
<tbody>
|
||||
<p>First of all if talking about PPLNS it is important to understand how it works. PPLNS is short for .Pay Per Last N Shares.. The current proportional reward system is round based. One round is the time between the first share after the last found block and the share which solves a block. PPLNS however means that we no longer consider valid shares of one round but we consider a number N of shares. No matter if they are part of the round or not. The number N is currently for each blockchain twice the difficulty (actually rounded down to an easy to calculate integer value).</p>
|
||||
<p>Let me illustrate PPLNS using the image below. One round has an arbitrary number of shares which is solely based on sheer luck. On proportional reward system only shares of one round are considered for calculating rewards. However with PPLNS a quite constant number N of shares is considered for calculating rewards. This number N changes only with the difficulty. Please have a look at the image below:</p>
|
||||
<p style="text-align: center;"><img class="size-full wp-image-150 aligncenter" title="PPLNS share per round" src="{$PATH}/images/shares_round.png" alt="PPLNS share per round" width="450" height="80"></p>
|
||||
<p>As you know the number of shares needed to solve a block within a round is different. Round one and three needed<em> (difficulty * 2)</em> shares to be solved. Round two and four are quite short rounds. There were less than <em>(difficulty * 2)</em> shares nessecary to solve them. Round five however is a very long round which means the pool needed more than <em>(difficulty * 2)</em> shares to solve the block. From this follows that:</p>
|
||||
<ul>
|
||||
<li>Rounds one and three are like proportional rounds. All of your shares from the given round are considered for reward calculations.</li>
|
||||
<li>For rounds two and four shares from the previous rounds are considered for calculations as well (marked green). In other words: regardless of round boundaries we always consider the last <em>(difficulty * 2)</em> shares. Your portion of the amount of shares is used to calculate your reward.</li>
|
||||
<li>Round five however is very long. In this round your lowermost shares (within the marked red part) are silently dropped if they are not within the last <em>(difficulty * 2)</em> shares.</li>
|
||||
</ul>
|
||||
<p><strong>Why do we need to switch the reward system at all?</strong></p>
|
||||
<p>PPLNS favors constant and/or occasional loyal pool members over pool hoppers. As you might have seen each time we find a LTC block the pools hashrate peaks instantly. This is due to pool hoppers starting to mine. They are betting for a .quick win. (like round two above) with low shares per round. If the round exceeds a certain amount of shares they .hop. to another proportional pool which started a new round more recently trying their luck on the other pool. This assures better rewards for pool hoppers over occasional or constant miners which are loyal to their pool. Pool hopping however implies that pool hoppers need to know when a round is started and how much shares are considered for reward. This is very easy with propotional reward system. Using PPLNS this is no longer true. On long rounds (like round five above) the pool hoppers shares won.t be considered for reward calculations in favor of loyal miners. This is due to the fact that pool hoppers only mine on the beginning of rounds. On short and normal rounds pool hoppers won.t loose their shares. But due to the fact that shares from previous rounds from loyal miners are considered twice (or even more often on extremely short rounds) the pool hopper won.t get the same reward as from proportional reward system.</p>
|
||||
<p><strong>I.m only an occasional miner. Will I loose shares if playing/being offline?</strong></p>
|
||||
<p>It depends. Even if you are a constant miner you.ll loose shares on very long rounds. On the other hand if you for example stop mining shortly before the end of round three from the image above you.ll be rewarded for round three. If you then start mining on the mid of round five you.ll be rewarded a bit for round four (despite the fact you haven.t submitted any shares as some of your shares from round three are considered for round four as well) and you.ll be fully rewarded for round five (you won.t loose any shares as you .skipped. the .red part. of shares which have been cut off due to the length of the round). The point however is no one (and thus the pool hopper as well) knows when a round ends in advance. Thus you deliberately can.t avoid cut offs. Sometimes you are lucky sometimes your are not. <em><strong>This however levels out over the time for non-hoppers</strong></em>. The important point is, that you as loyal pool member have an advantage over pool hoppers. Even if you are mining only occasionally in order to enjoy the silence within your mining room.</p>
|
||||
<p><strong>Isn.t it that you as pool operator earn more from PPLNS?</strong></p>
|
||||
<p>Short answer: No. As a pool operator I. In fact for a pool operator it doesn.t matter at all which reward system is used. I expect rounds to become a bit longer after PPLNS is activated as the pool hoppers will start to avoid the Pool. Thus revenues for me will be lower. But there were some loyal pool members who clearly stated that they want to get rid of the pool hoppers and I respect their wish. Furthermore I.m too an occasional miner on the Pool as I don.t want the miners to be running at night and from time to time I need them to test new Pool versions on development systems. Thus being a miner like you I like PPLNS better than proportional. But speaking as pool operator there is no difference between the reward systems.</p>
|
||||
<p>Thanks to g2x3k/Poolx-eu for PPLNS description</p>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</article>
|
||||
@ -1,25 +0,0 @@
|
||||
<article class="module width_full">
|
||||
<header><h3>About PPLNS Payout system, Facts and myths</h3></header>
|
||||
<div class="module_content">
|
||||
<table width="100%">
|
||||
<tbody>
|
||||
<p>First of all if talking about PPLNS it is important to understand how it works. PPLNS is short for .Pay Per Last N Shares.. The current proportional reward system is round based. One round is the time between the first share after the last found block and the share which solves a block. PPLNS however means that we no longer consider valid shares of one round but we consider a number N of shares. No matter if they are part of the round or not. The number N is currently for each blockchain twice the difficulty (actually rounded down to an easy to calculate integer value).</p>
|
||||
<p>Let me illustrate PPLNS using the image below. One round has an arbitrary number of shares which is solely based on sheer luck. On proportional reward system only shares of one round are considered for calculating rewards. However with PPLNS a quite constant number N of shares is considered for calculating rewards. This number N changes only with the difficulty. Please have a look at the image below:</p>
|
||||
<p style="text-align: center;"><img class="size-full wp-image-150 aligncenter" title="PPLNS share per round" src="{$PATH}/images/shares_round.png" alt="PPLNS share per round" width="450" height="80"></p>
|
||||
<p>As you know the number of shares needed to solve a block within a round is different. Round one and three needed<em> (difficulty * 2)</em> shares to be solved. Round two and four are quite short rounds. There were less than <em>(difficulty * 2)</em> shares nessecary to solve them. Round five however is a very long round which means the pool needed more than <em>(difficulty * 2)</em> shares to solve the block. From this follows that:</p>
|
||||
<ul>
|
||||
<li>Rounds one and three are like proportional rounds. All of your shares from the given round are considered for reward calculations.</li>
|
||||
<li>For rounds two and four shares from the previous rounds are considered for calculations as well (marked green). In other words: regardless of round boundaries we always consider the last <em>(difficulty * 2)</em> shares. Your portion of the amount of shares is used to calculate your reward.</li>
|
||||
<li>Round five however is very long. In this round your lowermost shares (within the marked red part) are silently dropped if they are not within the last <em>(difficulty * 2)</em> shares.</li>
|
||||
</ul>
|
||||
<p><strong>Why do we need to switch the reward system at all?</strong></p>
|
||||
<p>PPLNS favors constant and/or occasional loyal pool members over pool hoppers. As you might have seen each time we find a LTC block the pools hashrate peaks instantly. This is due to pool hoppers starting to mine. They are betting for a .quick win. (like round two above) with low shares per round. If the round exceeds a certain amount of shares they .hop. to another proportional pool which started a new round more recently trying their luck on the other pool. This assures better rewards for pool hoppers over occasional or constant miners which are loyal to their pool. Pool hopping however implies that pool hoppers need to know when a round is started and how much shares are considered for reward. This is very easy with propotional reward system. Using PPLNS this is no longer true. On long rounds (like round five above) the pool hoppers shares won.t be considered for reward calculations in favor of loyal miners. This is due to the fact that pool hoppers only mine on the beginning of rounds. On short and normal rounds pool hoppers won.t loose their shares. But due to the fact that shares from previous rounds from loyal miners are considered twice (or even more often on extremely short rounds) the pool hopper won.t get the same reward as from proportional reward system.</p>
|
||||
<p><strong>I.m only an occasional miner. Will I loose shares if playing/being offline?</strong></p>
|
||||
<p>It depends. Even if you are a constant miner you.ll loose shares on very long rounds. On the other hand if you for example stop mining shortly before the end of round three from the image above you.ll be rewarded for round three. If you then start mining on the mid of round five you.ll be rewarded a bit for round four (despite the fact you haven.t submitted any shares as some of your shares from round three are considered for round four as well) and you.ll be fully rewarded for round five (you won.t loose any shares as you .skipped. the .red part. of shares which have been cut off due to the length of the round). The point however is no one (and thus the pool hopper as well) knows when a round ends in advance. Thus you deliberately can.t avoid cut offs. Sometimes you are lucky sometimes your are not. <em><strong>This however levels out over the time for non-hoppers</strong></em>. The important point is, that you as loyal pool member have an advantage over pool hoppers. Even if you are mining only occasionally in order to enjoy the silence within your mining room.</p>
|
||||
<p><strong>Isn.t it that you as pool operator earn more from PPLNS?</strong></p>
|
||||
<p>Short answer: No. As a pool operator I. In fact for a pool operator it doesn.t matter at all which reward system is used. I expect rounds to become a bit longer after PPLNS is activated as the pool hoppers will start to avoid the Pool. Thus revenues for me will be lower. But there were some loyal pool members who clearly stated that they want to get rid of the pool hoppers and I respect their wish. Furthermore I.m too an occasional miner on the Pool as I don.t want the miners to be running at night and from time to time I need them to test new Pool versions on development systems. Thus being a miner like you I like PPLNS better than proportional. But speaking as pool operator there is no difference between the reward systems.</p>
|
||||
<p>Thanks to g2x3k/Poolx-eu for PPLNS description</p>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</article>
|
||||
@ -1,80 +1,48 @@
|
||||
<article class="module width_full">
|
||||
<header><h3>GettingStarted</h3></header>
|
||||
<div class="module_content">
|
||||
<table width="100%">
|
||||
<tbody>
|
||||
<p>
|
||||
</p>
|
||||
<li>1. <strong>Create account.</strong>
|
||||
<br>
|
||||
<ul>
|
||||
<li>Register <a href="{$smarty.server.PHP_SELF}?page=register">here</a>, or login if you already have account</li>
|
||||
<li>Create a <a href="{$smarty.server.PHP_SELF}?page=account&action=workers">worker</a> that will be used by the miner to login</li>
|
||||
</ul>
|
||||
|
||||
</li><li>2. <strong>Download a miner.</strong>
|
||||
<ul>
|
||||
<li><em>Windows users:</em> download and unzip:
|
||||
<a href="http://ck.kolivas.org/apps/cgminer/3.2/cgminer-3.2.2-windows.zip">Cgminer-3.2.2-windows.zip</a>.
|
||||
<li><em>Linux users:</em> download and unpack :
|
||||
<a href="http://ck.kolivas.org/apps/cgminer/3.2/cgminer-3.2.2-x86_64.tar.bz2">Cgminer-3.2.2 (64bit)</a>
|
||||
</pre></li>
|
||||
<li><em>Mac OS X users:</em> precompiled binaries are available <a href="https://bitcointalk.org/index.php?topic=55038.msg654850#msg654850">here</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>3. <strong>Configure your miner.</strong>
|
||||
<br><br>
|
||||
Settings for Stratum (recommended):
|
||||
</table>
|
||||
</tbody>
|
||||
<br>
|
||||
<table width="100%">
|
||||
<tbody>
|
||||
<tr><td>STRATUM:</td><td><kbd>stratum+tcp://yourdomain.com</kbd></td></tr>
|
||||
<tr><td>PORT:</td><td><kbd>3333</kbd></td></tr>
|
||||
<tr><td>Username:</td><td><kbd><em>Weblogin</em>.<em>Worker</em></kbd></td></tr>
|
||||
<tr><td>Password:</td><td><kbd>Worker Password</kbd></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table width="100%">
|
||||
<tbody>
|
||||
<br>
|
||||
If you use a command-line miner, type:
|
||||
<pre> ./cgminer --scrypt -o stratum+tcp://yourdomain.com:3333 -u <em>Weblogin</em>.<em>Worker</em> -p <em>Worker password</em>
|
||||
</pre>
|
||||
If you want, you can create additional workers with usernames and passwords of your choice <a href="{$smarty.server.PHP_SELF}?page=account&action=workers">Here<br></a><br>
|
||||
</li>
|
||||
<li>4. <strong>Create a Litecoin address to recieve payments.</strong>
|
||||
<ul>
|
||||
<li> Downloading the client & block chain: Download the Litecoin client from the <a href="http://www.litecoin.org/">here</a>.<br>
|
||||
Generate a new address and input it on your account page to receive payments.
|
||||
</li>
|
||||
</li>
|
||||
</tbody>
|
||||
</table>
|
||||
<table width="100%">
|
||||
<tbody>
|
||||
<li>5. <strong>Advanced cgminer settings / FAQ</strong>
|
||||
<ul>
|
||||
<li>
|
||||
<a href="https://github.com/ckolivas/cgminer/blob/master/SCRYPT-README">Scrypt readme</a>
|
||||
</li>
|
||||
<li>
|
||||
Don't set <b>intensity</b> too high, I=11 is standard and safest. Higher intensity takes more GPU RAM. Check for <b>hardware errors</b> in cgminer (HW). HW=0 is good, otherwise lower intensity :)
|
||||
</li>
|
||||
<li>
|
||||
Set shaders according to the readme (or look at your graphic cards specifications). Cgminer uses this value at first run to calculate <b>thread-concurrency</b>.
|
||||
Easiest way to get this optimized is to use same settings as others have used here: <a href="http://litecoin.info/Mining_Hardware_Comparison">here</a>.
|
||||
</li>
|
||||
<li>
|
||||
There's also an interesting project which gives you a GUI for cgminer. Windows only it seems.
|
||||
</li>
|
||||
<li>
|
||||
Here's a great <a href="https://docs.google.com/document/d/1Gw7YPYgMgNNU42skibULbJJUx_suP_CpjSEdSi8_z9U/preview?sle=true">guide</a> how to get up and running with Xubuntu.
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
</tbody>
|
||||
<header><h3>Getting Started Guide</h3></header>
|
||||
<div class="module_content">
|
||||
<li>1. <strong>Create account.</strong>
|
||||
<ul>
|
||||
<li>Register <a href="{$smarty.server.PHP_SELF}?page=register">here</a>, or login if you already have account</li>
|
||||
<li>Create a <a href="{$smarty.server.PHP_SELF}?page=account&action=workers">worker</a> that will be used by the miner to login</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>2. <strong>Download a miner.</strong>
|
||||
<ul>
|
||||
<li><em>Windows:</em> <a href="http://ck.kolivas.org/apps/cgminer/3.4/cgminer-3.4.3-windows.zip">Cgminer for Windows</a></li>
|
||||
<li><em>Linux:</em> <a href="http://ck.kolivas.org/apps/cgminer/3.4/cgminer-3.4.3-x86_64-built.tar.bz2">Cgminer for Linux (64bit)</a></li>
|
||||
<li><em>Mac OS X:</em> precompiled binaries are available <a href="https://bitcointalk.org/index.php?topic=55038.msg654850#msg654850">here</a>.</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>3. <strong>Configure your miner.</strong>
|
||||
<p>Settings for Stratum (recommended):</p>
|
||||
<table width="50%">
|
||||
<tbody>
|
||||
<tr><td>STRATUM:</td><td><kbd>stratum+tcp://{$smarty.server.SERVER_NAME}</kbd></td></tr>
|
||||
<tr><td>PORT:</td><td><kbd>3333</kbd></td></tr>
|
||||
<tr><td>Username:</td><td><kbd><em>Weblogin</em>.<em>Worker</em></kbd></td></tr>
|
||||
<tr><td>Password:</td><td><kbd>Worker Password</kbd></td></tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
</article>
|
||||
<p>If you use a command-line miner, type:</p>
|
||||
<pre>./cgminer --scrypt -o stratum+tcp://{$smarty.server.SERVER_NAME}:3333 -u <em>Weblogin</em>.<em>Worker</em> -p <em>Worker password</em></pre>
|
||||
<p>If you want, you can create additional workers with usernames and passwords of your choice <a href="{$smarty.server.PHP_SELF}?page=account&action=workers">Here</a></p>
|
||||
</li>
|
||||
<li>4. <strong>Create a Litecoin address to recieve payments.</strong>
|
||||
<ul>
|
||||
<li> Downloading the client & block chain: Download the Litecoin client from the <a href="http://www.litecoin.org/">here</a>.
|
||||
<p>Generate a new address and input it on your account page to receive payments.</p>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
<li>5. <strong>Advanced cgminer settings / FAQ</strong>
|
||||
<ul>
|
||||
<li><a href="https://github.com/ckolivas/cgminer/blob/master/SCRYPT-README">Scrypt readme</a></li>
|
||||
<li>Don't set <b>intensity</b> too high, I=11 is standard and safest. Higher intensity takes more GPU RAM. Check for <b>hardware errors</b> in cgminer (HW). HW=0 is good, otherwise lower intensity :)</li>
|
||||
<li>Set shaders according to the readme (or look at your graphic cards specifications). Cgminer uses this value at first run to calculate <b>thread-concurrency</b>. Easiest way to get this optimized is to use same settings as others have used here: <a href="http://litecoin.info/Mining_Hardware_Comparison">here</a>.</li>
|
||||
<li>There's also an interesting project which gives you a GUI for cgminer. Windows only it seems.</li>
|
||||
<li>Here's a great <a href="https://docs.google.com/document/d/1Gw7YPYgMgNNU42skibULbJJUx_suP_CpjSEdSi8_z9U/preview?sle=true">guide</a> how to get up and running with Xubuntu.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</div>
|
||||
</article>
|
||||
|
||||
@ -52,8 +52,6 @@
|
||||
<ul class="toggle">
|
||||
<li class="icon-desktop"><a href="{$smarty.server.PHP_SELF}?page=gettingstarted">GettingStarted</a></li>
|
||||
<li class="icon-doc"><a href="{$smarty.server.PHP_SELF}?page=about&action=pool">About</a></li>
|
||||
<li class="icon-bell"><a href="{$smarty.server.PHP_SELF}?page=about&action=pplns">PPLNS</a></li>
|
||||
<li class="icon-wrench"><a href="{$smarty.server.PHP_SELF}?page=about&action=vardiff">VARDIFF</a></li>
|
||||
<li class="icon-money"><a href="{$smarty.server.PHP_SELF}?page=about&action=donors">Donors</a></li>
|
||||
</ul>
|
||||
<h3>Other</h3>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user