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 0x0d7a594c66c2c46a6b5b7d6977c1f46b9c05a338d9347a72a439b927ba0bb114. Chain 2 (Bitcoin): anchored in block 953758 (2026-06-15T07:48:25Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/b34a7d9b-dc77-467a-bf75-1a3b1b6e5f6c.json and https://artists.proofprofile.net/proofs/artist/b34a7d9b-dc77-467a-bf75-1a3b1b6e5f6c.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 0xb2fc61a7fee399f3c4309535377e9354c5192be36d27cc5bb1358ff65c94ecef. Chain 2 (Bitcoin): anchored in block 958765 (2026-07-19T20:40:30Z), 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/JPTE01606240.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x407a2a142f4a4c8b95736b762765a7f874eaab18318619e85d4c98727b1db772. 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/JPPO01155739.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x318a68899cb8b245454b6d048501e05b76e9a0ba9946672f58342a7674221a17. Chain 2 (Bitcoin): anchored in block 960459 (2026-07-31T20:22: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/JPBV00800184.
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