BLVCK MINDZDOCS
Try demo ↗GitHub ↗

BLVCK MINDZ × NEAR / Agreements & shares

The identifier locates the track. The agreement sets the shares.

A recording and a composition are different assets. Their rights and revenue routes must be kept separate.

ISRC and ISWC

ISRC identifies a recording; ISWC identifies a composition. Neither code establishes who owns a right or what percentage each collaborator should receive. The participant sheet and applicable agreements provide that context.

Two layers of allocation

The sample first allocates the label’s agreed share. It then applies the collaborators’ weights to the remaining pool.

Recording sample:
Label: 40%
Artist: 60% × 70% = 42%
Beatmaker: 60% × 30% = 18%
Total: 100%

These are demonstration terms, not statutory percentages or approved commercial terms. Point allocation uses the largest-remainder method. Money uses integer micro-units and a separate remainder rule.

Five distinct revenue flows

FlowPrototype coverage
Master · ISRCRecording example: 2.00 test tokens.
Producer neighboring right · ISRCRecorded in the sample model; no invoice demonstrated.
Performer neighboring right · ISRCInformational external route; no collection or payout implemented.
Publishing performance · ISWCSeparate composition example: 1.00 test tokens.
Publishing mechanical · ISWCRecorded in the sample model; no invoice demonstrated.

These are not five slices of one invoice. Actual routes depend on rights, mandates, territory and agreements.

Read the full revenue template ↗

Documentation maintenance · 16 November 2026 · Source and scope