qrlMining_NewSite

This will be the site we host the pool and the main page for qrlmining.com

Branch This repo and add your features

Please build in a branch and merge any working features to master.

To-Do list

Site -

• Fill Content

Server

• Get ReactJS working
• Setup site to use react-foundation
• Get API info scraping and storage setup
  • List of API's we are going to scrape
  • Feed into D3 or similar and make graphs and pretty things
• Move into production env. harden and secure server

Hosting and analytics

• SEO presence from Google webmaster
• Import analytics and tracking via google/analytics
• Edit DNS settings to point to production server
• ...

---

WebSite Setup

There is a conf folder in the web server root. you will find configuration files there.

To setup the email server mailing list you will need to move files into the correct places, give the correct permissions and add your keys from mailgun.

This guide is using a LAMP server, apache2 MYSql and PHP to run the site. YMMV with other web servers.

Site overview

Main page has an email signup form that signs up a user with a mailgun mailing list.

Move Conf files

Create a folder in your home directory called .mail and set the owner to apache2 user

mkdir ~/.home/.mail

Now copy the files into this directory

• emQRLminingList.sh
• rmQRLminingList.sh
• Welcome.html *This is where the pretty email lives.

Then set permissions in the folder

sudo chown www-data:www-data ~/home/.mail -R

Edit the conf files

API Key

Set the variables accordingly. We need to assign our mailGun API-key to each command in emQRLminingList and rmQRLminingList.sh

nano ~/.mail/emQRLminingList

Add API key in the format of api:key-9dj7shci7iuew78489jw9e8c8dvjw89 # random key shown

Do the same for the rmQRL script. This will remove any email from the list.

nano ~/.mail/rmQRLminingList

Mailing list setup

In the rmQRL and emQRL files you can change the cURL call to mailgun with a new mailing list. This is one we setup.

Inside the addList(){} variable you will find the call to mailgun and the mailing list. Replace with the correct list.

PHP script edits

We also need to update the PHP script to where our folder lives. Username...

nano conf/email.php

change the $output = shell_exec("bash /home/ubuntu/.mail/emQRLminingList.sh '".$email."'"); line to ft your enviornment.

Do the same for the unsubscribe script.

nano conf/unsubscribe.php

Welcome Email.

The welcome email is generated using Foundation for email. This is ran through the Inlining processor and it spits out inline css imbedded html for the email. This email is located in the ~/.mail directory and can be reworked to whatever message you would like to send.

The call for the location of the email is found in the ~/.mail/emQRLminingList.sh varriable html=$(cat Welcome.html)

Simply change the location that cat is reading from. Make sure it is alid html and be sure to test on your personal email before sending.

Apache2 setup

We need to allow PHP files to be served by default.

sudo nano /etc/apache2/mods-enabled/dir.conf

Change the following:

<IfModule mod_dir.c>
    DirectoryIndex index.html index.cgi index.pl index.php index.xhtml index.htm
</IfModule>

to

<IfModule mod_dir.c>
    DirectoryIndex index.php index.html index.cgi index.pl  index.xhtml index.htm
</IfModule>

Restart apache2

sudo systemctl restart apache2

If everything worked you can now add email to your mailing list and get a pretty responce back.

---

Pool Configuration Instructions for QRL

Dependencies

sudo apt-get install libssl-dev libboost-all-dev git screen 

NodeJS

Following this guide install nodeJS via nvm

sudo apt-get update
sudo apt-get install build-essential libssl-dev

Grab nvm and install

curl -sL https://raw.githubusercontent.com/creationix/nvm/v0.33.8/install.sh -o install_nvm.sh

bash install_nvm.sh

It will install the software into a subdirectory of your home directory at ~/.nvm. It will also add the necessary lines to your ~/.profile file to use the file.

To use log out or run

source ~/.profile

Install your version of node and use it

nvm install 0.10

nvm use 0.10
nvm alias default 0.10
nvm use default

Redis

wget http://download.redis.io/redis-stable.tar.gz
tar xvzf redis-stable.tar.gz
cd redis-stable
make
make install

Secure redis firewall

# first, dont lock your self out
sudo ufw enable openssh
# now block external redis connections
sudo ufw deny 6379
sudo ufw deny 16379
sudo ufw deny 26379

# Enable UFW
sudo ufw enable

# Check UFW
sudo ufw status

Install Redis properly

Create a directory where to store your Redis config files and your data:

sudo mkdir /etc/redis
sudo mkdir /var/redis

Copy the init script

sudo cp utils/redis_init_script /etc/init.d/redis_6379

Edit the script

sudo nano /etc/init.d/redis_6379

Make sure to modify REDISPORT accordingly to the port you are using. Both the pid file path and the configuration file name depend on the port number.

Pool Config

Clone the repo found at Github

git clone https://github.com/cyyber/node-cryptonote-pool.git qrlPool

cd qrlPool
npm update

This will take awhile to run. Grab a coffee.

Config files

Copy the config_example.json file to config.json then overview each options and change any to match your preferred setup.

---

Instructions from Cyyber

I git these fro this conversation.

Here is the node-cryptonote-pool which has been modified to work with QRL codebase

Following is the customized QRL config.json file for cryptonote-pool (make sure to update pool address) QRLpool config.json

You need atleast two nodes, to set it up correctly. One of the node will be a mining node, but will not be running grpcProxy.py. You can directly start that node using command qrl --randomizeSlaveXMSS

The another node should be a node with pool service enabled. You may use following command into the 2nd node (running pool service).

qrl wallet_gen qrl -r --host 104.237.3.185 slave_tx_generate (make sure you enter access_type 1 ) move the newly generated slaves.json into ~/.qrl/ qrl -r --host 104.237.3.185 slave_tx_generate --otsidx 1 (make sure you enter access_type 0 ) rename this file from slaves.json to payment_slaves.json and move it to ~/.qrl/

Now run your node, wait for the 2nd node to start mining. As soon as it successfully starts mining, you need to stop the node. Override config mining_enabled to False

This will stop your node from mining alone.

Restart the node.

In order to override config. you can copy the config.yml from https://github.com/theQRL/QRL

The default config.yaml is already mentioned there.

You can create the file ~/.qrl/config.yml and override any of the above mentioned settings.

Once you have done this, there is no need to keep running the 1st node that you started. You can surely shut it down and let the pool continue mining.