One block has exactly one payee, by construction

The validator pays one address per block, and the coinbase carries exactly one address field. A reward cannot be divided on chain at all — not as a policy choice, but because there is nowhere in the header to write a second recipient.

So a poolAn operator that aggregates many miners' work, commits its own address in every coinbase, and pays miners out of what it collects. here is an operator that commits its own address in every coinbase, keeps an off-chain record of who did the work, and pays miners by ordinary Cardano transfers.

whitepaper §8

What each path actually asks of you

Pool
One config change and nothing else, ever. The operator runs the Stratum server, holds the hot wallet that signs winning blocks, pays the Cardano fee on every block that lands, and transfers your cut to your address. You are trusting their share accounting, which is true of every pool on every chain.
Solo
You run the WHAT miner software yourself: a Stratum server beside a Cardano node or light client. You hold a hot wallet for fees and for collateralADA a Cardano script transaction puts up in advance, forfeited only if the script fails while running. — ADA a Cardano script transaction puts up in advance and forfeits only if the script fails. You pay about a third of an ADA in fee per block that lands, and the reward goes to the address committed in the header, which can be a cold wallet with no connection to the hot one. Nobody takes a cut and nobody has to be trusted.

Both paths hash exactly the same jobs. The only difference the protocol sees is which address the coinbase commits to. See the two fields either path needs.

whitepaper §8

Running an endpoint, private or public

The software is the same either way: a Stratum server beside a Cardano node or light client, a hot wallet for fees and collateral, and the block transaction the validator checks. Pointing it at your own rigs makes it private; accepting other people's addresses makes it public.

What a public endpoint spends is the Cardano fee and the minimum ADA on every reward output it creates for somebody else — about 1.8 ADA a block, where where a block reward lands has the breakdown. How an operator recovers that, out of its fee or a prepayment, is its own arrangement and nothing the validator knows about.

Nor can that be abused: an operator only ever spends when somebody actually finds a block, which costs real electricity, so connecting with a million addresses drains nothing.

Paying miners takes no validator at all. A payout is an ordinary transfer, so a batch is one Cardano transaction with one output per miner, each carrying its own minimum ADA — which goes to the miner — and nobody has to be online to be paid. An operator that would rather split a reward on chain can commit a contract's address instead and let it divide what arrives.

whitepaper §8

The fee is not verifiable on chain

A pool's fee is the difference between what it collected and what it credits. The chain never sees sharesA submitted solution that meets a pool's own easier threshold, used as the unit for accounting who did the work., so it cannot check a fee taken against them. That trust comes with pooling, here as anywhere else.

What the chain can show you is the other half: every block that landed, which address it paid, and every transfer out of that address. So the pool's intake is public and its own payouts are public. The private part is the share ledger that connects them.

Which brings up the number a pool and a solo miner are both deciding on.