BLVCK MINDZBLVCK MINDZBuilt for NEAR HACKATHON
Real-World Money · Testnet
Music payment operations

Streaming income.
Shared as agreed.

One song’s payment, shared by the label, artist and producer.

Try a prefilled streaming-statement sample.
Test tokens on NEAR. No wallet setup.

01 / One track · sample agreement

Split a payment.

Identifies the recording. The agreement sets the shares.

Participants & agreement

Label · performer · music producer

The label’s sample allocation is 40%; the remaining 60% follows these contributor weights. The publishing sample uses a 25% allocation.

Local calculation. No tokens moved.

Testnet execution requires the new demo deployment.

Ready to run01 / 04

Follow the payment.

Start with a simulation. Then run a real testnet distribution.

Payment to allocate2.00 TEST USDCISRC · PYXXX2600001
Agreed sharesLabel · artist · producerOne agreement, applied to every payment.
Label——Expected
Artist——Expected
Beatmaker——Expected

    Simulation explains the split. Testnet provides the proof.

    02 / NEAR testnet evidence

    Check the payment.

    Expected amounts beside the amounts recorded on NEAR.

    Full evidence report ↗

    Public transaction data. No wallet needed.

    Recorded testnet payment · test tokens have no monetary value. See the build report for source/deployment correspondence.

    One track. Five revenue flows.

    The recording and the composition have distinct identifiers and agreements. Each flow has its own source and allocation; they are not five slices of one invoice.

    BLVCK MINDZ prototype template · sample terms
    Revenue flowIdentifierPrototype treatment
    MasterISRC · recordingLabel share + artists’ side. Main invoice example: 2.00 test USDC.
    Producer neighboring rightISRC · recordingAssigned to the label in this sample model. No invoice demonstrated for this flow.
    Performer neighboring rightISRC · recordingInformational only. External collection/payment is not implemented or verified here.
    Publishing: performanceISWC · compositionPublisher share + writers’ side. Additional example: 1.00 test USDC.
    Publishing: mechanicalISWC · compositionPublisher share + writers’ side. No invoice demonstrated for this flow.

    A code identifies a recording or composition; it does not establish ownership. Real allocations and collection routes require verified agreements and applicable territory/mandates. The prototype does not collect from distributors or societies.

    Interoperability

    Independent test payments on two networks. Cross-chain settlement is planned.

    Read the Solana / NEAR scope →

    Inspect the registered rights, confirmations and batch history

    Rights and shares

    —

    Invoices

    —