BLVCK MINDZ × NEAR / Limits & trust
What this demonstration does—and what remains open.
Use these boundaries when interpreting the result or reviewing the code.
Demonstrated scope
- Local calculation and fixed-sample testnet distribution.
- Recipient-level payment proof and saved-run recovery.
- Rejection of another distribution on the same paid batch.
Not delivered by this demo
- Commercial streaming revenue collection or payment.
- Legal verification of ownership or registration with collecting societies.
- Email sign-in and artist-controlled browser authorization.
- Economic deduplication across separate invoice IDs or networks.
- Complete failed-callback recovery.
- Cross-chain settlement.
Operator powers and public data
The operator prepares the sample accounts and confirmations, holds isolated testnet signing keys and can approve the fixed sample. This is not a demonstration of independent control by each artist. The implementation supports part of NEP-171; it does not implement token transfer. The payout receipt is an event, not a separate NFT.
Payment accounts, amounts and transfers are public. Keeping a document hash on chain does not make the payment private. No recovery phrase or private key is needed to read these docs or inspect a receipt.
What needs validation next
Clean source reproduction, participant authorization, exception recovery and reconciliation of an authorized pilot are the next technical and operational milestones. Measured time savings and repeat external use are still hypotheses to test.
Documentation maintenance · 16 November 2026 · Source and scope