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 0xa0b19e0042cdd95dd0a3557138311c556475e1dcf9f318068ffac4fecd907fcf. Chain 2 (Bitcoin): anchored in block 954638 (2026-06-21T03:45:44Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/d56eb84e-fe01-4180-9411-468adcc89cb4.json and https://artists.proofprofile.net/proofs/artist/d56eb84e-fe01-4180-9411-468adcc89cb4.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 0xa7ebd4c5c01b94a4d7edefe0a1e636aaea55824bfb36c1ad7a3ee22c23761ad4. Chain 2 (Bitcoin): anchored in block 956351 (2026-07-02T11:38: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/GBAYC1501752.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9571dde670bff65675c3496294ece60dc7ca41dc72776ba1a53cb7eb51de4dc5. Chain 2 (Bitcoin): anchored in block 957041 (2026-07-21T17:26:11Z), 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/GBAYC9500544.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc4dd03b5b30f438aea19f964a3f770dbf96b8f2d39a65a8459d819251826ee96. Chain 2 (Bitcoin): anchored in block 960300 (2026-07-30T19:42:40Z), 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/GBAYC1501759.
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