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 0x5a9b73580c70e78296f34580691ee20a6310f886293aa4e6b65813bb0d67a260. Chain 2 (Bitcoin): anchored in block 954549 (2026-06-20T10:56:20Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/ab3d6337-5f59-4c70-ae58-b92ae23dfc98.json and https://artists.proofprofile.net/proofs/artist/ab3d6337-5f59-4c70-ae58-b92ae23dfc98.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 0x7941806214485abe659df29faf81401f84b4db8c73e4fabafbea41ac9af1e5cd. Chain 2 (Bitcoin): anchored in block 958891 (2026-07-20T13:27: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/QMDA71593156.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xff0fcfbdd55fee2c574c45fea5b08e425dcc1ccf9595a2f55365a5625c195804. Chain 2 (Bitcoin): anchored in block 958943 (2026-07-21T00:27:37Z), 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/QMDA71593159.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x63b90e18be91a5a1fa37ce9a47580c0b93341cf03a18c1b04612626c097703aa. Chain 2 (Bitcoin): anchored in block 959063 (2026-07-21T21:45: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/QMDA71593162.
Jooy-E Noghre-Ye Mahtab (Duo for Setar & Tombak)
Jooy-e-Noghre-ye-Mahtab(Duo for Setar & Tombak)