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 0xb9813360d7928b0a95ee4a0d3085da6d1abf80130cedec330650a31da6e95ce8. Chain 2 (Bitcoin): anchored in block 953592 (2026-06-14T05:36:59Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/0783078b-a667-413c-8277-f32898f6c304.json and https://artists.proofprofile.net/proofs/artist/0783078b-a667-413c-8277-f32898f6c304.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 0xe3d36e863bd7b7c3072796a7a2331bbe13be34fd1c4cea6abde131ee0ac648bb. Chain 2 (Bitcoin): anchored in block 956738 (2026-07-05T04:47:21Z), 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/JPP561100829.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9e704205db9c098a2fb0b03d12343ac84aa3145514359cd69e65b362651a2b03. Chain 2 (Bitcoin): anchored in block 956725 (2026-07-05T01:12: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/JPP561100824.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xfe2953c012204d1caa0a92f6c9103a63a16091753e2d9d49d5ab80a53f8bde98. Chain 2 (Bitcoin): anchored in block 956891 (2026-07-06T07:16:32Z), 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/TCJPZ2413587.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x37d2cb8f5f4456a79092bbf405056244b05ba5afa5aa90b9ea027110215fd27c. 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/JPP561100546.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xe8e0797f1cbdea41381352dc951860aac3b6670ec126605b595c6ad54f1b376f. Chain 2 (Bitcoin): anchored in block 960403 (2026-07-31T13:04:34Z), 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/JPP561100541.
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