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 0xc8c698d8a90ae693f7d6eb5689fa900195befe366c6f6cecaf0358196c118f75. Chain 2 (Bitcoin): anchored in block 953827 (2026-06-15T19:59:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/f5f2b4c5-52d3-42e9-ba8d-14b5ca80fb18.json and https://artists.proofprofile.net/proofs/artist/f5f2b4c5-52d3-42e9-ba8d-14b5ca80fb18.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 0xdcab4067cd76ff4b0bcfd780c8eb032b77bb79e8688345e7c65f0c1b3de2855a. Chain 2 (Bitcoin): anchored in block 953528 (2026-06-13T15:41:10Z), 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/USG9K1600013.
I LIE HERE BURIED WITH MY RINGS AND MY DRESSES
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xf6a389620cc44ef63fa9e0b69eb32556cd2986e2c5a5888d4a3140b98c68bccb. Chain 2 (Bitcoin): anchored in block 956302 (2026-07-02T03:30:09Z), 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/QZHNA2143502.
You Think It's Like This But Really It's Like This (20 Year Anniversary Reissue)
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x206f410a113c82bd05ba5989f29aaf06497ced810d81ce2b213afc9d9792f01b. Chain 2 (Bitcoin): anchored in block 960108 (2026-07-29T13:09:35Z), 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/QZAZS2006904.
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 Note: an OTS proof may carry multiple Bitcoin attestations; OTSBitcoinBlock is the earliest confirmed one — a later attestation inside the proof corroborates it and is not a mismatch