thumb|Désir, sculpture by Aristide Maillol Desires are states of mind that are expressed by terms like "wanting", "wishing", "longing" or "craving". A great variety of features is commonly associated
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 0xde99fab8e7575a159c9329966d8d85de9be1076b4c827c20f67cfd46eb3f5695. Chain 2 (Bitcoin): anchored in block 954553 (2026-06-20T11:51:30Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/abb9422a-1f5d-49d5-9876-130695ecad5a.json and https://artists.proofprofile.net/proofs/artist/abb9422a-1f5d-49d5-9876-130695ecad5a.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
i'd rather sleep drill funk (slow version)
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 0x60e9d16b3d8efd9df43a6d849044ef61bbb22b03427e1b6e234ada1ce77d561e. Chain 2 (Bitcoin): anchored in block 958959 (2026-07-21T03:51:22Z), 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/QZLBC2422149.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x27204e2a83678f2a3b8359564c91c4f7fc7ba875f5c0f379708d4182bc889123. 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/AEA0Q2321438.