1. Compute SHA-256 of OTSCanonicalRecord value → must equal OTSHash 2. Open OTSProofURL → extract Bitcoin block number → must equal OTSBitcoinBlock 3. GET OTSBitcoinBlockVerifyURL → block must exist at that height 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 0x12d0a43deb3dd8276937bbe4cb677c4f0686ebe6fad1df3b8f4532853df80b07. Chain 2 (Bitcoin): anchored in block 954569 (2026-06-20T14:36:29Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/b0bd4247-bf24-4cd4-a1b8-7934a90768d5.json and https://artists.proofprofile.net/proofs/artist/b0bd4247-bf24-4cd4-a1b8-7934a90768d5.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 → block OTSBitcoinBlock must exist at that height 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 0x65808af414f6acc74576b34dcf0e244ce18106be2f6c08e5dfe5a3659bb2ed40. Chain 2 (Bitcoin): anchored in block 956402 (2026-07-17T03:39:30Z), 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/TCAHB2373900.
I Kept Hoping It Would Get Better but It Just Got Worse