Z-Man may refer to: Z-Man (rapper), rapper from the San Francisco Bay Area Z-Man Games, a game company named after Zev Shlasinger Z-Man Records, an Australian record label Tom Zenk (1958–2017), Am
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 0x2edfde95a4e3ead53d4bf1abc5347a3869c92dd3cc4756f79b58dcbc86518c55. Chain 2 (Bitcoin): anchored in block 953938 (2026-06-16T11:35:56Z). Bridge: the canonical record inside this Bitcoin proof contains the same CopyrightID. Verify: download https://artists.proofprofile.net/proofs/artist/20b3da02-0dc4-49ac-ab0e-a3fe77bfc805.json and https://artists.proofprofile.net/proofs/artist/20b3da02-0dc4-49ac-ab0e-a3fe77bfc805.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 0x82dec89e9e92e73abce74941c6f5a8b4f8dff42f688c3f4d9a0316bc94cf2d63. Chain 2 (Bitcoin): anchored in block 960160 (2026-07-29T22:48:59Z), 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/QMSQD1900005.
Dual-chain trust anchor. Chain 1 (CopyrightChains): CopyrightID 0xaef7a27a9266e40c63af3a9717fc5bffb3c358735c2a1dafd9c104eb3d4ef6c7. Chain 2 (Bitcoin): anchored in block 960481 (2026-07-31T23:51:35Z), 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/DEM091200045.