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 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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0cc1e9b5968c1fabeea882a1299ad60e9ed3611fdda03dad431fb6eb303f1665. Chain 2 (Bitcoin): anchored in block 954516 (2026-06-20T07:04:44Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/a1a0838f-b00e-4414-9b41-7c612fd4d310.json and https://artists.proofprofile.net/proofs/artist/a1a0838f-b00e-4414-9b41-7c612fd4d310.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
I Felt Like I Had a Little Bit of An Understanding
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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x82929971acd8108dd78ca086aca2f81874e99f666d53b86cb93b2698e35421a8. Chain 2 (Bitcoin): anchored in block 958924 (2026-07-20T18:54:07Z), 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/AEA2L2130828.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xe4a6c4606d2bedf3b20fb489c2caa39278d46b97b5555513ecfd948b644e4323. Chain 2 (Bitcoin): anchored in block 958523 (2026-07-18T08:54: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/AEA2L2145702.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb800d1fedc251f22b043586685ca5e555d368c06556656819e2159f7e1a9077b. Chain 2 (Bitcoin): anchored in block 957776 (2026-07-13T00:05:10Z), 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/AEA2L2158203.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xba5b6e41400c68fcfb2e6e6ea6600c60ec0e3b80f5cc888caaed42bc7f1dc33d. Chain 2 (Bitcoin): anchored in block 957782 (2026-07-13T00:52: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/AEA2L2170967.