Universal Currency (UNIT) SHA256 Mining Pool Setup — Engineering-First Checklist
UNIT pools fail for predictable reasons: the node gets out of sync, wallet RPC is exposed, or accounting can’t be reproduced after a restart. This page is written to prevent those operator mistakes while keeping the deployment understandable.
UNIT pool launch: the moving parts you must own
A UNIT pool is not just Stratum. You are operating a daemon that must stay in consensus, a share pipeline that must be deterministic, and a payout process that must be explainable to miners. Treat the pool as an always-on service with clear state boundaries (node, database, portal, wallet) so you can debug issues without guesswork.
- Pool mode: decide whether UNIT runs as a private pool (restricted access), a solo pool, or a public pool with onboarding and abuse controls.
- Accounting reproducibility: make sure rounds, shares, and payments can be recomputed from stored data after restarts or failovers.
- Node indexing: verify whether your UI/accounting requires txindex or other indexes; enabling them early avoids painful reindex windows later.
- Miner experience: define a stable share difficulty plan (varDiff = variable difficulty) and publish a short troubleshooting guide for common ASIC firmware.
Selecting a UNIT pool platform based on operational control
UNIT can run on either a classic Yiimp-style stack or a Miningcore-driven stack. The “right” answer depends on how much you value rapid UI delivery versus API control, and how comfortable you are maintaining the code path over time.
- Yiimp-based: good for a familiar portal and fast onboarding; start with the Yiimp setup reference and then add UNIT-specific wallet and indexing checks.
- Miningcore: a clean API surface and a modern service layout; see the Miningcore deployment guide if you want that operational model.
- Custom stack: best when UNIT needs bespoke explorer integration, custom payout rules, or multi-tenant operator tooling.
If you change indexing options after launch (for example enabling txindex), schedule downtime and document it. Reindex/rescan operations can look like “pool is broken” to miners unless you communicate clearly.
Build scope for UNIT nodes, indexing, Stratum, and payouts
- UNIT node services: install/build, peer reachability, disk sizing, and restart-safe service units with explicit log locations.
- RPC hardening: bind RPC to private interfaces, enforce allowlists, and keep credentials out of the web root and source control.
- Stratum configuration: port layout, vardiff tuning, connection limits, and miner compatibility tests across multiple ASIC firmwares.
- Payout pipeline: confirmation policy, batching, and safety checks. Use the payout schemes guide to align SOLO/PPLNS/PROP with your operational goals.
- Portal + status pages: UNIT landing page, account views, worker stats, and health indicators that reduce support load.
- Security and recovery: backup schedules, restore drills, and hardening steps from the pool security guide.
We also document the “reindex / rescan / restart” playbook for UNIT so you have a repeatable response when the daemon falls behind, the wallet needs a rescan, or you must roll a node upgrade under load.
UNIT miner connection examples and worker naming
For UNIT, keep connection documentation short and explicit: endpoints, whether TLS is offered, and how to format usernames (typically a UNIT payout address plus an optional worker suffix). Consistent conventions reduce invalid share and payout failures.
stratum+tcp://POOL-DOMAIN:3333
stratum+ssl://POOL-DOMAIN:3443If you accept rented hashpower, publish separate ports and onboarding notes so marketplace-style clients don’t disrupt farm miners.
UNIT-specific checks for indexing, fees, and rescans
- Index planning: determine up front whether your accounting/UI needs txindex or similar indexes, then enable and validate them before production traffic.
- Mempool and fees: review daemon fee policy and relay behavior so payout transactions confirm reliably. Document how you will react if fee pressure rises.
- Rescan readiness: practice wallet rescans and database reconciliation steps so you can recover cleanly after a crash or chain reorg event.
UNIT go-live tasks for pool operators
- UNIT node(s) are in full sync, with logs and metrics proving steady consensus and peer connectivity.
- RPC endpoints are private-only and tested with least-privilege credentials for pool tasks.
- Indexes required by your accounting/UI are enabled and validated (and reindex time is understood).
- Stratum ports are exercised with different miners; connection limits and ban rules behave as expected.
- Shares → rounds → payouts are verified with a controlled miner and a small live payout test.
- Database backups and restore procedures are proven, not assumed.
- Operator documentation is published: connection help, payout timing, confirmations, and a maintenance/status page.
UNIT pool FAQ for build and operations
Do I need txindex or address indexes for UNIT pool accounting?
It depends on your portal features and how you reconcile payouts. Check what your pool software queries (daemon RPC calls and explorer lookups) and enable only the indexes you actually need—then validate with a full payout cycle.
How do I handle UNIT wallet rescans without corrupting payouts?
Freeze automated payouts, snapshot database state, run the rescan/reindex steps you documented, and then reconcile balances against recorded payouts before re-enabling batching.
Can you migrate an existing UNIT pool to new servers?
Yes. We treat migration as a data integrity project: copy databases with verification, preserve configs and secrets, and run a staged cutover with miners pointed at the new Stratum endpoints.
How should I set confirmations for UNIT payouts?
Use the daemon’s consensus rules as the source of truth and pick a policy that protects against reorg risk. Document the policy publicly and enforce it in the payout scheduler.
Can UNIT Stratum run over TLS?
Yes. Many pools publish both plain TCP and TLS endpoints. The key is to terminate TLS in a way that does not hide miner IPs you rely on for abuse controls.
Need a UNIT pool built with indexing and recovery playbooks included? Contact the team to scope the deployment.