thumb|Carved wooden duck decoys A decoy (derived from the Dutch de kooi, literally "the cage" or possibly eenden kooi, "duck cage") is usually a person, device, or event which resembles what an indiv
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 0xef072bf1b0386923f7fc298dfdec65ba04d6b6ec1c9895fed575fac72e59666d. Chain 2 (Bitcoin): anchored in block 953741 (2026-06-15T04:44:49Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/a056d94e-7fc6-4530-919e-6546784ae7f7.json and https://artists.proofprofile.net/proofs/artist/a056d94e-7fc6-4530-919e-6546784ae7f7.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Permanent Failure/False Sense of Morality
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 0xafa1fb99478a7b5ec00c1aff1e7b809f85d6226c1548a95dcdae34dcaea91eee. Chain 2 (Bitcoin): anchored in block 958796 (2026-07-20T00:01:46Z), 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/USX9P2396842.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x39fec2d3480a3c1cf0d2f6220cb154837ff3cf8441b02ca7082a4ffe6895b896. Chain 2 (Bitcoin): anchored in block 956772 (2026-07-05T10:01:46Z), 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/USCGH2425592.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x8b4b89882d9456be1e9ab9d8611fafa6a0c20d5693494de0467e0b7a6bd8b1bb. Chain 2 (Bitcoin): anchored in block 959132 (2026-07-22T13:20:46Z), 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/USCGH2425593.