Public Pool

Public Pool is an open-source solo Bitcoin mining pool built on a NestJS/TypeScript stratum server, paired with a web UI for tracking your miners.

  • Crypto Currency
  • Network Services
  • Tools & Utilities
Public Pool is an open-source solo Bitcoin mining pool built on a NestJS/TypeScript stratum server, paired with a web UI for tracking your miners. It lets homelabbers self-host their own pool with support for custom IPs, custom ports, and direct Bitcoin node integration.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

57/100 Fair

Maintained
58last commit 169 days ago
Popular
53452 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data
Security check
70no serious findings, 20 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 13 days ago

GitHub stars
452
Open issues
58
Last commit
2026-06-05
License
GPL-3.0
Activity
stale

Checked 8 days ago - source: GitHub (benjamin-wilson/public-pool)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Get your Public access token first Create a Public access token (a secret code for API calls) and keep it safe, then use it where the API example says YOUR_ACCESS_TOKEN. It proves you are allowed to use the account, and without it every API call is rejected. source
  • Install the Public CLI with pipx or uv Install the Public CLI with pipx or uv, which are tools that install command-line apps. Without this, the public command won't be found and setup steps that rely on it will stop. source
  • Check that public --help works Run public --help after installing to confirm the CLI works. If it says command not found or shows nothing, the installer didn't put it where your terminal can find it, and later commands will fail. source
  • Unraid network setup In the Unraid template, set the External IP field to the address miners will connect to (your server IP for bridge or host networking, or the container IP for a custom network). Internal ports 3333, 3334, and 8080 can be remapped on the host; the web UI defaults to port 8080. source
  • Bare-metal deployment with PM2 To run outside a container, create a .env file from .env.example, then run npm install and npm run build, and start the server with pm2 start dist/main.js. In PM2 cluster mode, enable OS-level connection scheduling when the PM2 daemon starts. source
  • Web UI The web interface is provided by the separate public-pool-ui project; the Unraid template runs it alongside the pool server so the UI is available without extra setup. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why can't miners reach the pool when running Docker Compose?

The compose file maps the Stratum ports to 127.0.0.1 by default. Change the 3333 and 3334 entries to expose those ports on your server before miners connect.

What bitcoin.conf setting is required for the pool to use the Bitcoin RPC?

Add rpcallowip=172.16.0.0/12 to bitcoin.conf to successfully connect to the Bitcoin RPC.

What PM2 and Node.js settings are needed for cluster mode?

Use Node.js 22.12.0 or newer, and start the PM2 daemon with NODE_CLUSTER_SCHED_POLICY=none. The environment variable must be present when the daemon starts, not only in the worker configuration.

How is STRATUM_MAX_CONNECTIONS_PER_LISTENER calculated?

It is enforced per worker and Stratum port. Size it using the busiest port by multiplying worker count by the limit, for example 28 workers with the default 10000 limit allow up to 280000 connections on one port.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads