From acecc5ea1dd2287f36ced1193d09460fb3585c58 Mon Sep 17 00:00:00 2001 From: nrpatten Date: Thu, 12 Sep 2013 19:22:56 +1000 Subject: [PATCH] Create default.tpl --- public/templates/test/about/pool/default.tpl | 32 ++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 public/templates/test/about/pool/default.tpl diff --git a/public/templates/test/about/pool/default.tpl b/public/templates/test/about/pool/default.tpl new file mode 100644 index 00000000..ec0fbbcf --- /dev/null +++ b/public/templates/test/about/pool/default.tpl @@ -0,0 +1,32 @@ +
+

ThePool Collective

+
+ + +

After mining in other pools I have decided to setup my own pool, mostly for educational reason. I was curious how pools work, what is needed to get them started and what tools can be used to run them.

+

Lots of digging finally revealed that the following tools were required to run a Litecoin pool:

+ +
    +
  • Litecoin
  • +
  • 1. Provides litecoind, used to synchronize blocks and offer the API the pool connects to
  • +
  • Pushpool 0.5.1-tenebrix, a modified version of Pushpool supporting changed target difficulties (2^22 in this pool)
  • +
  • 2. Provides the API each worker (client miner) authenticates and connects to
  • +
  • mmcFE modified by Greedi & g2x3k with adjustments for this pool (proper hashrate for 2^22 difficulty)
  • +
  • 3. The Webinterface merging SQL and API information into a cohesive interface for user and worker management
  • +
+ +

+The hardest part was finding all the information needed and applying it to a new setup. +Many tools exist and even those three took a while to get them to work. +Especially the difficulty adjustment would not have been possible (for me) if it wasn't +for the pushpool tenebrix branch allowing a custom target bit and reducing difficulty per share. +More adjustments in the PHP code were necessary to reflect those changes and, at least +close enough, properly display hashrates on the pool site. It is running well right now but +please keen in mind that neither the code nor functionaliy are supported. +I am not responsible for lost coins due to a pool crash or other malfunctions which +could be caused by by code or the tools used in this implementation. +

+ +
+
+