❓ FREQUENTLY ASKED QUESTIONS

Stratum URL:

stratum+tcp://pool.pyblock.xyz:4445
stratum+tcp://pool.pyblock.xyz:23112 — ASIC (share diff 4096)

Configuration:

1. URL: stratum+tcp://pool.pyblock.xyz:4445 (GPU/CPU) or :23112 (BLAKE2b ASIC)
2. Username: Your Bitcoin address (any format: Legacy, SegWit, Taproot)
3. Password: Anything (we don’t check passwords)
4. Worker name (optional): Add .workername to your address

Example:

Username: bc1qYOURADDRESS.rig01
Password: x

Since block 970,000 these are Carousel ports: same rotation, same split as :30110. Nothing to reconfigure if you were already mining here.

WAVICLES is PyBLØCK’s own DATUM pool — nothing to do with Ocean. There are two ways in.

1 · You run the node (the real thing):

b.pyblock.xyz:28915

That is a DATUM endpoint, not a stratum port: your own datum_gateway connects to it, and your miners point at your gateway. Your Bitcoin Knots BLAKE2b node builds the block; the pool only sets the split. Pool pubkey and the full walkthrough are on the WAVICLES page and, step by step, on Get started.

2 · No node? Mine through ours:

1. URL: stratum+tcp://b.pyblock.xyz:23115 (GPU/CPU) or :23114 (ASIC, share diff 4096)
2. Username: Your Bitcoin address (.worker optional)
3. Password: Anything

The block is then built by PyBLØCK’s node and submitted by PyBLØCK’s gateway, but your address is still paid its share of the work window.

Native Stratum V2 over Noise — one port per pool:

stratum2+tcp://pool.pyblock.xyz:5594/9bHUc9mm6rV6mcg1QUWfgSToWtLrW9ydbXRvBfDGX1kCVeYhLfR
:5594 CHIRP (GPU/CPU) · :23133 CHIRP ASIC · :30130 CAROUSEL — same key on all three

Configuration:

1. URL: stratum2+tcp://pool.pyblock.xyz:<port>/<authority key>
2. Authority key: 9bHUc9mm6rV6mcg1QUWfgSToWtLrW9ydbXRvBfDGX1kCVeYhLfR — published so you can pin it
3. Username: Your Bitcoin address (.worker optional)
4. Password: Anything

SV2 here is the transport, not a separate pool: the payout is whatever the pool behind the port pays — CHIRP’s shared reward on :5594 / :23133, CAROUSEL’s 22 / 1% / 77% on :30130. The handshake is encrypted and the templates are the same clean, spam-free ones. Full spec: pyblock-sv2-blake2b.txt.

Stratum V1 — BLAKE2b:

stratum+tcp://pool.pyblock.xyz:5574 GPU / CPU / browser · diff 1
stratum+tcp://pool.pyblock.xyz:23113 ASIC · high diff (starts at 4096)

Configuration:

1. URL: stratum+tcp://pool.pyblock.xyz:5574 (GPU/CPU) or stratum+tcp://pool.pyblock.xyz:23113 (ASIC)
2. Username: Your Bitcoin address
3. Password: x

CHIRP is a shared-reward syndicate: when any member finds a block, the reward is split by loyalty (tenure) and power — you keep 98% (1% node-runner · 1% PyBLØCK). To qualify you need 7 days of mining and a small minimum power (~35 minutes of one Bitaxe). Minimum payout is 1,000 sats (anti-dust). Keep mining and your weight grows.

Optionally, yes. The plain stratum+tcp:// ports stay exactly as they are. If you want the transport encrypted and the pool authenticated, use native Stratum V2: Noise-encrypted binary framing, extended channels, and PyBLØCK’s authority key 9bHUc9mm6rV6mcg1QUWfgSToWtLrW9ydbXRvBfDGX1kCVeYhLfR pinned in the URL — same pools, same rules, same payouts:

• CHIRP GPU/CPU: stratum2+tcp://pool.pyblock.xyz:5594/9bHUc9mm6rV6mcg1QUWfgSToWtLrW9ydbXRvBfDGX1kCVeYhLfR
• CHIRP ASIC (diff 4096): stratum2+tcp://pool.pyblock.xyz:23133/9bHUc9mm6rV6mcg1QUWfgSToWtLrW9ydbXRvBfDGX1kCVeYhLfR
• CAROUSEL: stratum2+tcp://pool.pyblock.xyz:30130/9bHUc9mm6rV6mcg1QUWfgSToWtLrW9ydbXRvBfDGX1kCVeYhLfR

