Oracle3
Open-source trading engine and MCP server for prediction markets. Fee-aware no-arbitrage trading across related contracts, live on Kalshi, Polymarket and Solana or on paper.
SHA256 Mining Pool - Modern, Fast, Reliable
Translation pending
FinanceJavaScript · HTMLGitHub @janos-raulOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
SHA256-NOMP is mining pool software for sha256 coins
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
This is a SHA256 mining pool with solo mining support and ASICBoost with version rolling, based on Node Open Mining Portal.
This is beta software. All of the following are things that can change and break an existing SHA256-NOMP setup: functionality of any feature, structure of configuration files and structure of redis data. If you use this software in production then DO NOT pull new code straight into production usage because it can and often will break your setup and require you to tweak things like config files or redis data. Only tagged releases are considered stable.Read the full README ↗This is a SHA256 mining pool with solo mining support and ASICBoost with version rolling, based on Node Open Mining Portal.
This is beta software. All of the following are things that can change and break an existing SHA256-NOMP setup: functionality of any feature, structure of configuration files and structure of redis data. If you use this software in production then DO NOT pull new code straight into production usage because it can and often will break your setup and require you to tweak things like config files or redis data. Only tagged releases are considered stable.
Usage of this software requires abilities with sysadmin, database admin, coin daemons, and sometimes a bit of programming. Running a production pool can literally be more work than a full-time job.
m=solo password parameter (Miner Options)mining.multi_version extension for overt AsicBoost (Miner Options)Latest release: v1.6.0. Release notes for every version are in the Changelog; see Upgrading before updating a running pool.
SHA256-NOMP comes pre-configured with the following coins:
| Coin | Symbol | Algorithm | Ports | Min Confirmations | Block Time |
|---|---|---|---|---|---|
| Bitcoin | BTC | SHA256 | 50212-50216 | 101 | 10 min |
| Bitcoin Silver | BTCS | SHA256 | 50222-50227 | 201 | 5 min |
| Bitcoin Gold | BTGS | SHA256 | 50292-50296 | 101 | 10 min |
| Mytherra | MYT | SHA256 | 50232-50236 | 101 | 5 min |
| Bitcoin II | BC2 | SHA256 | 50242-50246 | 101 | 10 min |
| SHA256COIN | S256 | SHA256 | 50272-50276 | 201 | 20 min |
| ElevenSeventyFive | ESF | SHA256 | 50282-50286 | 101 | 10 min |
| VargaMesh | VMESH | SHA256 | merged only | 101 | 2 min |
All coins support:
If your pool uses SHA256-NOMP let us know and we will list your website here.
Building high-performance SHA256 mining infrastructure
.nvmrc; installation instructions)Those are legitimate requirements. If you use old versions of Node.js or Redis that may come with your system package manager then you will have problems. Follow the linked instructions to get the last stable versions.
Redis security warning: be sure firewall access to redis - an easy way is to
include bind 127.0.0.1 in your redis.conf file. Also it's a good idea to learn about and understand software that
you are using - a good place to start with redis is data persistence.
Follow the build/install instructions for your coin daemon. Your coin.conf file should end up looking something like this:
daemon=1
rpcuser=username
rpcpassword=password
rpcport=8332
For redundancy, its recommended to have at least two daemon instances running in case one drops out-of-sync or offline,
all instances will be polled for block/transaction updates and be used for submitting blocks. Creating a backup daemon
involves spawning a daemon using the -datadir=/backup command-line argument which creates a new daemon instance with
it's own config directory and coin.conf file. Learn about the daemon, how to use it and how it works if you want to be
a good pool operator. For starters be sure to read:
Clone the repository and run npm install for all the dependencies to be installed:
sudo apt-get install build-essential libsodium-dev libboost-all-dev libgmp3-dev node-gyp libssl-dev -y
sudo apt install nodejs npm -y
sudo npm install n -g
sudo n stable
sudo apt purge nodejs npm -y
git clone https://github.com/janos-raul/sha256-nomp
cd sha256-nomp
npm install
SHA256-NOMP uses three types of configuration files:
config_example.json and edit it)Every field, the fee setup and the payment modes are explained in the Configuration guide. Point each coin daemon's blocknotify at the portal so new blocks reach miners at once (see Block notifications):
blocknotify=node /home/user/sha256-nomp/scripts/cli.js blocknotify bitcoin %s
npm start
m=solo, d=, md=, tt=/rt=/vp=), mining.multi_versionBuilding high-performance SHA256 mining infrastructure
Donations for development are greatly appreciated!
bc1q0aa3k39ww33z24p3wpk72jjn32h2n5rfr85pnxbs1q8dnz4q52czdusl8hy04fw3jryj2kc3earck3y2qzhpajyfz7yvl8963rre5zqdp72pqy47ysttst0wmrReleased under the GNU General Public License v2. See the LICENSE file.