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 0x40b0186e6fee19de805027b947a8eddaa191a38291b6607837ab1c68833c2764. Chain 2 (Bitcoin): anchored in block 954615 (2026-06-20T22:44:50Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/c75f7478-6f2f-4708-8b7f-f6b1deab462e.json and https://artists.proofprofile.net/proofs/artist/c75f7478-6f2f-4708-8b7f-f6b1deab462e.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
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 0x62e7fb93c889b3e83c06622041106d7d9e8877d89fc62ba8466e0bdcd937a603. Chain 2 (Bitcoin): anchored in block 958461 (2026-07-17T23:18:11Z), 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/QZHN42526958.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x655d754d2974542d378c5f0ce7298cdcecf9c08013581ec14702f2034b512d7e. Chain 2 (Bitcoin): anchored in block 958362 (2026-07-17T04:32:48Z), 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/QZHN52544272.
no matter what happens in the end, im the most reminiscent
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xff3506eb51959e26670beada68dbb9a8cc1391c19dcfefb6b2f59b8d1d64c8a5. Chain 2 (Bitcoin): anchored in block 958749 (2026-07-19T15:48:23Z), 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/QZK6Q2598859.
this is my goodbye / was this the only outcome?
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x6243acd19f3379190bf61ad9e01b859231b15d52df33cece7f2446f8fd8fc993. Chain 2 (Bitcoin): anchored in block 957788 (2026-07-13T02:37:37Z), 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/QZZ7S2526134.