Mining Pools & Proxies

Node-cryptonote-poolOpen-Source Mining Pool Software for Windows

Review of node-cryptonote-pool for Windows: features, setup with Redis, fees, safety notes on the unmaintained code, and alternatives.

Free Open source Windows: Yes Updated 9 Mar 2021
9 min read Last update 9 Mar 2021 github.com/zone117x/node-cryptonote-pool

node-cryptonote-pool is open-source server software for running a mining pool for CryptoNote-based coins. It is aimed at operators who want to host a pool for their miners, not at people who only want to mine alone. It is one of the original pool applications written for cryptonotes, and it includes a web front-end and stores its data in Redis.

Before you deploy anything, know the project's status. Its repository states that it is no longer maintained, and the last code update was on March 9, 2021. Maintainers accept only critical or high-quality pull requests that have been well tested. That makes it a risky base for a new production pool without an audit, but it remains a useful reference for learning how pool servers handle shares, difficulty and payouts.

02

What Is a CryptoNote Mining Pool?

A mining pool combines the computing power of many miners so they can share block rewards. Each miner submits shares, which are partial proofs of work, and the pool credits them according to the difficulty they reached. Pools exist because solo mining can take a long time to produce a block, while pooled miners receive smaller but more regular payouts.

CryptoNote is a family of privacy-focused coins, and Monero is its best-known member. Pool software for these coins has to handle their specific block and transaction rules. node-cryptonote-pool was written for that purpose, so its concepts map closely to how these networks behave.

Operators who run a pool sit between the network and their miners. They must keep the server fast, reject bad shares, pay miners correctly and keep records. Understanding these responsibilities is the best place to start before you install any pool software.

03

Who Should Consider Running a Pool Like This?

Software like this suits developers who want to learn how pool servers work. Reading the code, changing the configuration and watching the logs teaches more about shares, difficulty and payouts than any article can. It is also useful for a small community that wants its own pool for a single coin and is prepared to manage the server.

It is less suitable for anyone who needs supported production software with regular security updates. The project is no longer maintained, so bugs and vulnerabilities may remain unfixed. Operators who go live with real miner funds should plan for code review, monitoring and a clear process for handling payouts.

Miners who only want to earn rewards are usually better served by a managed pool. Running your own pool means taking on responsibility for uptime, fee policy and accurate accounting, and that work grows quickly once more miners join.

04

How Pool Fees Work in the Default Configuration

The sample configuration sets a pool fee of 1.8 percent. A comment in the same file describes a total fee of 2 percent, which includes a developer fee alongside the pool fee. Those numbers come from the example settings, so a live pool can use different values.

Fees matter because they determine how much of each block reward reaches miners. An operator who keeps a fee should state it clearly to miners and document how it is applied. Hidden or changing fees erode trust quickly in a small pool community.

Before launch, review the fee settings line by line, confirm the developer fee behavior in the code, and test payouts on a small scale. Clear fee policies protect both the operator and the people mining in the pool.

05

Key features

Stratum-Style TCP Protocol

Instead of the older HTTP approach, the pool pushes new mining jobs to miners over a persistent TCP connection, in a style similar to stratum. The project says this yields a higher hash rate, lower network and CPU load on the server, and fewer orphan blocks. Miners spend less time waiting for fresh work.

IP Banning

Addresses that flood the pool with low-difficulty shares can be banned. This keeps attackers from consuming validation time with work that will never be worth paying. Banning works best as one layer of defense alongside firewall rules on your server.

Socket Flooding Detection

The server watches for connection patterns that look like a flood of socket requests. Catching these early helps the pool stay responsive for honest miners when someone tries to overload it.

Payment Processing

The software tracks each miner's shares and calculates balances, then sends payouts. Because the logic lives inside your pool, you need to understand how balances move before you open the pool to real miners.

Split Transactions

When a payout batch would exceed the maximum transaction size, the software divides it into several smaller transactions. This keeps payouts valid on networks that cap transaction size.

Minimum Payment Threshold

A miner's balance is paid out only after it reaches a configured minimum. Small balances build up until they cross that line, which reduces the number of tiny payments that would clutter the chain.

Minimum Denomination

Payment amounts can be truncated to a minimum denomination, reducing their precision. Simpler amounts make block transactions smaller and less complex, which is useful when you pay many miners in one run.

Detailed Logging

The pool writes detailed logs of share submissions, connections and payment runs. When a miner reports rejected shares or a payout looks wrong, these logs are the first place to check.

Multiple Ports With Individual Difficulty

You can run several ports, and each one can have its own difficulty. A low-difficulty port suits modest hardware, while a higher one suits powerful rigs, so one pool can serve very different miners.

Variable Difficulty and Share Limiter

Variable difficulty adjusts how hard shares are for each miner based on how quickly that miner submits them. The share limiter keeps submission traffic manageable, and slower devices get work they can finish.

Share Trust Algorithm

The share trust mechanism lowers CPU load by checking fewer shares with full hashing. Miners with a history of valid shares are trusted more, while the pool still validates others, which saves server resources without ignoring suspicious behavior.
06

Supported coins

The documentation mentions Bitcoin (BTC) and Monero (XMR). The software is built around the CryptoNote family of coins, so other coins can work only after careful configuration. Altcoins that change the minimum number of coin units require updating several config values, so test any new coin thoroughly before going live.

07

