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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x676d6c06e3d420a7d93c536b5cfd904651ee5cbf19e1621113768e65362e65dc. Chain 2 (Bitcoin): anchored in block 953423 (2026-06-12T21:20:00Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/a5964fbe-ec72-4668-bdb8-374091b0856f.json and https://artists.proofprofile.net/proofs/artist/a5964fbe-ec72-4668-bdb8-374091b0856f.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Project Purple Vol. 1 Welcome to Purple City
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
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x2c11db683065f09df9592c49bb95feffde901e072c0f7f08f0dd6dde5aea372c. Chain 2 (Bitcoin): anchored in block 956312 (2026-07-02T05:09:12Z), 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/USBAE0601068.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x21d95ffcef9de14d99b658d358cdeaa7bf773c8e5c9192ecad5e3e4b03cc627c. Chain 2 (Bitcoin): anchored in block 956304 (2026-07-02T03:55:08Z), 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/USUYG1069781.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xb3dea1d13660c8d38f3e9a297b778a559e52857fb3803227a4c25b0c8d165372. Chain 2 (Bitcoin): anchored in block 960160 (2026-07-29T22:48:59Z), 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/USDYP0610209.
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