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 0x437d2f13e233228780306afcf2f4d177f768adf61308439d5060c6490ce30281. Chain 2 (Bitcoin): anchored in block 953750 (2026-06-15T06:12:23Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/ab291c95-a5b8-4e15-a863-35e7769c20dd.json and https://artists.proofprofile.net/proofs/artist/ab291c95-a5b8-4e15-a863-35e7769c20dd.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 0xf00bfc2ad12910512af09833b4019086f0dbfa5c0656cfdd9e78d884fda85f6c. Chain 2 (Bitcoin): anchored in block 958774 (2026-07-19T22:23:47Z), 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/JPPC02211556.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xebefbedee7021b47482dbb2ed5c012d33ec4b03afbef361381fc5533e83a2f6f. Chain 2 (Bitcoin): anchored in block 956476 (2026-07-03T09:04:44Z), 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/JPPC02112026.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xf5615b9752ebd8d5e7b73157d2061daa3d86b7536487b0c3573ae9117b8e993c. Chain 2 (Bitcoin): anchored in block 957073 (2026-07-07T18:39:05Z), 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/JPPC02210026.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xf5615b9752ebd8d5e7b73157d2061daa3d86b7536487b0c3573ae9117b8e993c. Chain 2 (Bitcoin): anchored in block 953536 (2026-06-13T17:25:41Z), 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/JPPC02210026.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa43b959bc296e00ee37d72aa337c90b33942e0c641f82072bce4dbf0112b7f48. Chain 2 (Bitcoin): anchored in block 959132 (2026-07-22T13:20:46Z), 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/JPPC02111723.
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