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 0x81bac70db37aad2acbc63827b3fa5b6adf30ac3b3e2cc2fec46b38a67dbd660c. Chain 2 (Bitcoin): anchored in block 954028 (2026-06-17T01:08:06Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/395e3279-f4a5-4b80-8288-c5cb16bd1920.json and https://artists.proofprofile.net/proofs/artist/395e3279-f4a5-4b80-8288-c5cb16bd1920.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Spend a little more time trying to make something
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 0xa64c55176ba063704c4b4fdd331bb0c195b307bbe5b646950fe23be5dcb587a4. Chain 2 (Bitcoin): anchored in block 958335 (2026-07-16T22:37:47Z), 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/BK4DA2519586.
Oh yes, the past can hurt. But the way I see it
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x03eb916b93c51d2f84f57cdf2bf51142d727df68e6f594d3e29fac83c09e52a7. Chain 2 (Bitcoin): anchored in block 958489 (2026-07-18T04:13:26Z), 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/BK4DA2519587.
No one has ever made a difference by being like everyone else
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x66735cc45d8473c7e25cd0350b31b004996bf40c0b22562d0ab5b66303fe4089. Chain 2 (Bitcoin): anchored in block 958793 (2026-07-19T22:59:45Z), 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/BK4DA2519588.
It isn’t where you came from. It’s where you’re going that counts
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9f019aaaa11662d5a60efdf6dfedfdffc6eaef629266645b2431bcd50072a37a. Chain 2 (Bitcoin): anchored in block 958857 (2026-07-20T09:45:25Z), 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/BK4DA2519589.