1. Compute SHA-256 of OTSCanonicalRecord value → must equal OTSHash 2. Open OTSProofURL → extract Bitcoin block number → must equal OTSBitcoinBlock 3. GET OTSBitcoinBlockVerifyURL → returns the Bitcoin block hash at height OTSBitcoinBlock; GET https://blockstream.info/api/block/{that hash} → its timestamp must match OTSTimestamp 4. Read CopyrightID inside OTSCanonicalRecord → must equal the CopyrightID above 5. GET OTSVerificationAPI → pre-computed 6-check result from server 6. If all match: this entity was registered on CopyrightChains at OTSTimestamp, independently verifiable on Bitcoin
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9f9b2c118ae799ff1f446d19fe0b25251511317aed685893dfea1d12d4e31490. Chain 2 (Bitcoin): anchored in block 954346 (2026-06-19T03:51:26Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/95867de5-16a6-4be8-98de-a208ca7fb379.json and https://artists.proofprofile.net/proofs/artist/95867de5-16a6-4be8-98de-a208ca7fb379.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
1. Confirm isrcCode identifies the recording in the pre-2022 source corpus and cc-db-prod record 2. GET OTSVerificationAPI → server-side canonical-record, hash, and attestation checks must pass 3. GET OTSBitcoinBlockVerifyURL → returns the Bitcoin block hash at height OTSBitcoinBlock; GET https://blockstream.info/api/block/{that hash} → its timestamp must match OTSTimestamp 4. Confirm CopyrightID is the CopyrightChains transaction hash 5. If all match: the cc-db-prod record is independently anchored on Bitcoin at OTSTimestamp
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x229b7a5bd248898e777ff3156d37103155cf1154d733153fb7dfc5cb5ecb7e06. Chain 2 (Bitcoin): anchored in block 956826 (2026-07-05T19:27:56Z), registered by our registry partner. The server verifies the private canonical record against OTSHash without exposing internal provider keys. Confirm the public ISRC, CopyrightID, and Bitcoin evidence via https://artists.proofprofile.net/api/v1/bot/ots/verify/track/QZHN62455529.
Is this how it's supposed to be? (Radio Edit)
Is this how it's supposed to be? - Radio Edit
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xd0258c6d1b648de1a41048852f8a41d173663a1c3619524bf296f75879a839a6. Chain 2 (Bitcoin): anchored in block 956826 (2026-07-05T19:27:56Z), registered by our registry partner. The server verifies the private canonical record against OTSHash without exposing internal provider keys. Confirm the public ISRC, CopyrightID, and Bitcoin evidence via https://artists.proofprofile.net/api/v1/bot/ots/verify/track/QZZ7P2410971.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb3c4910e5e5783eba706ebf2374c44dd7aa7547382b76a2386098c9fa4d43ec9. Chain 2 (Bitcoin): anchored in block 958690 (2026-07-19T07:14:39Z), registered by our registry partner. The server verifies the private canonical record against OTSHash without exposing internal provider keys. Confirm the public ISRC, CopyrightID, and Bitcoin evidence via https://artists.proofprofile.net/api/v1/bot/ots/verify/track/QZDA82573328.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x1db130e65527062bce3f2d0ed9f142e2a37349d6549daaf9510892ab637accc0. Chain 2 (Bitcoin): anchored in block 956728 (2026-07-05T01:43:49Z), registered by our registry partner. The server verifies the private canonical record against OTSHash without exposing internal provider keys. Confirm the public ISRC, CopyrightID, and Bitcoin evidence via https://artists.proofprofile.net/api/v1/bot/ots/verify/track/QZNWR2565570.