Payouts and royalties

Where events come from

A usage event — play, rewind, purchase — is fixed by a §7.1 receipt signed by the subject's device key. Receipts enter the journal in batches, get confirmed and become the basis for settlement. "Confirmed" means the event counts in stats and payouts.

How it's calculated

• Protocol prices are set in minor units (kopecks) — no rounding drift.
• The obligation is split by the NDT manifest splits (Σ=100).
• Cascade: if a split has the parent role (wallet isrc:…), that share is re-split by the parent track's manifest — up to 10 levels deep.
• Multi-currency: events in different currencies accumulate as separate obligations; if no payment rail exists for a currency, the obligation is marked no_rail and waits.

Where the money goes

The base rail is SBP (Russia). Planned: the digital ruble and, for the international circuit, adapters for UPI (India), Pix (Brazil), CIPS (China). The protocol issues no tokens and pays no gas: rails are national, the transactions are banking.

Where to look

• Cabinet → Payouts: totals per currency, obligation history.
• Operator: the settlement worker closes the obligation queue; payout receipts are fixed in the registry (audit trail).

Disputes

NDP is not an arbiter: the math is transparent and verifiable, but legal claims are resolved between rights holders. The protocol provides the evidence — priority, splits, event history.