P2Pool Bitcoin: Trustless Peer-to-Peer Mining Explained

P2Pool is the original trustless peer-to-peer Bitcoin mining pool: no operator, no custodian, no permission required. Miners run their own node, join a shared parallel blockchain called the sharechain, and receive coinbase payouts directly when the pool finds a block. The original P2Pool for Bitcoin is no longer active — its last known block was in early 2019 — but the architecture it proved is the intellectual foundation for every decentralized pool design that followed, including DATUM and the emerging P2Pool v2 protocol.

What P2Pool actually is

Most mining pools work the same way: you point your miner at a company’s stratum server, the company selects which transactions go in the block, and at the end of the day the company pays you from a wallet it controls. You trust the operator to count your shares honestly, pay you accurately, and not run off with the funds.

P2Pool removes the operator entirely. Instead of connecting to a company’s server, you run your own P2Pool node on your own machine. That node joins a peer-to-peer network with every other P2Pool miner in the world. Together, those nodes maintain the sharechain — a second blockchain running in parallel to Bitcoin — and when the pool collectively finds a valid Bitcoin block, the reward is split directly in the block’s coinbase transaction, with no intermediary ever holding the funds.

There is no company to trust. There is no company to fail. There is no company to censor you.

The sharechain: how P2Pool coordinates miners without a server

Bitcoin blocks target a 10-minute interval and require enormous cumulative work to find. If P2Pool miners simply tried to find full Bitcoin blocks, they would have no way to prove proportional work contributions — it would just be solo mining with extra steps.

P2Pool solves this with the sharechain, a secondary blockchain targeting a 30-second block interval at much lower difficulty. Every time a miner finds a share — a block that meets the sharechain’s lower target but not Bitcoin’s full target — that share is broadcast to all other P2Pool nodes. The sharechain records this proof of work.

Occasionally, a share happens to meet Bitcoin’s full-network difficulty. That share is a valid Bitcoin block. When that happens, the reward is distributed according to each miner’s share of the last 8,640 entries in the sharechain, representing roughly 72 hours of contributions (the PPLNS window). Every miner who contributed work in that window receives a direct coinbase output proportional to their contribution — no batching, no pooled wallet, no withdrawal request required.

Key properties of the sharechain architecture:

• Trustless share validation — any miner can independently verify every other miner’s shares by checking the sharechain
• Sybil resistance — fabricating shares requires actual proof-of-work; there is no pool account to fake
• Pool-hop resistance — the PPLNS window rewards consistent contributors; joining only when a block is imminent does not pay
• Instant coinbase settlement — when a block is found, payouts exist on-chain in the same transaction; there is no settlement delay

Coinbase payouts: what “no custodian” actually means

In a standard pool, you mine, shares accumulate in a database, the pool finds a block, funds land in the pool’s wallet, and the pool later sends you your share (minus fees, minus withdrawal minimums, minus whatever policy they choose). The pool controls the money between block find and your withdrawal.

In P2Pool, there is no such intermediate state. The coinbase transaction — the first transaction in every Bitcoin block, created by whoever found the block — directly lists every miner’s payout address and amount. The payouts exist the moment the block is confirmed. There is no pool wallet. There is no waiting. There is no entity that could freeze your funds, because no entity ever holds them.

This is structurally distinct from pools that claim to be non-custodial through Lightning or batched on-chain payouts. Those pools still hold funds momentarily and make promises about disbursement. P2Pool’s coinbase payout is a consensus rule: the payouts are part of the block itself.

P2Pool vs solo mining

Both solo mining and P2Pool give you the same trustless property: you control your node, you validate your own transactions, no intermediary touches your funds. The difference is variance and frequency.

Property	Solo mining	P2Pool (original)
Operator trust required	None	None
Full node required	Yes	Yes
Transaction selection	You choose	You choose (coinbase template)
Payout frequency	When you find a block alone	When the pool finds a block (pooled hashrate)
Variance	Extreme (lottery)	High (pooled, but P2Pool hashrate was small)
Payout destination	Direct to your wallet	Direct coinbase output to your wallet
Current viability for Bitcoin	Yes — see solo mining guide	Original P2Pool no longer active; successors in development

P2Pool was designed for the middle ground: more frequent payouts than solo (because pooled hashrate found blocks more often than a single miner), while preserving the trustless property that solo mining has but conventional pools sacrifice. See our solo vs pool mining guide for the full trade-off analysis, and the every hash counts solo mining page for the philosophical case for direct participation.

P2Pool vs OCEAN + DATUM

OCEAN, launched in 2023, is the closest active implementation to P2Pool’s vision available today. Its DATUM protocol (Decentralized Alternative Templates for Universal Mining, launched September 2024) gives miners control over block template construction using their own full node — restoring the transaction-selection sovereignty that conventional pools strip away.

