Kiki or Ki Ki may refer to: Places Ki Ki, South Australia, Australia, a village Ki Ki, Iran, a village Kiai, Iran, a village also known as Kiki Kiki, Łask County, Poland, a village Kiki, Poddębi
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 0xacbbd38cbb8936563639bca87cb1ed999b4c0c00770c6aaea471e1fc648f1704. Chain 2 (Bitcoin): anchored in block 953750 (2026-06-15T06:12:23Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/ab29e3ca-e2ae-4ce6-afb8-cdb6a2eef55d.json and https://artists.proofprofile.net/proofs/artist/ab29e3ca-e2ae-4ce6-afb8-cdb6a2eef55d.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 0x5b47139a3a5073e3b239623ad2425b28441467de0c2e235ab304aa07ce11c653. Chain 2 (Bitcoin): anchored in block 958461 (2026-07-17T23:18: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/AEA3A2358281.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xbdc4c4552595cefa3c95339e4c5af821a2e041dee89fdc86c368263f92d127c4. Chain 2 (Bitcoin): anchored in block 956725 (2026-07-05T01:12:41Z), 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/AEA3A2324363.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x3cb106766dc9929c4de0606eb984328d46130ba315855038a87ad78a64969aeb. Chain 2 (Bitcoin): anchored in block 956545 (2026-07-03T19:59:51Z), 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/AEA3A2371994.