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 0x5d64cfc99ab653bd2c7d88d78896d18f08b13208ec93d7dd5573149d94beb435. Chain 2 (Bitcoin): anchored in block 953654 (2026-06-14T16:26:51Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/497e61ec-f4ae-4a02-b608-c2ba44ff7e24.json and https://artists.proofprofile.net/proofs/artist/497e61ec-f4ae-4a02-b608-c2ba44ff7e24.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 0x6e9926fb5a69e5e68ea718f5974f552e67687152a3340005eaa6d017aa6f1f84. Chain 2 (Bitcoin): anchored in block 957122 (2026-07-08T03:39:04Z), 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/GBLFP2237903.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x20ac391e8c89593f0894a525e5c05ee6125337eab8237e45b28e5c70c69cb688. Chain 2 (Bitcoin): anchored in block 956304 (2026-07-02T03:55:08Z), 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/ESA011526513.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xde59aa25212838e7412e588b78f621406cf31b78111e8c89810278d447e5f7ac. Chain 2 (Bitcoin): anchored in block 956312 (2026-07-02T05:09:12Z), 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/QZN882073703.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x03f6d6d3b25e2446eba04a52df29090ccc832e4089d943538afbc8d4badc3928. Chain 2 (Bitcoin): anchored in block 956304 (2026-07-02T03:55:08Z), 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/QM4TX2232174.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3dccd4d9de60ef8a038bfa7ab921bac720c07db4ece746fd2fd035b0ee5ca352. Chain 2 (Bitcoin): anchored in block 959155 (2026-07-22T19:36:48Z), 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/QZTLA2482320.
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