Kingpin or king pin may refer to: Vehicular part Kingpin (automotive part), the pivot in the steering mechanism The central bolt of a skateboard, axle assembly ("truck"), around which the rest of t
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 0x3e450916d74871294d175ad034e8cab5b1e169eacbdfaed40458b37583cc1a36. Chain 2 (Bitcoin): anchored in block 954500 (2026-06-20T04:47:29Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/9ca5f333-22fb-4c2b-9d97-b25eec5d228f.json and https://artists.proofprofile.net/proofs/artist/9ca5f333-22fb-4c2b-9d97-b25eec5d228f.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 0x7be34ac301dc33018b5dff1fcbaa9a1b2be63a366b7a5c857c5ba3bd60134a96. Chain 2 (Bitcoin): anchored in block 958444 (2026-07-17T19:12:23Z), 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/QZFZ32568224.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xf72f4f4c0fa2814288c641e2c3e820f9b21c41a003dd77a6bba795b3de658edb. Chain 2 (Bitcoin): anchored in block 958670 (2026-07-19T05:26:23Z), 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/QZES52569130.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xe9b86f3dbb2ab2ca6fd94deb96f255845ce1690f2ac1e1638d24f821b3b17959. Chain 2 (Bitcoin): anchored in block 958300 (2026-07-16T16:14:30Z), 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/SE6XX2591348.