About the numbers on this page

This pool runs in pps-classic mode, paying out in Thunder (BIP300 drivechain sidechain #9). Every accepted share credits your worker whether or not that share becomes a block. Credits accumulate under your Thunder address in pps_credits.

The rate is not a fixed number. It is derived from each block template as (block value ÷ network difficulty) × (1 − fee), so it moves with difficulty and with the fees in the template. Right now: 0.03 sats per unit of share difficulty, net of the 0.00% operator fee (gross 0.03). Every credit is stored with the exact rate it was paid at, so you can recompute your own balance on your worker page rather than take the pool's word for it.

When a share becomes a block, the coinbase pays the pool's own Bitcoin wallet (bc1qcpssv3eputpx2nmzvsntlrk3jgyyvqr9h5s5d5) for the miner-share of the reward, and the operator address (bc1qcpssv3eputpx2nmzvsntlrk3jgyyvqr9h5s5d5) for the fee of 0.00%. The operator then periodically batches accumulated BTC into Thunder via a canonical BIP300 deposit transaction — this is the step that actually moves value onto the sidechain. Once the pool's Thunder reserve is funded, the payout worker sends Thunder transactions to each miner's Thunder address on a cadence to drain their owed balance.

Why the two-step deposit? The LayerTwo-Labs enforcer only credits deposits that spend real, spendable UTXOs. Coinbases don't qualify; embedding the deposit directly in the coinbase results in a stranded output. Standard drivechain mining pools all route through a pool BTC wallet.

Connect a miner

stratum+tcp://stratum.ecashpool.io:3334
username:  <your-Thunder-address>[.<rig_label>]
password:  (ignored — any value)

The username must be a valid Thunder address — base58 of a 20-byte hash, e.g. 3Z6z1hPySNkFeB7HiKPCgqu4TZez. Generate one with thunder-cli get-new-address on any Thunder node. Using a Bitcoin address is rejected with "invalid thunder address" and no shares accrue. The optional .<rig_label> groups multiple rigs paying the same address as separate rows on the per-worker page.

Which port to connect to

stratum+tcp://stratum.ecashpool.io:3334   individual miners — difficulty from 1, vardiff follows your rig
stratum+tcp://stratum.ecashpool.io:3335   rented or aggregated hashrate (braiins) — difficulty 65,536, held
stratum+tcp://stratum.ecashpool.io:3336   rented or aggregated hashrate (nicehash) — difficulty 500,000, held

Which port you use does not change what you earn. Work is credited by its difficulty, so one share at 65,536 counts exactly as 65,536 shares at difficulty 1. The ports differ in the size of the unit, not in its price.

They exist because one difficulty cannot serve both kinds of miner. Rented hashrate does not arrive as a crowd of small rigs — a marketplace aggregates a whole fleet behind a single connection, and 1 PH/s at difficulty 1,024 is already about 227 shares per second down that one socket. On a port meant for a home ASIC the same fleet is hundreds of thousands per second: the pool limits the connection, and what the marketplace sees is a pool rejecting its work.

Vardiff cannot repair that after the fact. It moves by at most 4× per window, so climbing from 1 to 65,536 takes eight windows — around four minutes — and the rejects on the way up are what gets an order cancelled. The connection has to arrive at the right difficulty, which is what the second port is for.

A port with a held floor keeps it even when the chain is easier than the floor, because a marketplace measures the difficulty on the wire and cancels an order served under what the port advertised. When that happens your miner discards solutions the chain would have accepted, so mine on a floored port only if something is actually requiring it of you. This pool is not in that position right now.