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 0x4b1539ce523f404a2dac4af7e2353ccc85aca19bac4df8d20e6ee7d4495e15e2. Chain 2 (Bitcoin): anchored in block 954533 (2026-06-20T08:57:02Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/a41a485c-6603-4649-8e7f-cf4ffeb584c0.json and https://artists.proofprofile.net/proofs/artist/a41a485c-6603-4649-8e7f-cf4ffeb584c0.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
So we beat on, boats against the current
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 0x60fde23ee70d6234e15ed6a1a7e5b2422800ce6f1b31e152a55ad932e48bbcb1. 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/QZK6F2549407.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xd472a382510e503e062ad20f0d7e3ce4d0ada8a56930ef5055cd87af198591ff. Chain 2 (Bitcoin): anchored in block 958517 (2026-07-18T07:54: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/QZK6F2549408.
I'm so glad I live in a world where there are Octobers
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xcd886bbc8c7cecfc56f59864ca2c1740e099a16a6f7f416161161c6d7cb347ee. Chain 2 (Bitcoin): anchored in block 956578 (2026-07-04T02:23:20Z), 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/QZK6F2549409.