Clement or Clément may refer to: People Clement (name), a given name and surname Saint Clement (disambiguation)#People Places Clément, French Guiana, a town Clement, Missouri, U.S. Clement To
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 0x02ad04e9a3c1b31d210d4f43f3bdc4084d95d08ce23855f8d64957821da7ae02. Chain 2 (Bitcoin): anchored in block 953713 (2026-06-15T00:33:41Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/84f51610-d7eb-44ed-9a09-75023d46d7e2.json and https://artists.proofprofile.net/proofs/artist/84f51610-d7eb-44ed-9a09-75023d46d7e2.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 0x49ceca44a2f95cb8798fb5ff165c05c1f744731fb33570d451619d46a4ec8813. Chain 2 (Bitcoin): anchored in block 958686 (2026-07-19T06:43:29Z), 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/GX5MX2267715.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x98d16d2ee920782d6e2978d226d6a597a6aaf157f60da2d806c5771ab08c7555. Chain 2 (Bitcoin): anchored in block 956822 (2026-07-05T18:48:28Z), 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/GX5MX2267716.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x6035622c6e7e29eeab29afe9ebe0d1e5cbb95d30bf3619cd0fc2250d8993aa3b. Chain 2 (Bitcoin): anchored in block 957647 (2026-07-12T03:57: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/GX5MX2267718.