xmrwasp

XMR WASP

XMR WASP is a Websocket And Stratum Proxy for Monero (XMR) miners. It accepts connections from miners over both websocket and plain TCP sockets using the monero stratum protocol. Written in Go and partly inspired by XMRig-Proxy.

Goals

• Enable browser mining in a responsible way
• Educate site owners and users about browser mining through the example site which uses this project as a proxy.

Features

• Easy to use - just configure and execute the binary.
• No dependencies.
• Configurable with either OS Environment or JSON file.
• Low system overhead per connection.
• Accepts most miners, including Browser Miners!
• Reduce Pool Load by using one connection for many miners.
• Release builds for many platforms (not all thoroughly tested)

Installation

Download

Binary releases are available for most platforms

Move to a directory in your system PATH if desired.

Install with Go Toolchain

As long as you don't pass the -d flag, go get will install the package as well.

go get github.com/trey-jones/xmrwasp

Get the Docker Image

docker pull treyjones/xmrwasp

Usage

Binary Releases

To use XMR WASP just execute the binary as in the examples (unix):

Using a JSON config file

xmrwasp -c example/example.config.json &

Setting Environment at Runtime

XMRWASP_URL='xmrpool.eu:3333' \
XMRWASP_LOGIN='47sfBPDL9qbDuF5stdrE8C6gVQXf15SeTN4BNxBZ3Ahs6LTayo2Kia2YES7MeN5FU7MKUrWAYPhmeFUYQ3v4JBAvKSPjigi.250+env_example' \
XMRWASP_PASSWORD='x' \
xmrwasp

To run in the background and write to a log file instead of stdout:

XMRWASP_URL='xmrpool.eu:3333' \
XMRWASP_LOGIN='47sfBPDL9qbDuF5stdrE8C6gVQXf15SeTN4BNxBZ3Ahs6LTayo2Kia2YES7MeN5FU7MKUrWAYPhmeFUYQ3v4JBAvKSPjigi.250+env_example' \
XMRWASP_PASSWORD='x' \
XMRWASP_LOG='xmrwasp.log' \
xmrwasp &
tail -f xmrwasp.log

Docker

Environment Config

docker run --rm -e 'XMRWASP_URL=xmrpool.eu:3333' \
    -e 'XMRWASP_LOGIN=47sfBPDL9qbDuF5stdrE8C6gVQXf15SeTN4BNxBZ3Ahs6LTayo2Kia2YES7MeN5FU7MKUrWAYPhmeFUYQ3v4JBAvKSPjigi.250+env_example' \
    -e 'XMRWASP_PASSWORD=x' \
    treyjones/xmrwasp

File Config

docker run --rm -v $(pwd)/example.config.json:/config/config.json \
    treyjones/xmrwasp -c config.json

Run the example with docker-compose

cd example
docker-compose up

Configuration

Configuration can be done via system environment variables, or by invoking xmrwasp with the -c flag, and passing a path to a JSON config file.

Required Configuration Options

All Configuration Options

Compatibility

The example is using CryptoNoter for the browser miner. Since the Monero miner in that library is ripped straight from CoinHive, the latter can be used as well. If there are other browser miners that you want compatibility for, you can make an issue here, and I'll do my best to make it work.

Same goes for other mining software. Most any miner that can connect to a stratum mining pool should be able to connect to this proxy, excluding Claymore, for now. This proxy can also connect to another instance of itself, which is how donate works. If you have compatibility problems, let me know!

I also aim to have excellent compatibility with mining pools. I would love to know if you find a pool that isn't working with this proxy. If you are a pool operator I would love to have a conversation about how I can better handle errors, etc. Pool operators possibly have a lot to gain from their users connecting through a proxy since it reduces the number of connections that must be maintained by the pool (by a factor of up to 1000 in this case).

A Word About Responsibility

One of the primary features of this piece of software has to do with enabling Monero mining in the browser. The author of this project believes that browser mining can be a win-win. Even a win-win-win (users, website owners, and the blockchain). The users can win by not being subjected to ads, if browser mining proves to be lucrative enough for a site owner to stay afloat. But they can also lose, and lose badly, if the site owner doesn't excercise some restraint over the opportunity. Here are some things that you, as a site owner, probably know, but might be tempted to forget for the sake of maybe mining a few extra Moneroj:

• Don't mine on mobile devices, lest you destroy their battery and their ability to browse your site.
• Don't mine without telling your users that you are doing it.
• Give your users a say in whether they participate in mining, and how much.
• Throttling the browser miner is a good idea for everyone.

Roadmap

• Max connection lifetime and eventual spindown
• Web Interface exposing current status and history
• Multiple pool configs for fallback
• Performance Improvements: Faster release of memory on broken connections
• User Feedback?
• TLS support for stratum+tcp listeners
• Just tons of little things that could be better
• Linux package manager repositories?

Support This Project

The project has a donation mechanism built in. By default it donates for 1 minute and 12 seconds (donate=2) of every hour. It does this without breaking your pool connection. This is configurable down to 36 seconds (donate=1) per hour. Or higher if you feel generous. Saavy users of course may find that they can disable the donation mechanism. If you do so, consider a one time donation.

• Monero: 47sfBPDL9qbDuF5stdrE8C6gVQXf15SeTN4BNxBZ3Ahs6LTayo2Kia2YES7MeN5FU7MKUrWAYPhmeFUYQ3v4JBAvKSPjigi
• Bitcoin: 1NwemnZSLhJLnNUbzXvER6yNX55pv9tAcv

Support Through Development

I will gladly take a look at any pull requests that come my way. In particular if you wanted to take a stab at any of the following types of items that don't align very well with my skillset and interests:

• Making the example app look nice
• Building (or mocking up) a nice looking dashboard for a future web interface feature
• Making a badass logo/emblem to represent the project.
• Enhancing the appearance of the logging output.
• Testing on Windows