NormalDance Protocol · sovereign music infrastructure

Rights infrastructure for the multipolar music world

Every audio file carries its own passport: a perceptual fingerprint, a machine-readable rights manifest, and verifiable priority. Settlement flows over your national payment rails — not through a single Western chokepoint. Data stays in your jurisdiction.

Verify a track API reference

256 bytesperceptual fingerprint — robust to re-encoding, pitch and tempo shifts
≥ 0.95similarity of transcoded copies; foreign threshold < 0.75
~0.03 sfragment localization inside a mix (ADNA v2)
241tests green across registry, CLI and contracts

The gap

Artists in BRICS+ countries lose revenue to platforms that don't speak their payment rails, don't respect their data jurisdiction, and don't read rights from the file.

Western platforms, Western rails

Spotify, YouTube and sample libraries settle through SWIFT, Stripe and US banking. An artist in São Paulo, Mumbai or Johannesburg waits months for payouts that lose 15–30% to intermediaries.

Rights locked in PDFs

License terms are unreadable by machines. No player, label pipeline or AI service can answer: who owns this, can I use it, what does a derivative cost?

Detection ≠ settlement

Content-ID tools identify audio and issue takedowns. Nothing in their stack routes money to the rightsholder — especially across borders where the rails don't connect.

How it works

  1. Identification — perceptual fingerprint

    A 256-byte spectrogram fingerprint robust to re-encoding, format conversion, pitch and tempo shifts of ±8%. Numeric verdicts frozen by spec: ≥0.90 — same track; 0.75–0.90 — derivative; <0.75 — different. Windowed v2 signatures find fragments and cuts, with per-source attribution for multi-sample works.

  2. Rights manifest inside the file

    Every work gets an NDP-ID and an NDT manifest: authors, splits, license tier — embedded in the audio itself. Derivative chains are stored in the registry; a paid derivative automatically compensates every upstream contributor, up to 10 levels deep.

  3. Cascade settlement over your rails

    A usage event → fingerprint check → splits computed to the cent → payouts routed over the payment rail of each participant's jurisdiction. NDP is the settlement-logic layer; money moves on existing national infrastructure.

Payment rails for BRICS+

NDP is rail-agnostic by design. Each participant settles on the instant-payment infrastructure of their own country — no single chokepoint, no currency hegemony.

RailRegionStatus in NDP
SBP / Digital RubleRussiaproduction pilot
UPIIndiaintegration-ready
PixBrazilintegration-ready
CIPSChinaintegration-ready
local instant railsUAE, Egypt, Ethiopia, …adapter layer

The settlement engine computes obligations in minor units and routes each payout to the appropriate rail. Adding a new rail is an adapter, not a protocol change.

Data sovereignty

Your jurisdiction, your rules

Personal data is stored as cryptographic commitments — never raw. The registry can be deployed in-country; a BRICS+ partner runs the same open protocol under their own data-protection law.

No platform dependency

The rights manifest travels inside the audio file itself. Even if NDP disappears tomorrow, the fingerprint, splits and priority timestamp remain verifiable in every copy.

Open protocol, no token

No cryptocurrency, no tokenomics, no governance by a foreign DAO. A non-profit operator in each jurisdiction can run the registry. The protocol is the standard, not the platform.

Who it serves

Artists & producers

"Scan your catalog" — every track gets a fingerprint, a priority timestamp and verified splits. When your work is sampled, remixed or synced, you get paid automatically — in your currency, on your rail.

Labels & distributors

DDEX ERN feeds land in the registry as drafts; fingerprints are registered at catalog scale. Cascade splits flow to every upstream contributor without manual accounting.

Platforms & AI services

Query rights by ISRC, identify audio by fingerprint, get a numeric verdict. 21 MCP/API tools for AI agents. Your platform clears usage by reading the file — no legal overhead per track.

Engineering readiness

ComponentStateVerified by
CLI v0.7.1worksADNA v1+v2 fingerprints, signed play receipts, offline verification, bilingual RU/EN
Registry API 0.13.0workscascade splits, multi-currency settlement, DDEX ERN import, artist ID cards
Identification oracleworksHTTP API: fingerprint lookup, numeric verdicts, per-source attribution
MCP serverworks21 agent tools (SSE + HTTP), sandbox keys, Bearer auth
Test suites241 green109 (contracts) + 128 (registry) + 4 (payments)

What NDP is not

Not a payment system

Money moves on existing national rails. NDP is the identification, clearance and settlement-logic layer on top.

Not enforcement

We provide proof, priority and a payout route — never takedowns or policing.

Not surveillance

Verdicts are strictly about rights: authorship, priority, license scope. No content policing, no traffic inspection. This boundary enables trust across jurisdictions.

Partner with us

Running a music platform, label or AI service in a BRICS+ country? Deploy the protocol in your jurisdiction.

Telegram: @NORMALDANCE API reference