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 0x20e99ee224467438afafd85a7914cfba90291905886abdf1e09dfe7291509321. Chain 2 (Bitcoin): anchored in block 953407 (2026-06-12T19:24:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/8c8c122d-4703-4093-8f0f-a3bc4259b856.json and https://artists.proofprofile.net/proofs/artist/8c8c122d-4703-4093-8f0f-a3bc4259b856.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Our heartbeats will sync if we truly listen
It feels like it will go on forever. In a good way.
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 0xc85622982284e38c4e8839d90d8a2ec2007190ecdb7d249cf88624a0a8adb99c. Chain 2 (Bitcoin): anchored in block 958428 (2026-07-17T15:15:14Z), 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/DGA062467311.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xde7ec25629f3c018e2d784342cdd592695fba5a5ef9301b8df6c8ff0596f59b9. Chain 2 (Bitcoin): anchored in block 956545 (2026-07-03T19:59:51Z), 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/DGA072493935.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xc697b47a0740adca565f4bad6c05c6102f96bd1c2e9e4fb0f28435f063fbba7b. Chain 2 (Bitcoin): anchored in block 958091 (2026-07-15T03:17:03Z), 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/DGA072494377.