# CSD addr20 records across different mining pools

The same addr20 identifier does not merge pool ledgers. Shares, unpaid amounts and payment history remain source-specific. Changing a miner endpoint does not transfer a G-pools balance into another pool.

- Canonical: https://iotahome.site/en/learn/csd-change-pool-addr20-ledger
- Publisher: IOTA Watch
- Topics: Compute Substrate
- Published: 2026-10-26
- Updated: 2026-10-26

## At a glance

The same addr20 identifier does not merge pool ledgers. Shares, unpaid amounts and payment history remain source-specific. Changing a miner endpoint does not transfer a G-pools balance into another pool.

## What to check

Save the complete public 40-hex identifier, old pool, change time and outstanding balance. Verify the new pool’s supported format and statistics endpoint. Substrate SDK documentation does not establish Compute Substrate pool rules. For a source outside this integration, keep the original pool link and reconcile there.

## Example

Example: old-pool unpaid 5 and new-pool accrual 1 are separate source records. After payment, the receiving wallet balance is not a third mining reward to add again.

## Continue

[Open project monitor](https://iotahome.site/en/projects/csd)

## Sources and implementation

- [computesubstrate.org](https://computesubstrate.org/)
- [csd.yamaduo.no](https://csd.yamaduo.no/)
