Jack Cox may refer to: People Jack Cox (footballer) (1877–1955), English footballer Jack E. Cox (1896–1960), English cinematographer Jack Cox (Texas politician) (1921–1990), Texan politician and gube
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 0xadbd9b5f3058a2967e16cbe9a0eb69345c6f5ecf8bcf495780ca897d71961ccb. Chain 2 (Bitcoin): anchored in block 953638 (2026-06-14T13:10:39Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/3914d23c-b6a4-4cf0-aed4-f855755a6b9a.json and https://artists.proofprofile.net/proofs/artist/3914d23c-b6a4-4cf0-aed4-f855755a6b9a.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 0x33404a8060d9b48680843cc340155cac47b4e4992a1f6e0de603939faf34d527. Chain 2 (Bitcoin): anchored in block 958568 (2026-07-18T15:23: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/TCAFH2048592.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x757cada536d201c262c6f4ecbc1bfcafdbd604c527c69e59dd66fd685257d9e6. Chain 2 (Bitcoin): anchored in block 956826 (2026-07-05T19:27:56Z), 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/TCAFK2115973.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xbbf5c28d51ac215f29b11dc21d1c5c54f2027c296dee8aeeeaf947be1b401c71. Chain 2 (Bitcoin): anchored in block 956474 (2026-07-03T08:56:35Z), 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/TCAFT2137823.