Honest note: today the only SV2-BLAKE2b client is the bridge’s test client — pyblockMiner gets an SV2 mode next release (same spec, in pyblock-sv2-blake2b.txt); Sia ASICs don’t speak SV2 and stay on :23113.

Point it to stratum+tcp://pool.pyblock.xyz:23113. Share difficulty starts at 4096 (2⁴⁴ hashes per share) so a big miner doesn’t flood the pool when it connects.

Your credited power is identical: CHIRP counts Σ difficulty of accepted work, so share difficulty only changes how often you report, never your odds or your slice. Same syndicate, same registry, same 98% · 1% · 1% split. GPU / CPU / browser miners stay on :5574 (diff 1).

Since 2026-09-06 the CHIRP syndicate no longer mines a pool template: every CHIRP job is built on a sovereign template published by an independent node-runner (a Template Supplier), picked by the same deterministic Carousel rotation (seed = previous block hash, so anyone can recompute who was scheduled).

The node-runner whose template gets mined is paid 1% in the same coinbase that pays the members — 98% to the syndicate, 1% node-runner, 1% PyBLØCK, nothing custodial. Each block also commits a registry snapshot (v2) in an OP_RETURN, so the draw, the split and every payout are verifiable on-chain.

Stratum V1 — port 30110 (also :4445 and :23112 since block 970,000):

stratum+tcp://pool.pyblock.xyz:30110

Configuration:

1. URL: stratum+tcp://pool.pyblock.xyz:30110 — or :4445 / :23112, same Carousel
2. Username: Your Bitcoin address
3. Password: Anything

Every job hands your miner a different community member’s clean, spam-free template — you rotate through everyone’s sovereign templates. If you find a block you keep 22% (1% goes to the miner who supplied that template, 77% to PyBLØCK). Plain Stratum V1 — any BLAKE2b miner works; there is also a native SV2 port at :30130.

All Bitcoin address formats are supported:

• Legacy (P2PKH): Starts with 1 (e.g., 1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa)
• SegWit (P2SH): Starts with 3
• Native SegWit (Bech32): Starts with bc1q (recommended)
• Taproot (Bech32m): Starts with bc1p

⚠️ Important: Use an address you control, NOT an exchange address. Exchanges may not credit solo mining payouts correctly.

Yes! Add a worker name by appending .workername to your Bitcoin address.

Examples:

• bc1qYOURADDRESS.s19pro01
• bc1qYOURADDRESS.bitaxe-garage
• bc1qYOURADDRESS.basement-rig

All workers using the same Bitcoin address will be grouped together in your stats. Worker names help you identify which physical miner is which.

For CAROUSEL and CHIRP:

1. Open your address page (or type your address on the home page)
2. You should see your workers and hashrate within 5 minutes

For WAVICLES:

1. Go to the WAVICLES page
2. Look for your address in the current work window
3. If you run your own gateway, check its own status page too

✅ What you should see:

• Your workers listed with names
• Hashrate values (may take 5-10 minutes to stabilize)
• Last share timestamp (should update regularly)

PYBLOCK-CAROUSEL is true solo mining. The miner who finds the block receives 22% of the block reward; 1% goes to the node-runner whose template won and 77% to PyBLØCK — all inside the coinbase, never held by the pool.

Current block reward: 3.125 BTC (after the 2024 halving)

Payment: Sent directly to your Bitcoin address in the coinbase transaction of the block you found.

⚠️ High variance: You could find a block tomorrow, or it could take years depending on your hashrate. This is gambling with proof-of-work.

WAVICLES pays with TIDES: every block pays a work window worth 8× the network difficulty, sharing the reward among everyone who contributed to that window (0% fee). Nothing is held by the pool — it all goes out in the coinbase of the block itself.

How it works:

• You earn in proportion to the work you put into the current window, not to a snapshot of your hashrate
• Paid on-chain, in the block’s own coinbase — no thresholds, no withdrawals, no account
• Minimum 1,000 sats per identity and block; below that your share goes to the other miners of the window, never to the pool
• Each block commits the window snapshot on-chain (PYBLOCK-TON618 + a BLAKE2b-256 hash), so anyone can audit the split

The live window, the snapshot of each block and the verifier are on the WAVICLES page.

