Ken or KEN may refer to: Entertainment Ken (album), a 2017 album by Canadian indie rock band Destroyer Ken (film), a 1965 Japanese film Ken (magazine), a large-format political magazine Ken Maste
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 0x21d0fbecb2548c6bc4bea4041202680b580b738f7064879105007fa3dcdffdee. Chain 2 (Bitcoin): anchored in block 953924 (2026-06-16T09:52:28Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/1d003b31-ab42-4a9f-9d2c-36d08ea7c114.json and https://artists.proofprofile.net/proofs/artist/1d003b31-ab42-4a9f-9d2c-36d08ea7c114.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Ambient before the Trigger (Live at Trigger In The Box 2019)
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 0x902eab8b0d90f097e52aeef83ee5685203facab7c9639a406d09a5fa8419feec. Chain 2 (Bitcoin): anchored in block 956772 (2026-07-05T10:01:46Z), 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/JPF300600460.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xedc3a7a43e7b5e5a67ec645298b5bb0b366f1ab7b8df0e4f3424fdd1dedbebbb. Chain 2 (Bitcoin): anchored in block 959146 (2026-07-22T15:41:47Z), 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/JPF300801680.