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 0xd44f3e5ac3fdd3ddcc2e1efcd8f1e0069b0a3e70f509ddbb4fa13327ec2de17a. 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/16840f8d-9500-4259-a5b0-e470aef73b08.json and https://artists.proofprofile.net/proofs/artist/16840f8d-9500-4259-a5b0-e470aef73b08.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Bitte Recht einfach! Vorsorgen - Warum Vorsorgevollmacht, Patientenverfügung und Testament nicht auf die lange Bank gehören und wie du sie angehst (ungekürzt)
Kapitel 6 - Today I'll talk to him - Today, Band 1
Today I'll talk to him [Today, Band 1 (Ungekürzte Lesung)]
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 0xa5a544845bc5c8ce8cce055978faabdcbc50d19c09faf760adb8eaa2b710b236. Chain 2 (Bitcoin): anchored in block 956304 (2026-07-02T03:55:08Z), 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/DEXO52323950.
Kapitel 7 - Today I'll talk to him - Today, Band 1
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x6601da17d68a5f31ab0c10b220475d90d52a0b59f79f670250ee060e4dd58b59. Chain 2 (Bitcoin): anchored in block 956304 (2026-07-02T03:55:08Z), 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/DEXO52323951.