CHIRP turns solo variance into a syndicate lottery. Everyone mines together; when any member finds a block, 98% of the reward is split among qualifying members directly in the block’s coinbase. 1% pays the node-runner whose template the block was built from and 1% is the PyBLØCK fee — all in the same coinbase.

Your share is weighted by:

• Loyalty (tenure): how long you’ve been mining — full weight at 30 days
• Power: your accumulated work over the rolling 24h window

To qualify: 7 days of mining and a small minimum power (~35 min of one Bitaxe). Payouts below 1,000 sats are rolled forward (anti-dust). Every winner that fits in the 16 KB coinbase is paid in that block.

Watch your live weight and eligibility on the CHIRP page.

SV2 is only the transport — you are paid by the pool behind the port, exactly as if you had connected over Stratum V1:

• :5594 · :23133 → CHIRP’s shared reward (98% members · 1% node-runner · 1% PyBLØCK)
• :30130 → CAROUSEL, solo: you keep 22% — 1% to the miner whose clean template you were mining when you found the block, 77% to PyBLØCK

⚠️ Solo means extreme variance: you might find a block tomorrow or not for a long time. Payout is instant and on-chain when you do.

Fees are only ever taken from a block reward — never up front, never a subscription. What you keep comes first:

• CAROUSEL (4445 · 23112 · 30110): 22% for you · 1% node-runner · PyBLØCK fee 77%.
• CHIRP (5574 GPU/CPU · 23113 ASIC): 98% shared among members (split by loyalty + power) · 1% node-runner · 1% PyBLØCK fee.
• SV2 (5594 · 23133 · 30130): same split as the pool behind the port — CHIRP on :5594 / :23133, CAROUSEL on :30130.
• WAVICLES (DATUM 28915 · gateways 23115 / 23114): every block paid to the work window, split by share of work (TIDES), in that block’s coinbase · PyBLØCK fee 0%.

💡 Transparency: Every fee is deducted from the block reward inside the coinbase, on-chain and verifiable. What lands in your wallet is what you get. No hidden fees, no surprises.

Use our Mining Calculator to estimate:

• Time to find a block (solo mining)
• Expected daily/weekly/monthly earnings (pooled mining)
• Impact of network difficulty changes
• Profitability based on electricity costs

⚠️ Remember: These are statistical estimates. Actual results vary based on luck, network difficulty changes, and Bitcoin price volatility.

Hashrate is calculated over different time windows:

• 1m hashrate: Average over last 1 minute (most volatile, shows current performance)
• 5m hashrate: Average over 5 minutes (more stable)
• 1hr hashrate: Average over 1 hour (good indicator of consistent performance)
• 1d (24h) hashrate: Average over 24 hours (most reliable metric)
• 7d hashrate: Average over 7 days (shows long-term stability)

💡 Use 24h hashrate for the most accurate representation of your mining operation. Short-term values fluctuate due to variance in share submissions.

A share is a valid proof-of-work submission to the pool. Think of it as a lottery ticket.

How it works:

• Your miner attempts to solve blocks
• Most solutions don’t meet Bitcoin’s difficulty (too easy)
• These easier solutions are “shares” submitted to the pool
• Shares prove you’re actually mining
• One lucky share will eventually meet Bitcoin’s full difficulty = block found!

Best Share: The highest difficulty share you’ve ever submitted. The closer to network difficulty, the closer you were to finding a block!

Your miner reports its theoretical hashrate based on hardware specs. The pool calculates your effective hashrate based on submitted shares.

Why they differ:

• Variance: Share submission is probabilistic (like dice rolls)
• Network latency: Delays between miner and pool
• Rejected shares: Invalid submissions don’t count
• Calculation window: Shorter time windows show more variance

Over 24+ hours, your pool hashrate should match your miner’s hashrate within 5-10%. If consistently lower, check for hardware issues or network problems.

Network difficulty determines how hard it is to find a valid Bitcoin block. Bitcoin adjusts difficulty every 2016 blocks (~2 weeks) to maintain 10-minute average block times.

How it affects you:

• Difficulty increases: Harder to find blocks, lower expected earnings
• Difficulty decreases: Easier to find blocks, higher expected earnings
• Your hashrate stays the same, but your chances change

As more miners join the network, difficulty increases. As miners leave, difficulty decreases. This keeps block times consistent despite changing global hashrate.

Yes! We provide a public REST API for developers to integrate PyBLØCK stats into their apps.

Available endpoints:

• Pool statistics (hashrate, workers, blocks)
• Individual miner stats (by address)
• Block template data
• Network statistics