Property	P2Pool (original)	OCEAN + DATUM
Operator exists	No — pure P2P	Yes — OCEAN operates the pool
Block template selection	Each miner (via their full node)	Each miner using DATUM (via their full node)
Custodian holds funds	Never	No (transparent TIDES non-custodial payouts)
Full node required	Yes (mandatory)	Recommended for DATUM; optional for standard mode
Fee	0% (no operator)	1% with DATUM / 2% standard
Network hashrate	~0 TH/s (defunct)	Active — approximately 1% of global hashrate (attributable to OCEAN’s public stats; verify at ocean.xyz)
Active / production	No (last Bitcoin block ~February 2019, per Bitcoin Magazine)	Yes

The important distinction: P2Pool eliminated the operator entirely, which is the purest architectural form of decentralization. OCEAN keeps an operator (which introduces a point of trust and a fee), but DATUM removes the operator’s ability to censor your transactions — because you, not OCEAN, build the block template. Different trade-offs, same direction of travel.

For a full comparison of current live pools across decentralization, fees, payout schemes, and hashrate, see our mining pools hub and the 2026 Bitcoin mining pool comparison.

Why the original P2Pool stopped working on Bitcoin

P2Pool’s architecture was sound but ran into three compounding problems as the Bitcoin network grew:

1. Variance became prohibitive at small network hashrate

P2Pool’s effectiveness depended on the pool holding enough collective hashrate to find Bitcoin blocks with reasonable frequency. As large centralized pools captured the majority of global hashrate, P2Pool’s share shrank. Fewer blocks meant less frequent payouts, longer windows between income events, and a worse expected-value proposition for small miners who could not tolerate months between payouts. Blocks found on Bitcoin mainnet via P2Pool averaged once every 108 days as of early 2018 — essentially lottery-grade variance.

2. Coinbase transaction bloat

P2Pool paid every miner directly in the coinbase transaction. As more miners joined, the coinbase grew — each miner required a separate output. A bloated coinbase consumes blockspace that could otherwise carry fee-paying transactions, making P2Pool blocks less economically competitive to build than blocks from pools with simple coinbase structures. Miners building on those blocks receive less fee revenue, creating a structural disadvantage.

3. Dust economics

With a large number of miners splitting a block reward, individual payouts became extremely small. As Bitcoin transaction fees rose, these tiny coinbase outputs became economically unspendable — worth less than the cost to spend them. The trustless direct payout that was P2Pool’s core feature became a liability.

According to reporting in Bitcoin Magazine, the last block mined by the original P2Pool Bitcoin network was February 12, 2019. The project’s GitHub repository has been effectively dormant since the late 2010s.

What comes next: P2Pool v2, Braidpool, and DATUM

P2Pool’s failure was not a failure of the idea — it was a failure of the specific architecture to scale. Multiple projects are attempting to carry the trustless decentralized pool concept forward with improved designs:

P2Pool v2

A from-scratch rewrite in early development (as of mid-2026) that addresses the variance and coinbase bloat problems. The proposed design uses uncle blocks (reducing wasted work from stale shares) and atomic-swap payment channels (enabling payouts without bloating the coinbase transaction with hundreds of outputs). Status: early development; not yet production-ready for Bitcoin.

Braidpool

A directed acyclic graph (DAG) based approach to share tracking, replacing the linear sharechain with a structure that can handle high stale rates without discarding valid work. Designed to be more resilient to latency differences between geographically distributed miners. Status: research and prototype phase as of mid-2026.

Stratum V2 with miner-selected templates

The Stratum V2 protocol includes a Job Negotiation sub-protocol that allows individual miners to construct block templates and submit them to pools, rather than receiving pool-constructed templates. This is a different architectural approach — pools still exist as coordinators — but it achieves a similar goal of removing transaction-selection power from pool operators. Our Stratum V1 vs V2 comparison explains the full technical distinction.

OCEAN + DATUM (production today)

As noted above, DATUM is the only production implementation today that gives miners full block template control while providing access to pooled hashrate at meaningful scale. It does not eliminate the operator, but it neutralises the operator’s censorship capability. See the dedicated DATUM protocol page for setup details.

P2Pool setup outline (historical reference)

The original P2Pool is no longer active on Bitcoin. This outline is provided as historical documentation and as a reference for anyone experimenting with the protocol or evaluating its successors.

Requirements

• Full Bitcoin node — a fully synced bitcoind instance. There is no workaround; P2Pool requires direct RPC access to your own node. As of 2026 this means approximately 650 GB of disk space for a pruned node (or ~700+ GB for full archival), reliable bandwidth, and a machine capable of running 24/7.
• P2Pool software — the original Python-based P2Pool node (p2pool/p2pool on GitHub). Note: the repository is unmaintained; forks exist but are not officially supported.
• Mining hardware — any ASIC or GPU that can connect to a stratum server on your local machine
• Static payout address — your Bitcoin address for coinbase payouts; this is set at the node level, not per-connection

