Output distribution

Counts, heights and output indices

The get_output_distribution daemon method can return counts across a height range, including a cumulative representation. The caller must interpret the starting height and base count correctly instead of treating each cumulative value as the count for one block.

For RingCT outputs, the public amount category is zero. That is a protocol classification used for indexing confidential outputs. It does not mean those outputs contain zero XMR.

References: Daemon RPC reference · Monero source: wallet/wallet2.cpp

Distribution is not the selection policy

The distribution describes what output history is available. The wallet selection algorithm determines how it samples that history and handles unusable candidates. The two have different jobs.

An accurate table alone cannot guarantee a good anonymity set. The age model, available outputs and observer knowledge can all affect how plausible the selected ring members appear.

References: Monero source: wallet/wallet2.cpp

Example

A wallet samples an age according to its decoy-selection algorithm, then consults output counts to find candidates from the corresponding part of the chain. The counts are not balances or amounts received by named people.

References: Daemon RPC reference · Monero source: wallet/wallet2.cpp

Limits and cautions

Distribution data does not identify which outputs are unspent. Monero key images prevent double spending without publicly marking the actual spent output in each ring. A remote daemon can also supply misleading data, so requesting a distribution is not a trust guarantee.

References: Daemon RPC reference · Monero source: wallet/wallet2.cpp