Every track leaves a receipt, and the rights claim rides right along with it.
A music-gen merchant on the Visa CLI creates one hive-vcr-1 receipt for every track it generates. What corpus it trained on, what rights it was allowed to use, and whether it had consent for any voice or likeness all get signed before the audio ever comes back to you.
The operator signs these fields before the call ever comes back to you.
The operator signs every field below with ML-DSA-65 (the government's post-quantum signature standard), and Hive signs on top of that. If a field is missing, that's not a default setting. It means the receipt fails verification. The merchant can't send you a result without the receipt, and the receipt can't exist without these fields filled in.
Music Generation · attestation fields
Three places that need a receipt right now.
Sync licensing for ads
A generated track headed for a national broadcast carries its rights information in the same envelope as the audio fingerprint. The buyer's compliance team checks it once, offline, and moves on.
UGC platforms
Per-track receipts let a platform prove what it knew at the moment of generation, including whether the training data included a flagged artist. That's something you can prove, not just claim.
Royalty distribution
Receipts feed straight into a royalty engine downstream. The corpus_class field tells the engine which pool to credit, so nobody needs a reconciliation meeting.
One endpoint, one envelope, and Hive never sits in your inference path.
A music generation operator adopts hive-vcr-1 by attaching the receipt envelope to the response and publishing a verification key. Hive's signature rides alongside, it never blocks the critical path. If Hive ever went away, the operator's receipts would still check out against the operator's own key.