Connection flow

1. Run bitcoind with RPC enabled (rpcuser, rpcpassword, server=1)
2. Run the P2Pool node, pointing it at your local bitcoind via RPC
3. P2Pool exposes a stratum interface on port 9332 and a P2P port on 9333 for peer discovery
4. Point your miner to stratum+tcp://127.0.0.1:9332 — username and password are arbitrary
5. Forward port 9333 through your router if you want other P2Pool nodes to connect inbound to yours

What you cannot skip

The full node requirement is not optional and cannot be replaced by a pruned node’s JSON-RPC alone — P2Pool needs live mempool access to build valid block templates. This is also the reason P2Pool provides trustlessness: you are validating every transaction independently. If you are unwilling to run a full node, P2Pool is the wrong tool. Use a conventional pool, or consider OCEAN with DATUM if decentralization matters to you.

Is P2Pool right for you?

For Bitcoin mining in 2026, the honest answer is: the original P2Pool is not operational, so it is not an option. The relevant questions are about what comes next.

If your priority is zero operator trust and you are willing to accept extreme variance: solo mine. See our solo mining guide and every hash counts page for the full case.

If your priority is operator-free transaction selection with pooled hashrate: watch the P2Pool v2 and Braidpool projects. Neither is production-ready today.

If your priority is non-custodial payouts with miner-selected templates, available now: OCEAN with DATUM is the closest live option. Read the DATUM protocol explainer for setup and the pool payout calculator to model variance at your hashrate.

Use current hashprice data to sanity-check any pool-comparison math against live market conditions before committing hashrate.

Frequently asked questions

Is P2Pool still running on Bitcoin?

No. According to research published by Bitcoin Magazine, the last block mined by the original P2Pool Bitcoin network was February 12, 2019. The official homepage at p2pool.org explicitly states that P2Pool “is no longer viable in its original form” on Bitcoin. The GitHub repository has been effectively dormant since the late 2010s. If you encounter a node claiming to run P2Pool for Bitcoin, treat it with caution — you cannot verify share accounting if the network has no active participants.

What is the sharechain and why does it matter?

The sharechain is P2Pool’s core innovation: a second blockchain running in parallel to Bitcoin, targeting a 30-second block interval at lower difficulty. Miners submit shares to this sharechain as proof of ongoing work. When any share happens to meet Bitcoin’s full difficulty, it becomes a valid Bitcoin block and triggers payouts proportional to each miner’s recent sharechain contributions (the last 8,640 shares, roughly 72 hours). The sharechain means no miner has to trust a pool operator’s share-counting database — the blockchain itself is the ledger, verifiable by anyone.

How is P2Pool different from OCEAN?

P2Pool has no operator at all: it is a pure peer-to-peer protocol. OCEAN is an operated pool that uses the DATUM protocol to give miners control over block templates. The practical consequence: P2Pool charged 0% (no operator to pay), while OCEAN charges 1–2%. In exchange, OCEAN is live and has real hashrate; P2Pool for Bitcoin is not. OCEAN’s DATUM protocol achieves the key trustless property P2Pool was designed for — miners choose transactions — while accepting the trade-off of an operator handling reward distribution. See the DATUM protocol page for details.

Why does P2Pool require a full Bitcoin node?

P2Pool must build valid Bitcoin block templates to construct shares, and block templates require live access to the mempool and UTXO set — data only a full node has. The full node requirement is also the mechanism of trustlessness: you independently validate every transaction you include, rather than accepting a pool operator’s template. If you run P2Pool, you are a self-sovereign participant in Bitcoin’s transaction ordering, not a passive hashrate provider.

What happens to P2Pool coinbase payouts when a block is found?

The coinbase transaction — the special first transaction in a Bitcoin block that creates new coins — lists every participating miner’s address and their proportional payout amount. These outputs are created by consensus, not by a pool operator. The moment the block is confirmed, the payouts exist on-chain. There is no pool wallet, no withdrawal request, no minimum balance, and no company that could freeze or reverse the funds. The payouts are part of Bitcoin’s consensus state.

Is P2Pool v2 ready to use?

Not as of mid-2026. P2Pool v2 is an active development project that redesigns the protocol from scratch to address the original’s scaling problems — using uncle blocks to reduce wasted work and payment channels to avoid coinbase bloat. It is not yet in production and has no meaningful Bitcoin hashrate. Follow the development at the p2pool GitHub organisation and p2pool.org for updates. The project is genuinely promising engineering, but it has not cleared the gap between prototype and operational network.