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 0x6f2a9de6fad4b817621b6830756d8895aed535a94c5e412aa4efa0c2d08714b8. Chain 2 (Bitcoin): anchored in block 954066 (2026-06-17T08:11:48Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/613e9e3c-f10e-49dd-8568-10795bd05060.json and https://artists.proofprofile.net/proofs/artist/613e9e3c-f10e-49dd-8568-10795bd05060.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 0xaa83f351bbf9fb559cfa07963c033f12b285b1820b1d4b7b3dc17c239abbca87. Chain 2 (Bitcoin): anchored in block 958607 (2026-07-18T21:01: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/KRA252302008.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa20bf3c71c7b6e9b9fdb372593a474e0b98d33dfcc47aff8a145cef2ab0141fe. Chain 2 (Bitcoin): anchored in block 958716 (2026-07-19T10:15:55Z), 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/KRMIM2430005.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x553ed8269d4a312408759fa201bd7405ad770897852f66c1eecc3db80fb55833. Chain 2 (Bitcoin): anchored in block 958746 (2026-07-19T15:36: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/KRMIM2506427.
Drive or Die (For The More X WEEKEND IN TAIPEI)
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x1ab47516544c49e94316e59bd63b1f8a19ce8534f6df59ae197ebfdfa1614042. Chain 2 (Bitcoin): anchored in block 956420 (2026-07-03T00:42: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/KRMIM2524226.