Practical overview
When it fits
Use NOMP when you need to operate or extend the server side of a mining pool and can configure its coin daemon, pool settings and storage. Choose the matching built-in or tagged engine based on the coin's mining model.
Who it is for
- Operators setting up a standalone Stratum pool for one or more proof-of-work coins.
- Developers adapting pool support to a coin or mining algorithm using the documented engine and hash-registration approaches.
Documented uses
- Run a Stratum server for miners and connect it to a coin daemon.
- Configure a pool for Bitcoin Core variants that use the standard 80-byte proof-of-work header.
- Use a supported pluggable engine for coins with different block structures, proof-of-work verification or Stratum dialects.
- Develop a separate web front end against the server API.
Requirements & limits
The public repository specifies the MIT license.
- NOMP supplies the Stratum server, not a web portal; a web front end can be built against its API.
- Some engines require build tags, and RandomX requires cgo.
- Pool setup requires daemon, address, port and Redis storage configuration.
- Quantus optional PROP/SOLO payments require a separate signing bridge, funded hot wallet and specific Redis persistence settings.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Build and configure the default NOMP server
Prepare a NOMP binary and configuration file for a default-build coin pool.
Before you start
- Go build environment
- A coin daemon configuration
- Redis storage
Steps
Build the default server with the command below.
go build ./cmd/nompCopy
config.example.jsontoconfig.json.Edit the daemon, pool address, ports and storage sections.
Select the coin engine in the configuration when using an engine coin; omit it or use
gbtfor GBT coins.
Expected outcome
A compiled server and edited configuration file ready for the documented launch stage.
Guide limitations
- This guide stops at configuration; it does not establish that a particular coin or deployment will operate successfully.
- Engines requiring build tags are not included merely by selecting them in configuration.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 8 October 2026
- Original website title
- mining-pool/not-only-mining-pool · Official homepage title · retained in its source language

