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 0x77273ed8cb502904ec33826bf1b7d857a5b72621c0fcdebe166711963d9a7596. Chain 2 (Bitcoin): anchored in block 953695 (2026-06-14T21:42:01Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/71ca21f8-602e-48ed-b834-f86bab5dfc5a.json and https://artists.proofprofile.net/proofs/artist/71ca21f8-602e-48ed-b834-f86bab5dfc5a.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Something That Leads Me To You (Remix EP)
Something That Leads Me To You (Remixes)
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 0x60c904f156591e598d8acafc60e163046ea24415ef71b8b2185bf2dd827be63c. Chain 2 (Bitcoin): anchored in block 956474 (2026-07-03T08:56:35Z), 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/TLVEM2464376.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x0cfa9de6d784c647034d1677f14b0e36ef4662bfad75d2f6fc44cea1998d99be. Chain 2 (Bitcoin): anchored in block 958153 (2026-07-15T12:03:04Z), 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/QZPEW2524502.
I see you patiently wait to watch me bleed
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x8f673cc3274ffebae319f3a00289d0b48701bd9421fe41b3dc8c015fc8f0ebf9. Chain 2 (Bitcoin): anchored in block 956826 (2026-07-05T19:27:56Z), 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/QZES82551674.