pool.pc.am - PPLNS pool for PCoin (PCN), RandomX on an 80-byte Bitcoin headerI run this pool. It is the only PCoin pool that exists, which is a problem I would like somebody to solve by competing with me - see the last section, I mean that literally.
Connectionstratum+tcp://pool.pc.am:3333
Username is your PCN address (
pc1q...). Password is ignored - anything works. No registration, no account, no email.
Terms- fee
2%-
PPLNS (factor 2)
- payout
every block found - not on a timer, not on a threshold you have to reach first
- minimum payout 0.00000294 PCN
- payouts are made
in the coinbase of the block itself, so there is no hot wallet holding your balance and nothing for me to run off with. If you can see the block, you have already been paid.
- vardiff, target 15 s per share, range 1-1,000,000
Live, as I write this-
31 miners connected, pool hashrate 247,266 H/s
- network hashrate 708,285 H/s, so the pool is about 35% of it
- 319 blocks found to date, 15,631.00 PCN paid out
- chain height 4350, spacing 564 s over the last 300 blocks against a 600 s target
- whole-network emission at that pace: roughly 7,665 PCN/day, shared by everyone
API, if you would rather read it than trust me:
https://pool.pc.am/api/poolsTwo ways to point hashrate at it1. The node's built-in miner - no separate mining software at all:
bitcoin-cli startpoolmining "<your pc1q address>" 0
Needs node
and bitcoin-cli at v1.3.0 or newer; an older CLI sends the thread count as text and the call fails with a type error.
2. xmrig-family miners, via rx/pcoin - submitted upstream,
open and not merged, so treat it as third-party code:
https://github.com/Bendr0id/xmrigCC/pull/435./xmrigMiner -o pool.pc.am:3333 -u <your pc1q address> -a rx/pcoin -t 4
The pool rejected
100% of shares from standard xmrig with "share above target" while the miner hashed perfectly: it rebuilt the submitted header with the nonce bytes in the opposite order from the xmrig convention. My node's own miner and my pool were written from the same wrong assumption, so they agreed with each other and nothing looked broken until a third-party miner existed. Both byte orders are accepted now. Worth retrying.
What this pool does not doIt does not increase your earnings - after the fee you earn slightly less on average than solo mining. It reduces variance. That is the entire product, and on a chain emitting 7,665 PCN/day across everyone, variance is the thing worth reducing.
It does not make the chain faster. Spacing is set by the difficulty algorithm (LWMA, retargeting every block), not by how miners organise.
The disclosure that matters more than the termsA single solo address - not this pool, not me - currently finds
65% of blocks (measured over the last 150, 95% CI 57-72%). That is majority hashrate on a live chain, and it means a party other than me could reorganise recent blocks. Nothing has gone wrong so far: reorg_count is 0, no blocks unwound, supply exact against height. But you should know it before pointing hardware here, and you can check it yourself - every coinbase is public on
https://explorer.pc.am (use several hundred blocks; 60 is mostly noise).
Please compete with meOne pool on a chain is a centralisation problem even when the operator behaves, and "trust me" is not an answer. The pool code is MIT and lives in the PCoin repo under
contrib/pool:
https://github.com/pars5555/pcoin/blob/main/contrib/pool/MINER-INTEGRATION.mdIf you run pools and want to add PCN, I will help with the stratum details for free, including the nonce-order trap above, and I will link your pool from pc.am next to mine. I would rather be one of four pools than all of one.
The part you should not skipPCN is not traded on any exchange. No orderbook, no volume, no market cap, no way to sell it for cash. Mining here earns you a share of a fixed emission and nothing more; what you earn falls every time somebody else joins. If you want revenue, point your hardware at something with a market - genuinely, I am not being coy.
Chain is 18 days old. Source:
https://github.com/pars5555/pcoin
