Can you build a BCHC 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.

Do you help with nodes, RPC security, and wallet handling for BCHC?

Yes. We deploy and harden the node layer (RPC allowlists, secrets, monitoring), then validate wallet and payout flows with small-value test runs before going live.

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 BCHC 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.

BitCherry (BCHC) Pool Setup — Build and Operate a SHA256 Pool

BCHC pools are easiest to run when miner rules and payout behavior are explicit. This page is written to help operators lock down RPC, tune Stratum for stability, and avoid avoidable support tickets.

On this page

Pool basics
Stack choice
What we configure
Miner connection strings
Coin notes
Launch checklist
FAQ

BCHC pool basics: make miner behavior predictable

A BCHC pool is a controlled interface between miners and the chain. Your Stratum layer must reject bad inputs cleanly, and your wallet layer must never send funds without a verified accounting record. Build with constraints first, then widen access.

Access model: Define whether BCHC users authenticate by address or account.
Worker naming: Set length/charset rules and reject invalid workers.
Payout policy: Document thresholds, fees, and credit timing clearly.
Abuse controls: Add per‑IP limits and ban logic for misbehaving miners.

BCHC engine selection: what to optimize for

For BCHC, the “best” stack is the one you can support with minimal manual work. Choose tooling that gives you clear per‑miner rejects, easy config rollout, and logs you can hand to engineers.

Yiimp setup: Standard pool UX with quick setup. See the Yiimp setup guide.
Miningcore setup: Service‑oriented layout with automation hooks. See the Miningcore setup guide.
Custom ruleset: Useful when BCHC needs custom auth, scoring, or payout exports.

Documentation tip

If you plan to list BCHC on monitoring sites or directories, keep endpoint names and port purpose consistent. Consistency reduces misconfigurations and “wrong port” support traffic.

What we implement for a BCHC pool stack

BCHC daemon security: RPC auth, firewalling, and safe service users.
Share processing: Job timing, reject logging, and performance safeguards.
Database hygiene: Retention, indexing, and backup strategy for share tables.
Settlement pipeline: Define batching, thresholds, and audit records (see payout schemes).SOLO/PPLNS/PROP guide.)
Pool front end: Dashboard plus an operator‑oriented health/status page.
Ops hardening: Monitoring and incident alerts (see security hardening).

We also add guardrails: payout pause switches, sanity checks on wallet balance, and alerting when reject rates spike. Those controls matter more than polish on day one.

BCHC miner connection examples

Publish your recommended connection string, a fallback, and a single username pattern. Include one example that matches your payout address style.

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

For troubleshooting, include a short list of common reject reasons and what miners should change in their config.

BCHC checks: wallet, addresses, and accounting

Address validation: Use the daemon’s address validation calls and test deposits/withdrawals on small amounts before launch.
Payout reconciliation: Keep records that link payout batches to wallet txids so BCHC support can answer “where is my payment?” quickly.
Indexing vs performance: If you enable transaction indexing for audits, measure disk and CPU impact and monitor it.

BCHC go‑live checklist

BCHC daemon synced and monitored; restart behavior verified.
RPC isolated to private network; credentials rotated and stored safely.
Wallet backup and restore tested; payout wallet funded safely.
Stratum configured with sane bans; reject logging enabled.
Database pruning tested; backups scheduled and verified.
Payout pipeline tested end‑to‑end; pause/resume documented.
Public docs published; worker rules and support path clear.

BCHC pool setup FAQ

How do you stop BCHC miners from abusing the pool?

We enforce connection limits, rate limits, and ban rules, and we log rejects with reasons. Operators can then block abusive patterns without guessing.

Can you build BCHC payout reporting that miners can audit?

Yes. We can expose round summaries and payout batches, and we can retain enough data to answer disputes without keeping infinite share history.

How do you decide worker name rules for BCHC?

We define a clear allowed format, then enforce it server‑side so stats stay clean and miners do not create unparseable names.

Do you help with BCHC wallet encryption and backups?

Yes. We configure encryption, define an unlock workflow, and build a backup plan that can be tested and rotated.

What makes a BCHC pool “production ready” in your view?

Stable sync, safe RPC access, tested payouts, and observability around rejects and wallet sends. Without those, public traffic becomes risky.

If you want BCHC documentation and payout flows reviewed, Contact us and we’ll suggest concrete guardrails.