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 0x0a71232f3119fcc0584c5eca070ec526109b33aeb8af20c6fdc6cd6a578b00c7. Chain 2 (Bitcoin): anchored in block 953877 (2026-06-16T02:39:16Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/03928100-8b3c-4dc3-8b6f-8c2a9982a1f4.json and https://artists.proofprofile.net/proofs/artist/03928100-8b3c-4dc3-8b6f-8c2a9982a1f4.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
So we've heard the comet strike...what now?
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 0xa474368d5dc666f276e1abf1e07c5dd36716b9ac1fb4b5b19742021e20eb668b. Chain 2 (Bitcoin): anchored in block 956857 (2026-07-06T01:26:17Z), 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/QZWFQ2584786.