Can you build a BCH pool that is solo, private, or public?

Yes. The pool type affects authentication, abuse controls, and how you present payouts and stats. We’ll recommend a launch approach based on whether you’re mining alone, with a group, or operating a public pool.

Can I run BTC and BCH pools side-by-side on the same server?

Often, yes—especially for pilots. For production or public pools, we usually separate responsibilities so one coin’s node or payout issues don’t take down the entire operation. You’ll also want separate endpoints and clear documentation per coin.

Will it work with NiceHash hashpower?

In many cases, yes. Compatibility depends on how miners connect and how your pool handles difficulty updates and session behavior. We can tune vardiff and onboarding docs for external hashpower marketplaces where appropriate.

Do you provide the pool website, dashboard, and charts?

Yes. We can deliver a full branded pool website with a miner dashboard (workers, hashrate, payments), plus status pages. If you prefer an API-first deployment, we can also integrate stats into your own UI.

What do you need from me to start a BCH pool setup?

Your pool type (solo/private/public), expected hashrate, preferred payout model, target hosting (VPS/dedicated/cloud), and whether you want a full website UI or a minimal operational deployment. From there we propose the cleanest rollout.

Bitcoin Cash (BCH) Mining Pool Setup — Build, Secure, and Operate

BCH operations often differ from “Bitcoin‑like” assumptions in address handling and policy defaults. This page focuses on the checks that keep a BCH pool safe: template validation, payout correctness, and load‑aware Stratum tuning.

On this page

BCH pool basics
Choose your stack: Yiimp vs Miningcore
What we configure
Miner connection strings
Coin-specific notes for BCH
Launch checklist
FAQ

BCH pool operations: what to validate before you scale

A BCH pool must handle both hashpower and transaction policy. Your node provides templates, Stratum distributes work, and payouts require correct address handling and clear credit timing. Test the full loop in staging, including a real payout batch.

Node choice: Select a BCH node build and stay consistent across upgrades.
Address format: Ensure payout tooling accepts the address formats you publish.
Throughput planning: Design for higher share volume and larger mempool effects.
Policy visibility: Log template and submit errors so policy changes are visible.

BCH stack selection: when Yiimp or Miningcore fits

BCH pools are usually operated like BTC pools, but the best stack is the one you can observe and control. Choose tooling that gives you clear reject reasons and safe payout automation.

Yiimp for BCH: Good for standard pool UX and fast setup. See the Yiimp setup guide.
Miningcore for BCH: Good for service separation and APIs. See the Miningcore setup guide.
Custom extensions: Useful when you need BCH‑specific payout or policy hooks.

Address handling

Most BCH ecosystems use CashAddr. If you accept multiple address styles, normalize and validate them consistently in the payout pipeline. Always test with validateaddress/getaddressinfo before you open withdrawals.

What we configure for BCH pool reliability

BCH node ops: Install, keep peers healthy, and lock RPC to private hosts.
Template + submit path: Observe getblocktemplate, block submission, and failure modes.
Stratum scaling: VarDiff targets, connection caps, and gateway options for load.
Payout correctness: Scheme selection and miner expectations (see payout schemes).how to choose SOLO vs PPLNS vs PROP.)
UI and status: Miner dashboards plus operator health indicators.
Security and resilience: Hardening and maintenance routines (see ).

We also help operators document BCH specifics: address formats, credit timing, and how the pool reacts to orphans. Clear docs reduce support overhead.

BCH miner connection strings (examples)

For BCH miners, publish a simple endpoint list and the exact username format you require. Include an example payout address in the format you support.

stratum+tcp://POOL-DOMAIN:3333
stratum+ssl://POOL-DOMAIN:3443

If you provide TLS, show the TLS endpoint and note any firmware limitations that prevent SSL on older ASICs.

BCH‑specific implementation notes for operators

CashAddr in payouts: Decide whether you accept legacy and CashAddr inputs, then convert/validate consistently end‑to‑end.
Policy switches: BCH nodes can have policy toggles; record your chosen settings and monitor template errors after upgrades.
Indexing for audits: If you need deep reconciliation, enable the node indexing features you rely on and size disk accordingly.
Large‑block mindset: Keep an eye on DB and network paths; big blocks and bursts of activity can surface as latency and stale shares.

BCH production launch checklist

BCH node synced; implementation/version recorded; peers monitored.
RPC restricted; auth enabled; access audited periodically.
Wallet payout address handling tested with small transactions.
Stratum tuned for share load; VarDiff and bans validated.
Database sized; pruning and backups confirmed under load.
Payout pipeline tested end‑to‑end; orphan reversal verified.
Docs published for miners: endpoints, address format, support path.

BCH pool FAQ (technical)

Do you support CashAddr payouts for BCH pools?

Yes. We validate addresses using daemon calls, normalize formats where needed, and test real sends on small amounts before enabling automation.

Which BCH node should I run for pool operation?

Use a well‑maintained BCH node implementation that your team can patch and monitor. Whatever you choose, pin versions and stage upgrades with template tests.

How do you keep BCH pools stable during transaction spikes?

We tune job timing and gateways, watch stale rates, and ensure the database and network paths can absorb bursts without falling behind.

Can you run BCH alongside BTC/BCH forks in one environment?

Yes, with separate daemons and isolated wallet keys per coin. Shared monitoring and gateways can be reused when quotas are enforced.

What is your recommended BCH pre‑launch test set?

Template fetch, controlled mining, block submission, orphan simulation where possible, and a real payout batch to test address handling and fees.

If you need BCH address and policy reviewed for a pool launch, Contact us and we’ll map it to a concrete test plan.