thumb|Parisian costumes: The dandies of Paris in 1831. A dandy is a man who places particular importance upon physical appearance and personal grooming, refined language and leisurely hobbies. A dand
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 0xa866d32a5f0131440caf4229a365903c25023c08841d831ca9eed9a77f868632. 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/410f8368-6463-413d-bd42-d83e77f27296.json and https://artists.proofprofile.net/proofs/artist/410f8368-6463-413d-bd42-d83e77f27296.ots, run `ots verify -f record.json proof.ots` (https://opentimestamps.org).
Let's Catch the Beat: The Music That Launched the Legend
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 0xda2ed30374937bb0320200650bf33b807a4b2a5c4f3ca49dd9bd0357a600ffb7. Chain 2 (Bitcoin): anchored in block 956725 (2026-07-05T01:12:41Z), 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/GBAJE6800531.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0x89d84698e7f9364ba8e35ab4e5a9cd6207268b46946846c6d97266e58dcd3cc8. Chain 2 (Bitcoin): anchored in block 958561 (2026-07-18T14:22:01Z), 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/GBAJE6800747.