MixTrust (MXT) SHA256/SHA256d Mining Pool Setup — Operator Checklist
This guide is written for operators standing up a MixTrust (MXT) SHA256/SHA256d pool and want predictable share accounting, a hardened RPC surface, and miner documentation that reduces support tickets.
MixTrust pool fundamentals: shares, blocks, and payout correctness
Most “pool problems” are accounting or wallet problems, not Stratum problems. For MXT, treat the node and payout path as part of your critical system: define how balances move from shares → rounds → mature coins → payments, and instrument each boundary with checks.
- Pool posture: Decide whether you are onboarding the public, an internal farm, or a private group. Each posture changes anti-abuse defaults.
- Share acceptance rules: Define reject handling (stales/dupes/low diff) and make it visible in the dashboard so miners can self-diagnose.
- Payout mechanics: Choose a payout model and document when balances become payable (immature vs confirmed vs paid).
- Operational limits: Rate limits, per-IP session caps, and ban rules protect the pool when a miner misbehaves or a botnet finds you.
Choosing software for MXT: website-first vs API-first deployments
MXT does not require a special pool engine, but it benefits from a deployment that keeps configuration readable and repeatable. The right stack is the one you can operate without “mystery state.”
- Yiimp-based: Good for a traditional pool site experience with built-in pages. Reference: Yiimp setup guide. See Yiimp setup guide.
- Miningcore: Strong option when you want structured configuration, Postgres-backed accounting, and API endpoints for your own UI. Reference: Miningcore setup guide. See Miningcore setup guide.
- Custom integration: Useful if MXT’s daemon has quirks in block template fields or you need custom payout/anti-abuse logic.
VarDiff (variable difficulty) should be designed, not guessed. We set difficulty bands so small miners don’t flood share submissions and large miners don’t get “flat” hashrate charts from too few shares.
MXT pool buildout: components we configure and validate
- MXT daemon deployment: Build/install, sync monitoring, RPC auth, and non-root service operation.
- Database + retention: Schema, backups, and pruning rules matched to your share volume and reporting needs.
- Stratum config: Ports, TLS, difficulty curves, and ban logic that matches your expected miner population.
- Payments and fees: Thresholds, batching, fee accounting, and guardrails around manual payments. See payout schemes and SOLO vs PPLNS vs PROP.
- Site and stats: A clean front page, miner stats, worker tables, and a status view for incidents.
- Hardening & monitoring: Firewall policy, alert thresholds, log rotation, and recovery playbooks. See security hardening.
For MXT, we also test that wallet send calls return consistent error codes. That makes automated payout handling reliable and prevents silent failures.
MXT miner connection examples and credential conventions
Show two endpoints (plain + TLS) and a worker format that matches your auth design. If you use account-based auth, be explicit about whether the password field is used or ignored.
stratum+tcp://POOL-DOMAIN:3333
stratum+ssl://POOL-DOMAIN:3443For marketplace hashpower, we provide a separate “strict” port with tighter rate limits and clearer reject messaging.
MixTrust coin considerations for pool operators
- Address format and checksum behavior: Before launch, confirm the wallet rejects invalid addresses and how it handles mixed-case or alternate prefixes. Add server-side validation so typos never hit the payout queue.
- Mempool/fee policy reality: Some small chains have volatile fee acceptance. We test payout batching sizes and fee selection so payments don’t get stuck in the mempool.
- Node drift detection: Implement alerts for stalled headers, peer count collapse, and sudden reorgs; these are early indicators that payouts should be paused.
MXT go-live steps
- Node sync and peer stability observed over time, not just a one-time “caught up” check.
- RPC access restricted to pool hosts; secrets stored outside repo and rotated when needed.
- Share processor tested under load (burst shares) to validate DB and CPU headroom.
- VarDiff bands confirmed with at least one small miner and one high-hash ASIC.
- Payout automation proven with small payouts and a forced-failure test to confirm idempotency.
- Dashboard shows rejects by reason and exposes last payout run status.
- Operator runbook written: restart steps, incident checklist, and contact/support path.
MixTrust pool Q&A
Do you validate the MXT daemon build before wiring it to Stratum?
Yes. We verify the exact daemon version, confirm the RPC calls the pool will use, and run template/submission tests. That reduces the chance of launching against an incompatible fork.
Can you run an invite-only MXT pool without public registration?
Yes. We can configure private authentication, disable public signups, and still provide a dashboard for your miners. Abuse controls can be relaxed when you control the miner set.
How do you reduce rejected shares on MXT?
We tune timeouts, job refresh behavior, and VarDiff, then test with real miners. We also publish miner-side guidance so farms avoid proxy misconfiguration and stale-heavy setups.
Do you help design payouts and fee accounting for MXT?
Yes. We implement your chosen payout model, add batching controls, and expose payment history with enough detail for miners to audit results.
What should I include when requesting an MXT setup plan?
Send the target pool type, expected miner count/hashrate, hosting preference, and whether you need a full public website. If you have an existing wallet/node, include how it was built and where it runs.
Need a MixTrust pool that is easy to operate? Contact us with your planned miner mix and payout model. Contact us.