Let me Win! logo

Let me Win! — BCH Pool

A new crypto mining pool experience — Bitcoin Cash
coin: BCH payout: PPLNS-like (per diff_valid) backend: NOMP + Redis + custom RPC
Current round: Last closed: Quick BCH pool overview.
Active workers
0
Pool hashrate (live)
0.00 H/s
Σ workers vs pool:

How to connect (BCH)

Configure your miner with the BCH pool address and choose the right port depending on power and stability.

  • stratum+tcp://YOUR_HOST:3333 — Bitaxe and other low-power ASICs
  • stratum+tcp://YOUR_HOST:3334 — Mid-range / aggressive miners
  • stratum+tcp://YOUR_HOST:3335 — High-end / TH/s miners

Bitaxe (BM1370/BM1366) – realistic expectations

Bitaxe are “hobby” ASICs with low power consumption. GUI values (AxeOS) are instant; the pool shows averages over time and the impact of rejects/disconnections. On BCH, the order of magnitude remains the same — only network difficulty changes.

Mode Typical frequency Power Device hashrate (AxeOS) Pool hashrate (70–85%) Notes
Default (safe) ~350–400 MHz 8–12 W 8–20 GH/s 6–16 GH/s Stable and cool
Performance ~450–500 MHz 12–18 W 18–35 GH/s 13–28 GH/s Good compromise
Moderate OC ~525–575 MHz 18–25 W 30–55 GH/s 21–45 GH/s Requires decent cooling
Strong OC ⚠️ ~600–625+ MHz 22–30 W+ 45–70+ GH/s 30–50+ GH/s Risk of throttling/rejects when hot
Metrics glossary

How numbers are computed across the app.

Current round (Workers)

Per-worker hashrate (live) is computed from accepted shares over a recent time window. The backend uses diff_valid_window · 2^32 / window_seconds, aligned with the pool’s live window.

Worker efficiency = valid / (valid + invalid). diff_setting is the current difficulty target assigned to the worker.

The live pool hashrate is the sum of per-worker hashrate on the same time window. Device GUIs may show slightly higher or more volatile values because they are more “instant” and do not include rejects/disconnections.