Keke may refer to: People Surname Harold Keke (born 1971), Solomon Islands warlord Joseph Keke (1927–2017), Beninese politician Leo Keke (1947–2012), Nauruan politician Ludwig Keke (born c. 1935)
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 0xd219c3370b5cd425bdd9fead9b5829eb68378a4c3145a82b84c4694b6578d059. 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/51dc0392-a6e4-4426-928a-199966fd36fb.json and https://artists.proofprofile.net/proofs/artist/51dc0392-a6e4-4426-928a-199966fd36fb.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 0xfc7002b9ac7982742b10e64228131df5d5a63eb909a6c4c6f621eea98d1c6ee3. Chain 2 (Bitcoin): anchored in block 958828 (2026-07-20T05:21:06Z), 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/QM4TW2234504.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x19ac8cebcd98b3edd250fe617de3dad6af17f232451be3d41e8aa41a90931714. Chain 2 (Bitcoin): anchored in block 959123 (2026-07-22T11:35:32Z), 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/QZNJW2545039.