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 0x06541f9cffe1b9553a8efb605243d9207f22522cb2fec1680e5c841d4236b9d2. Chain 2 (Bitcoin): anchored in block 954553 (2026-06-20T11:51:30Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/ad611359-1db3-4bc7-ad16-7f5301141309.json and https://artists.proofprofile.net/proofs/artist/ad611359-1db3-4bc7-ad16-7f5301141309.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 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 0x4f8101ae2e22fb6451530e43f4f9ea8534f9753f2e8cc02d7cdc659c28c40bca. Chain 2 (Bitcoin): anchored in block 956578 (2026-07-04T02:23:20Z), 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/TCAFQ2104812.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x4d3d83c371e57cf9ed68bf71c44a988c660ce35d5530c8f677a2893e153894d0. Chain 2 (Bitcoin): anchored in block 957770 (2026-07-12T23:17:00Z), 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/FRS182146695.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xe5070ae6202ba74b41ba95bb1bff2b6ac6cd22f0149d5d43d1a3065f94a404d0. Chain 2 (Bitcoin): anchored in block 959123 (2026-07-22T11:35:32Z), 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/FRS182146696.
Do I Need to Explain About Jakarta Prayer?
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xec7b8de3d6cc6fa206141d2ef5657639d71bac9d5ba4b1c7f3fce3e26dc9dd49. Chain 2 (Bitcoin): anchored in block 958761 (2026-07-19T17:49: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/FR59R2404155.