Bitcoin Forum
January 11, 2026, 09:09:44 AM *
News: Due to a wallet-migration bug, you should not upgrade Bitcoin Core. But if you already did, there's no need to downgrade.
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [BTC][BCH][DGB] BitcoinCashPool.org — C/C++ based, fastest [SHA-256] mining pool  (Read 19 times)
88nE6w2xfri6izL1Xx239ELXb (OP)
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile WWW
January 10, 2026, 08:43:48 PM
Last edit: January 10, 2026, 09:19:21 PM by 88nE6w2xfri6izL1Xx239ELXb
 #1

[Bitcoin][BCH][DGB] BitcoinCashPool.org — C/C++ based, fastest [SHA-256] mining pool. New Stratum + ZeroMQ.

Welcome to BitcoinCashPool.org
An anonymous, multithreaded, non-blocking, UNIX-socket-oriented, scalable SHA-256 mining pool written in pure C/C++ with a custom ZeroMQ library.

[Architecture] BitcoinCashPool.org is not a fork of legacy open-source solutions. It is a unique, high-performance engine written from scratch in C/C++. We rejected heavy interpreted languages (Python, NodeJS, Java, Go, C#) in favor of direct memory management and CPU resource control.
To claim the title of the fastest pool on the market, we implemented two fundamental technologies used in High-Frequency Trading (HFT):
   •   UNIX Domain Sockets: Unlike classic pools that use network sockets (TCP/IP) for inter-process communication (Stratum ↔ DB ↔ Payouts) even on the same machine, we use UNIX sockets.
   •   Direct Transfer: Data bypasses the network stack, going directly through the OS Kernel.
   •   No Overhead: We eliminated packet encapsulation/decapsulation, checksums, and routing overhead.
   •   Security & Speed: This makes internal pool communication lightning-fast and secure at the filesystem level.
   •   ZeroMQ (ØMQ): An asynchronous messaging library acting as the pool's backbone.
   •   Concurrency: Handles hundreds of thousands of connections and millions of shares in parallel without blocking main processes.
   •   The Philosophy of Zero: Zero Broker, Zero Latency, Zero Administration.
   •   Scalability: Thanks to Asynchronous I/O, the pool efficiently utilizes all CPU cores.
   •   Resilience: Even during hashrate spikes or DDoS attacks, your share is accepted and processed instantly.
The Bottom Line: The combination of C/C++, UNIX sockets, and ZeroMQ saves precious milliseconds at every stage. In SOLO mining, where a fraction of a second separates a Valid Block from an Orphan, this architecture gives you a mathematical advantage.
[Registration] No registration required. The pool is fully anonymous and stores no client data. All logs are encrypted and wiped after 48 hours. We only keep a list of solved/rejected blocks for stats and debugging.
[Connection] We use a reworked TCP Stratum protocol compatible with all modern ASICs.
Dedicated ports for each coin: DGB=3333, BCH=4444, BTC=5555. Auto-VarDiff is enabled on all ports.
   •   URL: The pool address with the specific port.
   •   USER: Your wallet address for payouts. Double-check this! If the address checksum fails validation by the node, the pool cannot write it into the coinbase transaction, and the reward will be lost. Copy-paste it; do not type manually.
   •   PASS: x (Password does not affect mining or difficulty).
   •   Note: Difficulty is assigned individually. Do not try to set it manually via the password field.

DGB
Code:
URL: stratum+tcp://eu.bitcoincashpool.org:3333
USER: dgb1walletaddress.worker
PASS: x

BCH
Code:
URL: stratum+tcp://eu.bitcoincashpool.org:4444
USER: 1BitcoinCashAddress.worker
PASS: x

BTC
Code:
URL: stratum+tcp://eu.bitcoincashpool.org:5555
USER: 1BitcoinWalletAddress.worker
PASS: x

[Address Types] We support all standard address formats.
   •   DGB: “dgb1…”, “D...”, “S...”
   •   BCH: “q...”, “p…”, “bitcoincash:…”, “1…”, “3…”
   •   BTC: “bc1…”, “1…”, “3…”
[Wallets] Technically, payouts work with any valid address. However, not all exchanges or web wallets can correctly credit a Coinbase Transaction (generated from a block). We strongly recommend using a local wallet where you control the private keys (Bitcoin Core, Electron Cash, etc.). Do not mine to online wallets or obscure exchanges that may not support coinbase deposits.
We have tested and verified the following:
   •   DGB: DigiByte Core, TrustWallet, Exodus, Binance Exchange.
   •   BCH: Bitcoin Cash Node, Electron Cash, Exodus, MEXC Exchange.
   •   BTC: Bitcoin Core, Bitcoin Knots, Electrum, Exodus, MEXC Exchange.
Note regarding MEXC: We contacted their tech department. Their parsers are now configured to credit mining deposits after 8 confirmations. Use promo code mexc-bitcoincash for a permanent fee discount.
[Supported Hardware] Tested with: Antminer, WhatsMiner, Avalon, Innosilicon, SealMiner, TeraFlux, BitAxe, NerdAxe, NerdQaxe, NerdQaxe++, NerdOctaxe+.
   •   NOT Supported: WhatsMiner M30 with old firmware, and any NerdMiner/USB stick with hashrate below 50 Gh/s.
   •   Supported Firmwares: Vnish, Braiins OS, Gminer, HiveonOS, and stock.
[Protocols] Supports AsicBoost, Proxying, extra_nonce, and vardiff.
[Merged Mining] Not supported. You only get rewards for the coin you are mining. However, you can split your workers across different coins and ports. The pools are logically and physically separated.
[Rentals] Works seamlessly with MiningRigRentals and Nicehash.
[Statistics] Track your rigs via the “Worker Stats” field on the website. Enter your wallet address and hit “Search”.
   •   Workers: Total active connections.
   •   Total Shares: Valid shares submitted since connection.
   •   Best Share (current): Highest difficulty share found in the current block round.
   •   Best Ever: Highest difficulty share ever found by your workers. (Just for bragging rights, has no economic meaning).
   •   Last Share Time: Timestamp of the last valid submission.
   •   Address Hashrate History: 48-hour interactive graph.
   •   Active Workers Details: Granular stats per worker (1m, 5m, 1h, 1d, 7d hashrate).
[Difficulty] There are two types: Share Difficulty and Block Difficulty. Minimum share difficulty is set to 2048. The pool uses VarDiff to adjust your difficulty dynamically so you send ~1 share per second.
   •   Hashrate is a myth: The pool doesn't "know" your hashrate. It calculates it based on the number and difficulty of shares submitted over time.
   •   Share Difficulty: Only needed to prove the worker is alive and to draw the graph. It does not affect finding a block.
   •   Block Difficulty: A dynamic network parameter (1 block for DGB, ~1-6 blocks for BCH, 2016 blocks for BTC). It is the same for everyone in the world.
How winning works:
   1   Share > Share Diff & Share < Block Diff: Accepted as a valid share. Updates your stats.
   2   Share > Block Diff: BINGO. The pool propagates the solution to the network. You get the reward.
[Accepted & Rejected Shares] Every submission passes a strict validator.
   •   Accepted: Valid work. Updates stats. If diff > network diff -> Block found.
   •   Rejected: Useless work. Not counted in hashrate.
   •   Stale: You solved a block that the network already found. Often due to latency/ping. Normal range: < 1.00%.
   •   Duplicate: Worker sent the same share twice (firmware bug).
   •   Low Difficulty: Share difficulty lower than requested (chip error or overclocker issue).
For clarity, the path of any share from the worker to the pool can be represented as the following graph diagram:


Code:
Worker Sends a share..
      │
      ▼
[Pool Validator]
      │
      ├─► REJECTED ──┐
      │              │
      │              ├─► Stale (Obsolete): Too late, the network is already on the new block.
      │              ├─► Duplicate: Resubmitting the same solution.
      │              └─► Low Diff: Difficulty below minimum of 2048 (chip error).
      │
      └─► ACCEPTED ─────┐
                        │
                        ▼
             [Difficulty Comparison]
                        │
                        ├─► Share Difficulty < Block Difficulty
                        │     │
                        │     └─► OK: Hashrate graph update, Best Share.
                        │               (No reward, just statistics).
                        │
                        └─► Share Difficulty > Block Difficulty
                              │
                              └─► BLOCK CANDIDATE: Instant sending to Node!
                                        │
                                        ▼
                                [Network Response]
                                        │
                                        ├─► ACCEPTED! (First seen):  BLOCK ACCEPTED (The reward goes to the address).
                                        └─► REJECTED (Too late): ORPHAN (No Reward, Inconclusive).
                                                  


[Effort & Luck] Effort is the work done relative to network difficulty. Luck is the inverse of Effort.
   •   Effort < 100%: You found a block faster than expected. (Lucky!)
   •   Effort > 100%: You are working longer than expected. (Unlucky...)
   •   No Memory: High current effort (e.g., 400%) does not mean a block is "due". Every hash is an independent event. The chance to find a block at 0% effort and 400% effort is mathematically identical.
[Time to Block]
   •   Personal: Calculated as Difficulty * 2^32 / Hashrate. This is a mathematical average (Expected Value), not a countdown timer. You might find a block in 10 minutes or 3 days.
   •   Pool Stats ("Time to Block"): Estimates how often the entire pool finds a block based on total hashrate. E.g., "9h" means the pool finds a block roughly every 9 hours.
[Reward] Direct Coinbase Transaction. https://learnmeabitcoin.com/technical/mining/coinbase-transaction/
   •   The pool does not hold your funds.
   •   The pool does not send transactions.
   •   The network generates coins directly into your wallet.
   •   Reward: Block subsidy + Tx fees from the mempool.
   •   No Minimum Payout: You get the full block reward instantly.
 You can track the latest mempool transactions and fees here: https://mempool.jhoenicke.de/#BTC,24h,fee or https://mempool.space/mempool-block/0
[Maturity] Since these are freshly minted coins, the network locks them to prevent reorg attacks.
   •   Status: "Immature".
   •   Unlock Time: 100 confirmations (~1000 mins for BTC/BCH, ~25 mins for DGB). This is a blockchain (https://learnmeabitcoin.com/technical/mining/coinbase-transaction/#coinbase-maturity) rule, not a pool rule.
[Block Status]
   •   ACCEPTED: Valid block, added to the blockchain. Reward incoming.
   •   ORPHAN: Valid work, but someone propagated a block faster. No reward. Happens due to network latency.
[Fee] 1.1%. Taken only after a block is found and confirmed. Covers node operation and development. We do not touch your coins; the fee is part of the coinbase generation parameters.
[Team] BitcoinCashPool.org is a non-profit project founded by volunteers from the P2Pool Foundation with 14+ years of industry experience. We follow the "True Bitcoin" philosophy described by Satoshi in 2008. We didn't hire a designer from Apple to make flashy animations. We focused on pure math and C++ code. In mining, only the cryptographic result matters, not the UI wrapper. Our goal was to build a utility tool 100x faster than centralized chinese alternatives.
[Support] No bots. No fax. No "hotlines". No emails. No useless ticket systems. Direct engineer-to-miner communication.
   •   Telegram: Real-time chat with devs and community: https://t.me/bitcoincashpool
   •   BitcoinTalk: Official thread (this topic).
We value smart questions and are always happy to share knowledge about fair mining.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!