Leighton may refer to: Places In Australia: Leighton, Western Australia, a beachside locality In the United Kingdom: Leighton, Cambridgeshire Leighton, Cheshire Leighton, North Yorkshire Leighton
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 0x32678e4cf541f11109b539871b0d469e93ab2df7bbc48c329c519420872582cb. Chain 2 (Bitcoin): anchored in block 954065 (2026-06-17T08:10:43Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/50d4ae2f-fb0b-4bab-9751-faacf405badd.json and https://artists.proofprofile.net/proofs/artist/50d4ae2f-fb0b-4bab-9751-faacf405badd.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 0x96b38fa86d9bfa9e7fe3dce62bf709aa9e77939e157b1a69e1622598d5629ad1. Chain 2 (Bitcoin): anchored in block 959023 (2026-07-21T15:22: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/GB8KE2213751.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x93c53069726827bfcb1c41f29a2d1fcd47534c43e84a3b49207cc8c10717ebe7. Chain 2 (Bitcoin): anchored in block 958224 (2026-07-16T02:28:43Z), 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/GB8KE2308198.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x11b2e1592f932d9e9cdc0b602cdffde53f80fee4421ff81f788a6620bd4ab3b5. Chain 2 (Bitcoin): anchored in block 958420 (2026-07-17T13:33:01Z), 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/GB8KE2425587.