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 0xb4536176d95f02a71dd0af6be58aacd373b6b5a79a7e6c939d703bf3342067c5. Chain 2 (Bitcoin): anchored in block 953648 (2026-06-14T15:20:52Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/3fc7b28f-56a5-434e-9fcd-b4bdebdf1f5b.json and https://artists.proofprofile.net/proofs/artist/3fc7b28f-56a5-434e-9fcd-b4bdebdf1f5b.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Ach, sag doch nicht immer wieder Dicker zu mir
Sag' doch nicht immer Dicker zu mir‬ - 50 große Erfolge
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 0x98d1d6591d21d1f266c7e4de2845eb54321467a913722b5f856f163691a48960. Chain 2 (Bitcoin): anchored in block 958245 (2026-07-16T07:18:33Z), 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/DER751641602.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xbbb80b220eed44910d8d4ee426cd9babd98b7cd544da3d7ef34659190d3c89fe. Chain 2 (Bitcoin): anchored in block 958300 (2026-07-16T16:14:30Z), 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/DER751641626.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x7d9a9cda0fd9011f0525dd125196b508cd007fcd71ae53e6427e1485fe1c74af. Chain 2 (Bitcoin): anchored in block 959118 (2026-07-22T10:01:58Z), 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/DER751641601.
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