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 0xf52a1cae34f4961defffe2666209496ca4ee742a915463075c779b75f7de7e4a. Chain 2 (Bitcoin): anchored in block 954650 (2026-06-21T04:51:12Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/d94541b9-8921-4c1d-90fc-b42372f95e1b.json and https://artists.proofprofile.net/proofs/artist/d94541b9-8921-4c1d-90fc-b42372f95e1b.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
J'ai aimé, j'ai souffert, maintenant je hais
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 0x160eff6fbd1f11cf64b1233821f12cd488bdeab6800bfb614bb074e41f7c73f0. Chain 2 (Bitcoin): anchored in block 957820 (2026-07-13T07:54:01Z), 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/CAA0Q1522304.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x82671ca367c34fbf7efc8a93b433cc5024140e0e7ae9e07c5edbbc9edc8de93e. Chain 2 (Bitcoin): anchored in block 957020 (2026-07-07T09:18:01Z), 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/CAA0Q1312117.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x7a6cbd739b33cbf3e743ec98257fe43736bfb33d20f68680db489eaaad7628ac. Chain 2 (Bitcoin): anchored in block 960150 (2026-07-29T21:51: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/CAA0Q1312114.
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