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 0x5528ac3bca32d909e84dc1f594c8563351e25a160a68ae56503b6518f659181f. Chain 2 (Bitcoin): anchored in block 953724 (2026-06-15T01:43:13Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/8e29fe6b-34cc-4c5a-829d-db2c6621accb.json and https://artists.proofprofile.net/proofs/artist/8e29fe6b-34cc-4c5a-829d-db2c6621accb.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Coro Hermandad Nuestra Sra. Del Rocio De Triana
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 0xa054573eba4cc0a756729e3ab4f594e767f21dd2a79f345c2319c15138be71ad. Chain 2 (Bitcoin): anchored in block 953528 (2026-06-13T15:41:10Z), 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/ES5029600131.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xa054573eba4cc0a756729e3ab4f594e767f21dd2a79f345c2319c15138be71ad. Chain 2 (Bitcoin): anchored in block 953520 (2026-06-13T13:32: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/ES5029600131.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x92777a4c62e9b7318a732f7fd129493351546761082e1adeee3ea3438828c0b9. Chain 2 (Bitcoin): anchored in block 960344 (2026-07-31T04:14:58Z), 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/ES5029600119.
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