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 0xded409c20fa98f0ee6641b25c184cdf1c59532e2ee258ac63c1f5b258b03466c. Chain 2 (Bitcoin): anchored in block 953791 (2026-06-15T13:40:30Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/ddbc54d2-b1f3-4f8a-864b-ffd5efa48203.json and https://artists.proofprofile.net/proofs/artist/ddbc54d2-b1f3-4f8a-864b-ffd5efa48203.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
One Day I'll Find A Solution To All Of My Problems
Can’t You Just Make Fun Of The Way I Talk Again So Things Can Go Back To The Way They Used To Be?
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 0xe0521ad40ce7f08f99982b3f526b9e243df3d5e83057392b1682266976122e05. Chain 2 (Bitcoin): anchored in block 956484 (2026-07-03T10:47:44Z), 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/USE830929510.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x29710fdb06993857f7a9613001e4e7ebbe68526bdf84fa44b63ae3fd5daaa971. Chain 2 (Bitcoin): anchored in block 958975 (2026-07-21T08:28:50Z), 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/USE830929511.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x9876b14e2d969d70ac614ddbaae860aff222e9291c3872d0781f66dbe25a1238. Chain 2 (Bitcoin): anchored in block 956790 (2026-07-05T12:31:54Z), 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/USE830929513.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x1114662c3e5236cf91a980a7016166bcc595770ab4ab6a4bd4c658806e7e0250. Chain 2 (Bitcoin): anchored in block 958504 (2026-07-18T05:41:32Z), 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/QZ22B1883153.