Elastos (ELA) Merged‑Mining (AuxPoW) Pool Setup — Operational Blueprint
Elastos uses the SHA256/SHA256d proof‑of‑work family, so ASIC miners can contribute hashpower. A production‑grade ELA pool is more than a Stratum port: you need stable nodes, auditable accounting, and miner‑friendly onboarding.
ELA merged mining: what changes operationally (AuxPoW)
Merged mining means one mining job can produce work for more than one chain. For Elastos, that introduces extra moving parts: auxiliary block construction, proof submission, and accounting that must stay cleanly separated from the parent chain.
- AuxPoW (auxiliary proof-of-work): validate the end-to-end aux flow so blocks are submitted correctly and tracked to maturity.
- Isolation by design: keep ELA balances, wallets, and payout logic independent—even if the parent chain is also in your stack.
- Operational visibility: monitor aux block acceptance, orphan handling, and template freshness so issues surface immediately.
- Miner documentation: keep endpoints and worker rules simple; merged mining already has enough complexity behind the scenes.
Engine choice for ELA AuxPoW: practical options
The right engine for ELA depends on how you implement the AuxPoW pipeline and what else you operate. We prioritize a design that keeps the aux logic auditable and easy to monitor.
- Yiimp-based: Works well when you want a classic UI and fast deployment; start with Yiimp setup guide and integrate AuxPoW carefully.
- Miningcore: A good fit when you want services separated and monitored; use Miningcore setup guide as the baseline and add the aux submission path.
- Custom stack: Choose custom when you need tight integration with an existing BTC pool, custom reporting, or specialized aux validation.
Treat ELA merged mining as its own product: separate wallets, separate dashboards, and separate incident response steps. Shared systems hide problems.
ELA merged-mining build scope (aux flow + pool ops)
- ELA node layer: deploy and supervise nodes, restrict RPC, and validate AuxPoW-related calls in staging.
- Pool core + database: block tracking that records aux context, share accounting, and retention tuned for expected hashrate.
- Stratum endpoints: ports and VarDiff (variable difficulty) tuning; document merged-mining behavior without exposing internals.
- Payout pipeline: isolated wallet signing, batching, and payout model selection (see payout schemes plus how to choose SOLO vs PPLNS vs PROP).
- Website UI: ELA-specific stats and payment history; avoid mixing dashboards across coins to prevent confusion.
- Security hardening: backups, secrets handling, firewalling, and monitoring guidance (see security hardening).
We validate the AuxPoW path with controlled tests: generate work, submit aux blocks, track confirmations, and reconcile payouts—before you scale traffic.
ELA merged-mining miner endpoints (documentation examples)
Keep miner-facing connection info minimal. If miners can connect and see consistent stats, the aux mechanics can stay behind the curtain.
stratum+tcp://POOL-DOMAIN:3333
stratum+ssl://POOL-DOMAIN:3443Publish a short note describing merged mining at a high level and clarify that miners still connect using standard Stratum URLs.
ELA AuxPoW integration notes: accounting isolation and monitoring
- Aux submission logs: record auxpow submissions and acceptance results so troubleshooting has concrete evidence.
- Accounting isolation: keep ELA wallets and ledgers separate from any parent-chain payouts you operate.
- Node pairing: verify the parent-chain and ELA components agree on job flow, so aux proofs are built from fresh templates.
- Orphan monitoring: alert on shifts in orphan behavior and correlate with node health and template freshness.
- Upgrade discipline: test aux pipeline changes in staging; regressions are expensive to debug in production.
ELA AuxPoW launch checklist (validate before scaling)
- ELA node synced and healthy; aux-related calls validated in staging before public mining.
- RPC restricted and authenticated; aux submission and wallet methods reachable only from required services.
- Stratum endpoints tested; VarDiff stable and logs confirm clean share and aux submission flow.
- Database backup and restore drill completed; block and aux tracking verified.
- Payout rehearsal completed with isolated ELA wallet and confirmation tracking.
- UI and status pages show ELA-specific health signals; no mixed accounting with other coins.
- Launch plan staged with rollback steps and monitoring thresholds for scaling up.
ELA merged-mining FAQ for pool operators
What does AuxPoW change in an ELA pool build?
It adds an auxiliary block flow that must be constructed, submitted, and tracked. We build monitoring around that path so you can see acceptance and maturity behavior clearly.
Can ELA merged mining share infrastructure with a BTC pool?
Infrastructure can be shared, but accounting should not be. We isolate wallets, balances, and dashboards so issues in one environment don’t corrupt the other.
How do you test the ELA AuxPoW pipeline before launch?
We run controlled tests in staging: generate jobs, submit aux proofs, track confirmations, then execute a payout cycle and reconcile results against the ledger.
Do miners need special software for ELA merged mining?
Miners typically connect with standard Stratum endpoints. The merged-mining complexity lives on the pool side, not in the miner configuration.
What do you need from me to start an ELA AuxPoW setup?
Tell us your existing pool stack, expected hashrate, hosting plan, and whether you want ongoing monitoring and operations after deployment.
Running BTC already and adding ELA AuxPoW? Contact us with your current stack so we can plan isolation correctly.