How to install Node-cryptonote-pool on Windows

  1. 1

    Get the Software From an Official Source

    Download only from the official website or the project's GitHub page at github.com/zone117x/node-cryptonote-pool, using the Releases section where available. Avoid mirrors, file-sharing sites and links from forums or chat groups.

  2. 2

    Verify the Download

    Compare the file's SHA-256 checksum with the value published by the project, or check its signature if one is provided. If the hash does not match, delete the file and download it again from the official source.

  3. 3

    Install Redis and Prepare the Configuration

    Install a Redis server and confirm it starts before you launch the pool, because the software stores its data there. Open the configuration file and set the coin parameters, ports, difficulty values and payment options.

  4. Start the Pool and Test It

    Launch the server and connect a test miner to one of your ports. Check that shares appear in the logs and that the statistics update correctly. Only open the pool to outside miners after the test run looks clean.

08

System requirements

  • A running Redis server that the pool can reach
  • Firewall rules that allow miners to connect to the TCP ports you configure
09

How to use Node-cryptonote-pool

Most of the work with node-cryptonote-pool happens in the configuration file and the logs. Set the basics first, then test everything with a single miner before you accept real hashpower.

  1. Open the configuration file and set the coin parameters, including the minimum coin unit for your coin.
  2. Define each port and give it its own difficulty, such as a low-difficulty port for modest hardware.
  3. Set the minimum difficulty (minDiff) so the lowest accepted share difficulty is clear.
  4. Configure the minimum payment threshold and the minimum denomination for payouts.
  5. Start Redis and confirm that it accepts connections.
  6. Launch the pool server and point a test miner at one of your ports.
  7. Watch the logs for accepted shares, rejected shares and connection events.
  8. Run a small test payout on a test balance and verify the amounts before accepting real miners.
10

Pros & cons

Pros
  • Open source under GPL-2.0, so the code can be read, audited and modified
  • Covers core pool needs, including payments, logging and difficulty control
  • Multiple ports, each with its own difficulty, serve different hardware
  • Built-in measures against low-difficulty share attacks and socket flooding
  • Useful for learning how pool servers actually work
Cons
  • The project is no longer maintained, and the last code update was March 9, 2021
  • Maintainers accept only critical or well-tested pull requests
  • Operators need working knowledge of Redis and pool configuration
  • Documentation centers on Bitcoin and Monero, so other coins need extra work
  • Altcoins with different minimum units require reconfiguring several settings
11

Is Node-cryptonote-pool safe?

node-cryptonote-pool is no longer maintained, so treat it as a risk when handling real miner payouts. Download only from the official website or the project's GitHub page, and verify the SHA-256 checksum or signature before you install it. Never enter a seed phrase or wallet recovery phrase on any third-party website, including sites offering pool setup help. Antivirus tools sometimes flag mining-related software, so add a narrow exclusion for the specific folder if needed, but never disable your protection entirely. Review payment settings carefully, test with small amounts, and check the latest version on the official website before going live.

  • Official source only. Download from github.com/zone117x/node-cryptonote-pool. Ignore ads and lookalike domains.
  • Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
  • Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
12

Alternatives

Compared with cryptonote-universal-pool, which is an improved version built on node-cryptonote-pool and adds MySQL support, the original is simpler but older. MiningCore is a broader pool-building framework that supports more coins, including Ergo, so it suits operators who plan several pools. P2Pool takes a decentralized approach for Monero, where miners share work peer to peer rather than depending on one operator. XMRig Proxy is different again: it sits between miners and a pool to manage farms, rather than running a full pool itself. Choose based on the coin, your need for a maintained codebase and your operational goals.

13

Specifications

Price
Free
Type
Open source
License
gpl-2.0
Latest version
—
Last update
9 Mar 2021
Windows support
Yes (Windows build or installer)
Source code
github.com/zone117x/node-cryptonote-pool
14

Frequently asked questions

It can be installed safely if you download it from the official source and verify its checksum, but the project is no longer maintained, which adds risk. Test it on a small scale before handling real miner payouts. Review the code and settings carefully, and never enter a seed phrase on a third-party website.

Yes, the project offers a Windows build or installer. Redis must still run alongside the pool, so you need to set it up before launching the server. Check your firewall settings so miners can reach the ports you configure.

Start by editing the configuration file to set your coin parameters, ports, difficulty and payment options. Then start Redis, launch the pool server and connect a test miner. Watch the logs for accepted shares before opening the pool to others.

No, the project is not actively maintained. Its last code update was on March 9, 2021, and maintainers accept only critical or high-quality pull requests that have been well tested. Expect no regular security or feature updates when you choose it.

The documentation mentions Bitcoin (BTC) and Monero (XMR). Other CryptoNote-based coins may work with configuration changes, but coins with different minimum coin units require updating several settings. Test any new coin thoroughly before going live.

The sample configuration sets a pool fee of 1.8 percent, and a comment in the file describes a total fee of 2 percent including a developer fee. These are example values, and an operator can change them. Be transparent with miners about whatever fee you choose.

Yes, the pool uses Redis to store its data. Install and start Redis before launching the pool, and confirm the connection in your configuration. Without a running Redis server, the pool cannot store shares or balances.

Options include cryptonote-universal-pool, which builds on the same codebase with MySQL support, and MiningCore, which is a broader framework for several coins. Choose an alternative that is actively maintained if you need long-term support for a production pool.

15

Verdict

node-cryptonote-pool is best for developers, students and small technical teams who want to understand how a CryptoNote pool server works. Its features are well suited to learning, including variable difficulty, multiple ports, payment controls and detailed logs. It is not a good fit for anyone who needs actively maintained production software, because the last code update was in 2021. If you use it, test thoroughly, keep your fee policy transparent and check the latest version on the official website before going live.

Download now