Can you build a PROC 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 PROC?

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

ProCurrency (PROC) Mining Pool Setup — SHA256/SHA256d Deployment Notes

ProCurrency uses the SHA256/SHA256d proof‑of‑work family, so ASIC miners can contribute hashpower. A production‑grade PROC pool is more than a Stratum port: you need stable nodes, auditable accounting, and miner‑friendly onboarding.

On this page

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

Before you pool PROC: validate the chain and the wallet behavior

For smaller SHA256 coins, the highest risk is not hashrate—it is operational uncertainty. A PROC pool should start with basic chain validation: the node stays synced, RPC calls behave as expected, and the wallet can reliably construct and sign payouts.

Chain viability: confirm you can maintain stable peers and that your node does not drift behind height during normal load.
Wallet I/O: test address generation, balance reporting, and transaction creation with the exact daemon build you will run in production.
Accounting boundaries: decide how you handle orphaned blocks and credit reversals before you accept public miners.
Stratum ergonomics: document the username format you accept and how workers are named, so miners do not accidentally mine to an invalid address.

PROC platform decision: fast Yiimp portal vs clean Miningcore APIs

PROC can be served by either Yiimp or Miningcore; the difference is how much UI you want out-of-the-box versus how much you prefer to automate via APIs.

Yiimp route: good when you want a familiar portal with minimal custom coding. Use Yiimp setup guide as a starting point, then focus on security and backups.
Miningcore route: strong for operators who want clean metrics and integration into Prometheus/Grafana-style stacks. Start from Miningcore setup guide and tailor coin settings.
Custom route: choose this if you need bespoke payout logic, special authentication, or a multi-tenant architecture with strict client isolation.

Operator note

Define your performance target up front: low-latency Stratum for farm miners is a different profile than “burst traffic” from rentals.

PROC pool configuration scope (what gets delivered)

Node provisioning: install/build, version pinning, and a documented procedure for upgrades, reindex, and rescan.
RPC hardening: private network exposure, credential rotation, and allowlists so only the pool backend can call wallet methods.
Stratum services: connection limits, ban thresholds, and a tested vardiff policy; vardiff here means share difficulty adapts per worker to keep server load stable.
Payout system: batch construction, fee strategy, and references to payout schemes plus a decision guide for SOLO vs PPLNS vs PROP.
Pool UI and status: basic miner stats, pool health, and an incident banner path when the chain is unstable.
Security and maintenance: upgrades, audit logs, and operational controls aligned with security hardening.

A PROC pool build is more than a Stratum port. We wire the parts that reduce operator pager fatigue: deterministic payouts, clear alerting, and a repeatable deploy process.

PROC miner config examples you can paste into documentation

Keep your miner docs strict: one canonical set of URLs, one worker format, and examples for both plain TCP and TLS. Everything else belongs in a longer help page.

stratum+tcp://POOL-DOMAIN:3333
stratum+ssl://POOL-DOMAIN:3443
username: PROC_WALLET_ADDRESS.rig01
password: x

If you accept marketplace hashpower, add an example that matches their “user.worker” conventions and mention any enforced minimum difficulty or extranonce requirements.

PROC-specific checks: addresses, RPC, and payout safety

Address validation: verify the daemon’s address prefix and checksum rules, then add a front-end validator so users cannot register a malformed payout address.
Wallet locking: decide whether the pool unlocks the wallet only for payout windows or keeps it unlocked; document the risk trade-off and test restart behavior.
Explorer/indexing: if you operate an explorer, confirm it agrees with the pool’s block tracking; mismatches usually point to reorgs or bad peer sets.

PROC commissioning checklist (from testnet to mainnet)

Bring up a node on clean storage, sync it fully, and confirm basic RPC calls (getblockcount, getblockhash, getwalletinfo) are stable.
Restrict RPC to a private interface, then verify the pool backend can reach it and the public website cannot.
Configure pool coin settings, start Stratum, and test share submission using a single known miner.
Force a payout dry-run (no broadcast) to validate fee selection, change outputs, and address formatting.
Enable logging/metrics for rejects, block candidates, orphan rate, and wallet RPC errors; alert on abnormal patterns.
Run a short public beta with tight limits, then adjust vardiff and banning based on observed miner behavior.
Finalize documentation and incident procedures, then open registration if running a public pool.

ProCurrency pool FAQ (ops + security)

What is the minimum information required to spin up a PROC pool?

At minimum you need the daemon build/version you trust, a payout wallet plan, and a DNS name for the pool endpoints. Everything else—UI, payout model, monitoring—should be decided before public miners arrive.

Can I operate PROC as a private pool for a single farm?

Yes. A private pool is often safer for smaller coins because you control miner behavior. You can still keep public-facing docs minimal while retaining full monitoring and payout verification.

Why do rejects spike when PROC hashrate jumps suddenly?

Large hashrate swings change share arrival patterns and can expose weak vardiff settings or CPU bottlenecks. You fix it by tuning per-connection difficulty targets and ensuring the backend can process bursts.

Should the PROC wallet live on the same host as Stratum?

Only if you have to. Separating the wallet host reduces blast radius, especially when you need to unlock keys for payouts. If co-located, isolate with firewall rules and strict service accounts.

Do you support security hardening and long-term maintenance for PROC?

Yes. The core work is hardening RPC and secrets, building monitoring, and documenting upgrade procedures so the pool stays predictable through node releases.

Need PROC validated and deployed safely? Contact us and include whether you want solo, private, or public operation.