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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3542bdd8f6104b65e1f491fafe2f7d0189065594afe69965d0a51114ac853413. Chain 2 (Bitcoin): anchored in block 953407 (2026-06-12T19:24:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/d8f88f0a-8257-4a05-b0f1-3cb3dbb7b071.json and https://artists.proofprofile.net/proofs/artist/d8f88f0a-8257-4a05-b0f1-3cb3dbb7b071.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Vem Jogando Xerecão no Baile do Vermelhão
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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xf7e01d72fbc0ccfaf6630c2cd8b66515b192458d7ce8427fe90a451b0aa7fd92. Chain 2 (Bitcoin): anchored in block 956312 (2026-07-02T05:09: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/QZW9K2221641.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x036ee252d9d0db50cdc5f424dc72e3255f1eea6808a1fd574f606e3bf26f4249. Chain 2 (Bitcoin): anchored in block 957118 (2026-07-08T03:20:19Z), 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/BCJR62000008.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x78a8c0329a4fe8849bfb92798aaee573aa9f197c8d476cc05b05226a3cda78a9. Chain 2 (Bitcoin): anchored in block 956302 (2026-07-02T03:30:09Z), 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/BRUM71802659.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xdf31376f0a174ebfb8e688b03a4d56028e3a732bc7f7f16fc7b7d0c5bf87cbc4. Chain 2 (Bitcoin): anchored in block 960273 (2026-07-30T15:42:38Z), 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/QZ5AB1972786.
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