PK or pk may refer to: Arts and entertainment Gaming Probability of kill (Pk), in computer games, simulations, models, and operations research Disney's PK: Out of the Shadows, a 2002 video game Pl
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 0x13b55ed2967a9ba1a9fe2d8efb5b31ce0fa58011606228f6f2d7eedb11e8061e. Chain 2 (Bitcoin): anchored in block 953407 (2026-06-12T19:24:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/549f3a85-c0d4-43cc-91c2-4f7ae52b36d7.json and https://artists.proofprofile.net/proofs/artist/549f3a85-c0d4-43cc-91c2-4f7ae52b36d7.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 0x714211312b4576568dde9653261bb78b572a1ea14146578fc1727c681858e280. Chain 2 (Bitcoin): anchored in block 958695 (2026-07-19T07:37:00Z), 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/QM4TW2414277.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x99975960304b806edfbfc1750a2878ac72b086c9f76410aac6e1c7fce9e8ec16. Chain 2 (Bitcoin): anchored in block 958194 (2026-07-15T20:32:27Z), 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/QM6N22574545.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x131366522b5ce5c87fd2076e1ca63f8fa2ec79f3d7c6f9901fe6587d4bf3643a. Chain 2 (Bitcoin): anchored in block 956420 (2026-07-03T00:42: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/QMDA72526652.